In order to be able to use the build system within the new SDK we need to be able to keep it isolated from the host system. One of the good things about our existing SDK is that it ships its own libc which avoids any dependency on the host's one, which may have a different ABI than the one linked to when the SDK was built. If we're shipping the build system within the SDK, any native binaries within the sysroot should also be using that libc (and any other libraries that are part of the host part of the SDK). There is a small caveat in that the native libc when building the SDK must still be older or ABI-compatible with the nativesdk libc being built for the SDK. We may want to add some kind of check for this so that at least we fail during the build rather than when trying to actually use the SDK.
http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=2cbab459e471abbddba8badc64805e7226e864be
Mihai, can you verify this and also see if a TC is needed? Thanks!
Created attachment 2156 [details] populate_sdk log
bitbake uninative-tarball fails with error: nativesdk-eglibc not found in the base feeds (x86_64-nativesdk noarch any all) Richard has confirmed this is a genuine bug. Reopening.
Changing nativesdk-eglibc to nativesdk-glibc in the recipe works.
http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=0389b3b7e8004373320689750ecf877ae5cc6da9
Verified.