Mercurialcrosstool-ng / file revision
summary | shortlog | changelog | graph | tags | branches | files | changeset | file | latest | revisions | annotate | diff | raw | help
patches/duma/2_5_1/100-cross-compile.patch
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Mon Mar 28 01:05:18 2011 +0200 (2011-03-28)
changeset 2362 0888065f8c4d
parent 236 42650dc4e95e
permissions -rw-r--r--
cc/gcc: cleanup the _or_later logic

So far, we've had a version always select appropriate _or_later option,
which in turn would select all previous _or_later options.

Because the dependencies on companion libs were cumulative, that was
working OK. But the upcoming 4.6 will no longer depend on libelf, so
we can't keep the cumulative scheme we've been using so far.

Have each release family select the corresponding dependencies, instead
of relying on selecting previous _or_later.

Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr> 
     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  #
crosstool-ng