On Tue, Oct 29, 2019 at 10:52 PM Khem Raj <raj.k...@gmail.com> wrote: > > see > > gcc > -LTOPDIR/build/tmp/work/x86_64-linux/colord-native/1.4.4-r0/recipe-sysroot-native/usr/lib > > -LTOPDIR/build/tmp/work/x86_64-linux/colord-native/1.4.4-r0/recipe-sysroot-native/lib > -Wl,--enable-new-dtags > -Wl,-rpath-link,TOPDIR/build/tmp/work/x86_64-linux/colord-native/1.4.4-r0/recipe-sysroot-native/usr/lib > > -Wl,-rpath-link,TOPDIR/build/tmp/work/x86_64-linux/colord-native/1.4.4-r0/recipe-sysroot-native/lib > > -Wl,-rpath,TOPDIR/build/tmp/work/x86_64-linux/colord-native/1.4.4-r0/recipe-sysroot-native/usr/lib > > -Wl,-rpath,TOPDIR/build/tmp/work/x86_64-linux/colord-native/1.4.4-r0/recipe-sysroot-native/lib > -Wl,-O1 -Wl,--allow-shlib-undefined > -Wl,--dynamic-linker=TOPDIR/build/tmp/sysroots-uninative/x86_64-linux/lib/ld-linux-x86-64.so.2 > -LTOPDIR/build/tmp/work/x86_64-linux/colord-native/1.4.4-r0/recipe-sysroot-native/usr/lib/pkgconfig/../../../usr/lib > -lgio-2.0 -lgobject-2.0 -lglib-2.0 > -LTOPDIR/build/tmp/work/x86_64-linux/colord-native/1.4.4-r0/recipe-sysroot-native/usr/lib/pkgconfig/../../../usr/lib > -llcms2 -lm -LTOPDIR/build/tmp/work/x86_64-linux/colord-native/1.4.4-r0/build > -lcolord > TOPDIR/build/tmp/work/x86_64-linux/colord-native/1.4.4-r0/build/cd_idt8.o > -o TOPDIR/build/tmp/work/x86_64-linux/colord-native/1.4.4-r0/build/cd_idt8 > > it does show that we are linking -lgobject-2.0 but order seems a bit > iffy to me. Since it should appeat after .o files. > > On Tue, Oct 29, 2019 at 10:37 PM Khem Raj <raj.k...@gmail.com> wrote: > > > > it seems its not linking with gobject-2.0 properly, pango had similar > > problem which was fixed with > > https://gitlab.gnome.org/GNOME/pango/commit/d0cb6be7431d1a3c711bd45bcf05b34601604037 > > > > On Tue, Oct 29, 2019 at 4:43 PM Andreas Müller <schnitzelt...@gmail.com> > > wrote: > > > > > > On Tue, Oct 29, 2019 at 3:15 PM Khem Raj <raj.k...@gmail.com> wrote: > > > > > > > > Fails again > > > > > > > > https://errors.yoctoproject.org/Errors/Details/274899/ > > > > > > > Continuing like this does not make sense any more. Need to set up an > > > environment where I can reproduce this error - may last. > > > Good news: Our company's stone-age autobuilder shows the same error. That opens me the door to a more systematic approach :)
Andreas -- _______________________________________________ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel