summaryrefslogtreecommitdiff
path: root/meta/recipes-devtools/gcc/gcc-configure-runtime.inc
diff options
context:
space:
mode:
authorRichard Purdie <richard.purdie@linuxfoundation.org>2011-03-15 20:11:17 +0000
committerRichard Purdie <richard.purdie@linuxfoundation.org>2011-03-21 17:40:21 +0000
commitd492ebf8b1801da99c679f465be98ce54fd3061a (patch)
tree05de172c2707009e3a2ef5cb032f5cd66e9efac7 /meta/recipes-devtools/gcc/gcc-configure-runtime.inc
parenta9d41062e24a6b99661b3a5256f369b557433607 (diff)
downloadopenembedded-core-d492ebf8b1801da99c679f465be98ce54fd3061a.tar.gz
openembedded-core-d492ebf8b1801da99c679f465be98ce54fd3061a.tar.bz2
openembedded-core-d492ebf8b1801da99c679f465be98ce54fd3061a.tar.xz
openembedded-core-d492ebf8b1801da99c679f465be98ce54fd3061a.zip
bitbake.conf/tune files: Adjust PACKAGE_EXTEA_ARCHS
There is a problem with the current PACKAGE_EXTRA_ARCHS implementation since its impossible to control which extra architectures sort higher than TARGET_ARCH and which sort lower. In the x86 case for example, TARGET_ARCH might be "i586", i486 should be lower than this and i686 should be higher. There are also complications where its easy to inject duplicate entries into the variable. I tried various versions of this patch and concluded that it was simplest just to force the tune files to include TARGET_ARCH in the list in the right place if they're planning to customise it themselves. Other approaches with appends and prepends just complicated the code for no good reason. The TARGET_ARCH definitions should also move to the tune files but I'll leave this for a separate patch. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-devtools/gcc/gcc-configure-runtime.inc')
0 files changed, 0 insertions, 0 deletions