patches/duma/2_5_1/100-cross-compile.patch
author Oron Peled <oron@actcom.co.il>
Mon Aug 03 00:49:25 2009 +0200 (2009-08-03)
branch1.4
changeset 1456 94fc77c37418
parent 236 42650dc4e95e
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.

Manually backported from 1449:8ad2773e7ae3
     1 diff -dur duma_2_5_1/Makefile duma_2_5_1.orig/Makefile
     2 --- duma_2_5_1/Makefile	2006-06-18 06:02:13.000000000 +0200
     3 +++ duma_2_5_1.orig/Makefile	2007-07-11 17:49:43.000000000 +0200
     4 @@ -98,10 +98,6 @@
     5    LIBS=-lpthread
     6  endif
     7  
     8 -
     9 -CC=gcc
    10 -CXX=g++
    11 -AR=ar
    12  INSTALL=install
    13  
    14  ############################################################
    15 @@ -169,7 +165,7 @@
    16  
    17  createconf: createconf.o
    18  	- rm -f createconf
    19 -	$(CC) $(CFLAGS) $(DUMA_OPTIONS) createconf.o -o createconf
    20 +	$(HOSTCC) $(HOSTCFLAGS) $(DUMA_OPTIONS) createconf.o -o createconf
    21  
    22  tstheap: libduma.a tstheap.o
    23  	- rm -f tstheap
    24 @@ -211,7 +207,7 @@
    25  # define rules how to build objects for createconf
    26  #
    27  createconf.o:
    28 -	$(CC) $(CFLAGS) $(DUMA_OPTIONS) -c createconf.c -o $@
    29 +	$(HOSTCC) $(HOSTCFLAGS) $(DUMA_OPTIONS) -c createconf.c -o $@
    30  
    31  
    32  #