Created attachment 3035 [details] log.do_compile Git rev: master/8debfea81e69d038bd2d56314b272cb74f5582ed Steps: 1. Set MACHINE="qemuarm64" 2. Run bitbake gst-player This issue only happens on Fedora23 i686 for qemuarm64. I also tested on Debian 8 i686, there is no such issue. Please see the attached log for details.
(-r:27384): GLib-ERROR **: ../../glib-2.46.2/glib/gmem.c:130: failed to allocate 6102809472 bytes qemu: uncaught target signal 5 (Trace/breakpoint trap) - core dumped I don't have a 32 bit machine here - do other glib-based recipes fail to build as well, or do they work? (i.e. gstreamer, gtk+ gtk+3)
(In reply to comment #1) > (-r:27384): GLib-ERROR **: ../../glib-2.46.2/glib/gmem.c:130: failed to > allocate 6102809472 bytes > qemu: uncaught target signal 5 (Trace/breakpoint trap) - core dumped > > > I don't have a 32 bit machine here - do other glib-based recipes fail to > build as well, or do they work? (i.e. gstreamer, gtk+ gtk+3) glib-2.0, gstreamer-1.0, gtk+ and gtk+3 can build without problems
Okay, then I need ssh access to the host where you see this failure. Can you provide that? I can set it up myself, but it will take more time.
(In reply to comment #3) > Okay, then I need ssh access to the host where you see this failure. Can you > provide that? > I'm afraid you can not do that. We are in separated network and it is not permitted for my company. Sorry. Yi > I can set it up myself, but it will take more time.
I've just checked with Fedora 24 i686 and latest master, and I can't reproduce. GstPlayer*gir and GstPlayer*typelib are created just fine (they are now generated by gstreamer1.0-plugins-bad). Can you try that on your side?
(In reply to comment #5) > I've just checked with Fedora 24 i686 and latest master, and I can't > reproduce. GstPlayer*gir and GstPlayer*typelib are created just fine (they > are now generated by gstreamer1.0-plugins-bad). > > Can you try that on your side? Yes. It works on 2.2 M1 now. But still failed on krogoth branch.
Yeah, but if it's krogoth-only issue, then it is far too obscure and not worth spending time on. If anyone hits the problem (which I think is extremely unlikely), they can use a 64 bit build host, or a different distro.
This issue doesn't happen on 2.2 M1 and 2.2 M2. Verified it.