scripts: always create lib32 and lib64 symlinks
Unconditionally create the lib32 -> lib/ and lib64 -> lib/ symlinks.
This is reportedly a fix to build a toolchain for a 32-bit target on
a 'pure' 64-bit host (eg. on Fedora FC12, host libs are in lib64/,
and there is no lib -> lib64 symlink, as we can see on other distors,
as Debian). As gcc only puts static host lib in lib64/ (along with
target files in subdirs), we can safely create the symlinks.
Also note that the symlinks are summarily removed at the end
of the build.
Signed-off-by: Anthony Foiani <anthony.foiani@gmail.com>
[Yann E. MORIN: fix a comment, rephrase the commit log]
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
1 # Test suite config options
13 prompt "GCC test suite"
14 depends on EXPERIMENTAL
18 Select this option to install the GCC test suite in $CT_PREFIX_DIR/test_suite.
20 The GCC test suite includes a collection of various toolchain tests for GCC -
21 it utilizes the DejaGnu test framework.
23 For some tests a network enabled target with ssh server is required.
25 A helper Makefile is provided for running the tests - please see the included
26 README for information on how to run the test suite.