Bug 4148 - Add a mechanism to build a package that is the same bitsize as the machine
Summary: Add a mechanism to build a package that is the same bitsize as the machine
Status: RESOLVED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: core (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium enhancement
Target Milestone: 3.3 M3
Assignee: Kai Kang
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2013-03-28 22:20 UTC by Mark Hatle
Modified: 2021-02-04 02:27 UTC (History)
7 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Yes (doc changes required)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mark Hatle 2013-03-28 22:20:56 UTC
There are a few cases where the userspace application has to be built as the same bitsize (32-bit/64-bit) as the kernel.  In a multilib configuration where the default multilib does not match the kernel's bitsize this is very difficult for a new user to do.

For example:

a powerpc64 kernel would usually have a 32-bit (powerpc) filesystem.  Something like 'crash' needs to be built 64-bit in this case.  So the user is forced to know they have to build "lib64-crash" and not just 'crash'.

There should be a way the user can ask for 'crash', and instead they get 'lib64-crash' to build and be installed as necessary.

This is important because image / packagegroup recipes may have things like 'crash' hardcoded into them, but that package won't actually work on the target system.
Comment 1 Randy MacLeod 2018-01-25 16:22:27 UTC
Jackie, Is this still a problem for the crash package?
If so, it would be good to fix early in 2.6 unless you have a low risk change now for oe-core-2.5M3.
Comment 2 Jackie Huang 2018-01-26 08:24:33 UTC
(In reply to comment #1)
> Jackie, Is this still a problem for the crash package?

Yes, it still be a problem.

> If so, it would be good to fix early in 2.6 unless you have a low risk
> change now for oe-core-2.5M3.
Comment 3 Kai Kang 2020-10-26 18:49:28 UTC
I think it could be fixed by adding crash to NON_MULTILIB_RECIPES which is introduced by commit 25f7c6c329038b443d36074fff45a30ba3712f7a.