samples/powerpc-e500v2-linux-gnuspe/reported.by
author Oron Peled <oron@actcom.co.il>
Mon Aug 03 00:49:25 2009 +0200 (2009-08-03)
changeset 1449 8ad2773e7ae3
parent 935 e175e3538310
child 2139 983823b3b569
permissions -rw-r--r--
[complib:mpfr] Fix building MPFR in some weird cases

The tmul test uses a compiled-in input file in $(srcdir).
The problem is that the Makefile passes it unquoted. The C code
tries to stringify it using clever macros, which may *usually* work.

In my case the source directory was named:
.../toolchain-powerpc-e500v2-linux-gnuspe-1.0-2.fc10/.../tests
And guess what? During testing I found out the program fails because
it tries to open:
.../toolchain-powerpc-e500v2-1-gnuspe-1.0-2.fc10/.../tests

Yes, CPP tokenized the macro before stringifying it and not surprisingly
the 'linux' part was converted to 1.
[on Fedora-10: cpp (GCC) 4.3.2 20081105 (Red Hat 4.3.2-7)]

So the attached patch simplify the macros and pass the path as string
from the Makefile.
     1 reporter_name="Nate CASE"
     2 reporter_url="http://sourceware.org/ml/crossgcc/2008-10/msg00016.html"
     3 reporter_comment="This is a sample config file for Freescale e500v2 processors (e.g.,
     4 MPC8548, MPC8572).  It uses eglibc (for e500/SPE patches) and a recent
     5 gcc (4.3.1, for e500v2 DPFP support) and will generate appropriate
     6 dual-precision floating point instructions by default.
     7 
     8 Note: If building a Linux kernel with this toolchain, you will want to
     9 make sure -mno-spe AND -mspe=no are passed to gcc to prevent SPE
    10 ABI/instructions from getting into the kernel (which is currently
    11 unsupported).  At this time, the kernel build system only passes
    12 -mno-spe by default (this should be fixed soon hopefully)."