Mercurialcrosstool-ng / file revision
summary | shortlog | changelog | graph | tags | branches | files | changeset | file | latest | revisions | annotate | diff | raw | help
patches/duma/2_5_12/100-cross-compile.patch
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Tue Sep 23 14:48:10 2008 +0000 (2008-09-23)
changeset 872 fd4bf138f08f
permissions -rw-r--r--
Bart De VOS pointed out that removing absolute paths from the libc linker scripts is plainly wrong.
It dates from dawn ages of the original crosstool code, and is not well explained. At that time, binutils might not understand the sysroot stuff, and it was necessary to remove absolute paths in that case.

/trunk/scripts/build/libc/glibc.sh | 14 2 12 0 ++------------
1 file changed, 2 insertions(+), 12 deletions(-) 
     1 diff -durN duma_2_5_12.orig/Makefile duma_2_5_12/Makefile

     2 --- duma_2_5_12.orig/Makefile	2007-08-17 09:34:25.000000000 +0200

     3 +++ duma_2_5_12/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 @@ -299,7 +296,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 @@ -360,7 +357,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  #
crosstool-ng