The extensible SDK uses uninative.bbclass, and that not only requires that SDK_ARCH == BUILD_ARCH (since it re-uses some items built for the build host), but it also has UNINATIVE_LOADER hardcoded to "${STAGING_DIR_NATIVE}/lib/ld-linux-x86-64.so.2" which limits it to 64-bit x86 machines, placing the same limitation on the extensible SDK.
(In reply to comment #0) > The extensible SDK uses uninative.bbclass, and that not only requires that > SDK_ARCH == BUILD_ARCH (since it re-uses some items built for the build > host), but it also has UNINATIVE_LOADER hardcoded to > "${STAGING_DIR_NATIVE}/lib/ld-linux-x86-64.so.2" which limits it to 64-bit > x86 machines, placing the same limitation on the extensible SDK. Paul, is this not the same issue that is fixed in 8124?
We do still have the SDK_ARCH == BUILD_ARCH limitation, but I don't think that's going to be solvable in 2.1 and we might want to create a new bug for that.
The UNINATIVE_LOADER LIMITATION was fixed with BUG 8124. Regarding SDK_ARCH == BUILD_ARCH, BUG 8929 was opened to address it.