aboutsummaryrefslogtreecommitdiffstats
path: root/meta/recipes-devtools/binutils/binutils-cross-canadian.inc
diff options
context:
space:
mode:
authorRichard Purdie <richard.purdie@linuxfoundation.org>2014-07-24 22:10:49 +0100
committerRichard Purdie <richard.purdie@linuxfoundation.org>2014-07-25 15:33:32 +0100
commit29202cd1b9d2e5d56e5b9f7a596e44e229c90492 (patch)
treeb5931519d15a489256a14b869b40660a85c5645e /meta/recipes-devtools/binutils/binutils-cross-canadian.inc
parent5aea553e6eaa3b9647f26944976d2a9da79cba42 (diff)
downloadopenembedded-core-contrib-29202cd1b9d2e5d56e5b9f7a596e44e229c90492.tar.gz
gcc-multilib: Simply/fix MULTILIB_OPTIONS handling
MULTILIB_OPTIONS takes the parameters which trigger a given multilib to be selected. It supports *one* option per multilib, '/' separated. Spaces separate options used to generate additional multilib combinations. Adding in all of CFLAGS to this is therefore clearly a really bad idea but how do we fix things? The best option I've come up with so far is a list of whitelist variables to use to trigger the multilibs. Its populated with the standard multilibs we support, anyone setting up an advanced multilib can populate the variable with the correct trigger parameters. This has the advantage of simplifying the code and allowing us to remove the code filtering blocks since there is no longer option duplication. Testing after this change shows a much improved sdk toolchain functionality. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-devtools/binutils/binutils-cross-canadian.inc')
0 files changed, 0 insertions, 0 deletions