scripts: remove . from $PATH
Add CT_SanitizePath function which removes entries referring to ., /tmp
and non-existing directories from $PATH, and call it early in the
build script.
If . is in PATH, gcc-4.4.4 build breaks:
[ALL ] checking what assembler to use...
/tmp/build/targets/arm-unknown-linux-uclibcgnueabi/build/gcc-core-static/arm-unknown-linux-uclibcgnueabi/bin/as
...
[ALL ] config.status: creating as
i.e. "as" is supposed to be the arm-unknown-linux-uclibcgnueabi cross assembler,
but config.status creates a local "as" script which is calling the
host assembler.
Signed-off-by: Johannes Stezenbach <js@sig21.net>
[Yann E. MORIN: style fixes + explanations]
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
(transplanted from 20dd8cef1c8adff0aa3e78ae6d7acfbc45ed5a83)
1 # Menu for the cross GDB
7 select GDB_GDBSERVER if ! BARE_METAL
9 Build and install a cross-gdb for the target, to run on host.
13 config GDB_CROSS_STATIC
15 prompt "Build a static cross gdb"
18 A static cross gdb can be usefull if you debug on a machine that is
19 not the one that is used to compile the toolchain.
21 That way, you can share the cross-gdb without installing a toolchain
22 on every machine that will be used to debug target programs.
24 config GDB_CROSS_USE_GMP_MPFR
31 gdb can use GMP+MPFR, although it does not seem compulsory.
33 Say 'Y' here if you want to use GMP+MPFR.
35 config GDB_CROSS_USE_MPC
39 select GDB_CROSS_USE_GMP_MPFR
42 gdb can use MPC, although it does not seem compulsory.
44 Say 'Y' here if you want to use MPC.