README
author Oron Peled <oron@actcom.co.il>
Mon Aug 03 00:49:25 2009 +0200 (2009-08-03)
changeset 1449 8ad2773e7ae3
parent 1335 4a5540d3a301
child 1463 de40924df7b4
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 This is the README for crosstool-NG
     2 
     3 To get you started, just enter:
     4   ./configure --help
     5 
     6 You can find a (terse and WIP) documentation in docs/overview.txt.
     7 
     8 You can also point your browser to
     9   http://ymorin.is-a-geek.org/dokuwiki/projects/crosstool
    10 
    11 If you want to enhance crosstool-NG, there's a to-do list in the TODO file.
    12 
    13 If you need to send a bug report or a patch, please send a mail with subject
    14 prefixed with "[CT_NG]" with the following destinations:
    15     TO: yann.morin.1998 (at) anciens.enib.fr
    16     CC: crossgcc (at) sourceware.org
    17 
    18 Patches should come with the appropriate SoB line. A SoB line is typically
    19 something like:
    20   Signed-off-by: John DOE <john.doe@somewhere.net>
    21 
    22 The SoB line is clearly described in Documentation/SubmittingPatches , section
    23 12, of your favourite Linux kernel source tree.
    24 
    25 The people that helped are listed in docs/CREDITS. Many thanks to them! :-)
    26 
    27 The list of known issues is listed in docs/known-issues.txt.
    28 
    29 Aloha!