samples/powerpc-e500v2-linux-gnuspe/reported.by
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 2173 fff955de3fb8
child 2369 c92281709a49
permissions -rw-r--r--
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>
yann@2139
     1
reporter_name="Anthony Foiani <anthony.foiani@gmail.com>"
yann@2139
     2
reporter_url="http://sourceware.org/ml/crossgcc/2010-09/msg00100.html"
yann@2290
     3
reporter_comment="This is a sample config file for Freescale e500v2 processors (e.g., MPC8548,
yann@2173
     4
MPC8572). It uses eglibc (for e500/SPE patches) and a recent gcc (4.5.1,
yann@2173
     5
for e500v2 DPFP support) and will generate appropriate dual-precision
yann@2173
     6
floating point instructions by default.
yann@935
     7
yann@2173
     8
Note: If building a Linux kernel with this toolchain, you will want to make
yann@2173
     9
sure -mno-spe AND -mspe=no are passed to gcc to prevent SPE ABI/instructions
yann@2173
    10
from getting into the kernel (which is currently unsupported). At this time,
yann@2173
    11
the kernel build system properly passes those two options, but older kernels
yann@2173
    12
were only passing -mno-spe by default."