samples/powerpc-e500v2-linux-gnuspe/reported.by
author "Yann E. MORIN" <yann.morin.1998@free.fr>
Thu Dec 27 12:45:22 2012 +0100 (2012-12-27)
changeset 3152 b286c7993be5
parent 2290 ba82eb173bd4
permissions -rw-r--r--
scripts/addToolsVersion: properly handle .in vs. .in.2

While most components have their version in the .in file, some
have it in the .in.2 (eg. elf2flt).

Currently, to handle this case, we indiscriminately munge both files,
but this is wrong: in the elf2flt case, if we add a binutils version,
we do not want it to be added to elf2flt, and conversely.

So, for each tool, we need to explicitly know what file to munge.

Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.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@2369
     4
MPC8572). It uses eglibc (for e500/SPE patches) and a recent gcc (4.6.0,
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."