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>
1 # powerpc specific configuration file
4 select ARCH_SUPPORTS_32
5 select ARCH_SUPPORTS_64 if EXPERIMENTAL
8 select ARCH_SUPPORT_ABI
9 select ARCH_SUPPORT_CPU
10 select ARCH_SUPPORT_TUNE
12 The PowerPC architecture, as defined by:
13 http://www.ibm.com/developerworks/eserver/articles/archguide.html
15 config ARCH_POWERPC_SPE
17 prompt "Enable SPE support"
20 Add support for the Signal Processing Engine. This will set up
21 the toolchain so that it supports the SPE ABI extensions. This
22 mainly targets Freescale e500 processors.
24 Setting this option will append "spe" to the end of your target
25 tuple name (e.g., powerpc-e500v2-linux-gnuspe) so that the gcc
26 configure/build system will know to include SPE ABI support.
27 It will also automatically add "-mabi=spe -mspe" to your
28 TARGET_CFLAGS, and "--enable-e500_double" to your CC_EXTRA_CONFIG,
29 so you do not need to explicitly add them.