On Tue, Jan 12, 2016 at 2:02 PM, Andre McCurdy <[email protected]> wrote: > On Tue, Jan 12, 2016 at 1:32 PM, Richard Purdie > <[email protected]> wrote: >> On Mon, 2016-01-11 at 23:18 -0800, Andre McCurdy wrote: >>> Andre McCurdy (5): >>> strace: drop unnecessary dependency on acl >>> strace: fix --disable-aio configure option >>> strace: remove need for git-version-gen script >>> strace: fix ARCH definition in tests/Makefile >>> strace: update 4.10 -> 4.11 >> >> I included this in a -next build but it failed on the autobuilder: >> >> http://errors.yoctoproject.org/Errors/Details/27173/ >> http://errors.yoctoproject.org/Errors/Details/27101/ >> http://errors.yoctoproject.org/Errors/Details/27101/ >> >> One is poky, one is poky-lsb, looks like it might be a debian system >> specific issue :/. > > Looks like it's calling the host gcc with -isystem set to OE's > x86_64-linux sysroot, and then gets confused because host gcc seems to > be generating 32bit binaries by default. > > Does adding "-m64" to the failing gcc command line fix it?
Clearing CFLAGS_FOR_BUILD, CPPFLAGS_FOR_BUILD and LDFLAGS_FOR_BUILD from within the recipe looks like it's going to fix it. CPPFLAGS_FOR_BUILD = "" CFLAGS_FOR_BUILD = "" CXXFLAGS_FOR_BUILD="" LDFLAGS_FOR_BUILD = "" It raises some questions though. We setup CFLAGS_FOR_BUILD etc unconditionally from autotools.bbclass with -isystem pointing to the native sysroot, but I don't see any default dependency to ensure that the native sysroot actually contains anything. Should CFLAGS_FOR_BUILD etc perhaps only be setup for packages which are known to need it, when we know there's an appropriate dependency in place to populate the native sysroot? >> Cheers, >> >> Richard >> -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
