Bug 8723 - extensible SDK: remove limitation to 64-bit x86 machines
Summary: extensible SDK: remove limitation to 64-bit x86 machines
Status: RESOLVED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: core (show other bugs)
Version: 2.0
Hardware: All Multiple
: Medium+ enhancement
Target Milestone: 2.1 M2
Assignee: Randy Witt
QA Contact: Aníbal Limón
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2015-11-24 22:08 UTC by Paul Eggleton
Modified: 2016-01-26 10:33 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Don't know


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Paul Eggleton 2015-11-24 22:08:24 UTC
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.
Comment 1 Randy Witt 2016-01-14 22:17:05 UTC
(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?
Comment 2 Paul Eggleton 2016-01-14 22:19:40 UTC
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.
Comment 3 Randy Witt 2016-01-14 22:42:09 UTC
The UNINATIVE_LOADER LIMITATION was fixed with BUG 8124. Regarding SDK_ARCH == BUILD_ARCH, BUG 8929 was opened to address it.