On Fri, 2016-03-04 at 15:55 -0800, Andre McCurdy wrote: > On Fri, Mar 4, 2016 at 3:23 PM, Khem Raj <[email protected]> wrote: > > On Sat, Mar 5, 2016 at 6:33 AM, Richard Purdie > > <[email protected]> wrote: > > > > > > +# https://wiki.debian.org/GCC5 > > > +# We may see binaries built with gcc5 run or linked into gcc4 > > > environment > > > +# so use the older libstdc++ standard for now until we don't > > > support gcc4 > > > +# on the host system. > > > +BUILD_CXXFLAGS_append = " -D_GLIBCXX_USE_CXX11_ABI=0" > > > > > > Is this the right way to try and fix this? Any better ideas? > > > > yes thats the best option we have given the myriad of build OSes we > > have to support. > > An alternative would be to configure our uninative gcc5 libstdc++ > with: > > EXTRA_OECONF_append = " --disable-libstdcxx-dual-abi > --with-default-libstdcxx-abi=gcc4-compatible" > > Not sure if that's better though. Just a different approach to > achieve > the same thing.
We don't actually build our own gcc-native with uninative though, we're trying to keep it small/fast and adding our own gcc doesn't really do that. I'm going to test the above and some other fixes on the autobuilder, see how it looks. Cheers, Richard -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
