patches/duma/2_5_8/100-cross-compile.patch
author Oron Peled <oron@actcom.co.il>
Mon Aug 03 00:49:25 2009 +0200 (2009-08-03)
changeset 1449 8ad2773e7ae3
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 diff -durN duma_2_5_8.orig/Makefile duma_2_5_8/Makefile
     2 --- duma_2_5_8.orig/Makefile	2007-08-17 09:34:25.000000000 +0200
     3 +++ duma_2_5_8/Makefile	2007-09-07 21:50:04.000000000 +0200
     4 @@ -93,9 +93,6 @@
     5  # also define 'WIN32'
     6  
     7  # some defaults:
     8 -CC=gcc
     9 -CXX=g++
    10 -AR=ar
    11  INSTALL=install
    12  RM=rm
    13  RMFORCE=rm -f
    14 @@ -281,7 +278,7 @@
    15  
    16  createconf$(EXEPOSTFIX): createconf.o
    17  	- $(RMFORCE) createconf$(EXEPOSTFIX)
    18 -	$(CC) $(CFLAGS) $(DUMA_OPTIONS) createconf.o -o createconf$(EXEPOSTFIX)
    19 +	$(HOSTCC) $(HOSTCFLAGS) $(DUMA_OPTIONS) createconf.o -o createconf$(EXEPOSTFIX)
    20  
    21  tstheap$(EXEPOSTFIX): libduma.a tstheap.o
    22  	- $(RMFORCE) tstheap$(EXEPOSTFIX)
    23 @@ -338,7 +335,7 @@
    24  # define rules how to build objects for createconf
    25  #
    26  createconf.o:
    27 -	$(CC) $(CFLAGS) $(DUMA_OPTIONS) -c createconf.c -o $@
    28 +	$(HOSTCC) $(HOSTCFLAGS) $(DUMA_OPTIONS) -c createconf.c -o $@
    29  
    30  
    31  #