crosstool-ng: patches/gcc/4.2.3/280-eabi

buildtools: move to working directory

There is absolutely *no* reason for the buildtools (wrappers to gcc, g++,
as, ld... for the local machine) to be in the toolchain directory. Moreover,
they are removed after the build completes.

Move them out of the toolchain directory, and into the build directory (but
yet the part specific to the current toolchain). This means we no longer
need to explicitly remove them either, BTW, but we need to save/restore them
for the restart feature.

Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>

     1 diff -durN gcc-4.2.3.orig/gcc/config/arm/linux-eabi.h gcc-4.2.3/gcc/config/arm/linux-eabi.h

     2 --- gcc-4.2.3.orig/gcc/config/arm/linux-eabi.h	2007-09-01 17:28:30.000000000 +0200

     3 +++ gcc-4.2.3/gcc/config/arm/linux-eabi.h	2008-05-25 23:47:36.000000000 +0200

     4 @@ -47,7 +47,8 @@

     5  #define SUBTARGET_CPU_DEFAULT TARGET_CPU_arm10tdmi

     7  #undef SUBTARGET_EXTRA_LINK_SPEC

     8 -#define SUBTARGET_EXTRA_LINK_SPEC " -m armelf_linux_eabi"

     9 +#define SUBTARGET_EXTRA_LINK_SPEC	\

    10 +	" %{mlittle-endian:-m armelf_linux_eabi} %{mbig-endian:-m armelfb_linux_eabi}"

    12  /* Use ld-linux.so.3 so that it will be possible to run "classic"

    13     GNU/Linux binaries on an EABI system.  */

author	"Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
	Thu Dec 23 20:43:32 2010 +0100 (2010-12-23)
changeset 2307	2efd46963086
parent 533	81a582c81c13
permissions	-rw-r--r--