So, do you mean that this is not a layer problem but distro problem? Considering Yocto/Poky based distro like Silica/ArchiTech or Ti/Arago: should I contact Arago or ArchiTech community or Poky community? Who should define these parameters "umbrella" distro or sub-distro? I suppose I should contact myself (or Poky), as I started from plain Yocto/Poky and copied some layers from Arago distribution (meta-ti and layers it required).
2015-06-12 17:51 GMT+03:00 Khem Raj <[email protected]>: > On Fri, Jun 12, 2015 at 4:16 AM, matti kaasinen > <[email protected]> wrote: > > > > klibc_2.0.4.bb recipe linking crashes with following error messages. > > arm-poky-linux-gnueabi-ld: error: > > > .../sysroots/am335x-evm/usr/lib/arm-poky-linux-gnueabi/4.9.2/libgcc.a(bpabi.o) > > uses VFP register arguments, usr/klibc/libc.so does not > > arm-poky-linux-gnueabi-ld: failed to merge target specific data of file > > > .../sysroots/am335x-evm/usr/lib/arm-poky-linux-gnueabi/4.9.2/libgcc.a(bpabi.o) > > > > I'm checked out fido branch of meta-openembedded. > > It means that TOOLCHAIN_OPTIONS is not passed via CFLAGS when building > klibc, we have a diversion > in expectation where we do not configure toolchain to hardfp unless we > specify it via cmdline to compiler. Once you > fix that, next thing might be that klibc is not good with hardfp > itself which could be a bigger problem. > -- > _______________________________________________ > Openembedded-devel mailing list > [email protected] > http://lists.openembedded.org/mailman/listinfo/openembedded-devel > -- _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-devel
