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@free.fr>
Sun Nov 25 18:22:38 2012 +0100 (2012-11-25)
changeset 3133 36aa2ae92c29
parent 236 42650dc4e95e
permissions -rw-r--r--
cc/gcc: do not print 'core' or 'final'

In gcc-'s core and final passes, do not print 'core' or 'final' in
log messages. We already print it in step messages.

Also, as we use the core backend to build the bare-metal final gcc,
it can be disturbing to read 'core' while we're in fact in 'final'.

Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.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