testing uclibc changes is tricky because the final gcc tends to miscompile
uclibc code or barf up internal compiler errors.
install binutils into $(TOOLCHAIN_DIR)/initial (without changing the configure
prefix) and copy it from there to $(TOOLCHAIN_DIR)/ so that the initial gcc
can be put into $(PATH) for the uclibc build, even if the final gcc
is already installed.
SVN-Revision: 32553
Currently, to build a biarch toolchain, we need to explicitly give
options to the binutils and gcc configure commands:
CONFIG_EXTRA_BINUTILS_CONFIG_OPTIONS="--enable-targets=powerpc64-linux-uclibc"
CONFIG_EXTRA_GCC_CONFIG_OPTIONS="--enable-biarch --enable-targets=powerpc64-linux-uclibc"
This change replaces the command line options with an 'extra arch'
configure option:
CONFIG_EXTRA_TARGET_ARCH=y
CONFIG_EXTRA_TARGET_ARCH_NAME="powerpc64"
And a way to invoke this extra arch on the compiler command-line:
CONFIG_EXTRA_TARGET_ARCH_OPTS="-m64"
In this case, this results in an extra compiler:
'powerpc64-linux-uclibc-gcc', which invokes
'powerpc-linux-uclibc-gcc -m64'
This is a more standard way of building biarch toolchains, and allows
the packages to not have to care about how to invoke the 64-bit
compiler.
Signed-off-by: Jeremy Kerr <jk@ozlabs.org>
SVN-Revision: 10802
Currently, we can specify extra configure options for gcc, but not
binutils.
This change adds an EXTRA_BINUTILS_CONFIG_OPTIONS config variable,
so we can add configure options for binutils.
Signed-off-by: Jeremy Kerr <jk@ozlabs.org>
SVN-Revision: 9407
Felix Fietkau