Hi Anders, On Wed, Jun 14, 2017 at 11:20:57AM +0200, Anders Darander wrote: > * Maxin B. John <maxin.j...@intel.com> [170614 10:24]: > > > Hi Paul, > > > On Tue, Jun 13, 2017 at 04:24:38PM -0700, Paul D. DeRocco wrote: > > > In order to try out the much more recent compiler in the Yocto SDK (and to > > > prepare for converting to a different architecture in the future), I built > > > a standard SDK by using do_populate_sdk on my image. I managed to modify > > > my project to use the toolchain and libraries in the sysroot in the SDK, > > > and it successfully produces an executable. But when I copy this into my > > > system, it barfs because there is no libstdc++.o (and perhaps other > > > libraries) on my system. And there is no libstdc++.a in the SDK. > > > Had a similar experience with respect to the availability of static > > libraries > > in the SDK. > > > https://bugzilla.yoctoproject.org/show_bug.cgi?id=5347 > > > One way to fix this will be to include required static libraries in the > > image > > before building SDK - eg: for glibc static development libraries: > > > IMAGE_INSTALL_append = " glibc-staticdev" > > Why install it to the image? > > TOOLCHAIN_TARGET_TASK_append = " glibc-staticdev" > > would be better, as it'll only add this package to the SDK.
Thanks for the suggestion. This looks much better. Time to update the documentation :) > Cheers, > Anders Best Regards, Maxin -- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto