CODEWITHSUNDEEP
yoctobitbake
aerkenemesis
aerkenemesis

Reputation: 672

Controlling architecture in resulting RPM's

I am trying to build all the recipes I made for my target architecture for my host systems architecture (x86_64), with the intention of being able to install these RPM's in x86_64 environments.

To do this I simply set MACHINE=genericx86-64 and build; however, the resulting RPM's seem to have their architecture set to core2_64. I guess it is related to the TUNE_FEATURES="m64 core2" reported when running bitbake (see below).

How can I make sure that these RPM's end up as x86_64 so that my host (RHEL7) accepts them?

Build Configuration:
BB_VERSION        = "1.34.0"
BUILD_SYS         = "x86_64-linux"
NATIVELSBSTRING   = "universal-4.8"
TARGET_SYS        = "x86_64-poky-linux"
MACHINE           = "genericx86-64"
DISTRO            = "generic-panel"
DISTRO_VERSION    = "0.7"
TUNE_FEATURES     = "m64 core2"
TARGET_FPU        = ""

Example

# rpm -i xxx.core2_64.rpm
package xxx.core2_64 is intended for a different architecture

$ uname -a
Linux localhost 3.10.0-693.2.2.el7.x86_64 #1 SMP Sat Sep 9 03:55:24 EDT 2017 x86_64 x86_64 x86_64 GNU/Linux

Upvotes: 0

Views: 1529

Answers (1)

aerkenemesis
aerkenemesis

Reputation: 672

The solution was to modify the DEFAULTTUNE variable, so i just added DEFAULTTUNE_genericx86-64 = "x86-64" to my local.conf.

Upvotes: 1

Related Questions