Mercurialcrosstool-ng / file revision
summary | shortlog | changelog | graph | tags | branches | files | changeset | file | latest | revisions | annotate | diff | raw | help
patches/duma/2_5_15/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 572 944e145f3890
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 -durN duma_2_5_15.orig/GNUmakefile duma_2_5_15/GNUmakefile

     2 --- duma_2_5_15.orig/GNUmakefile	2008-08-03 21:22:38.000000000 +0200

     3 +++ duma_2_5_15/GNUmakefile	2009-06-19 15:32:23.000000000 +0200

     4 @@ -93,10 +93,6 @@

     5  # also define 'WIN32'

     6  

     7  # some defaults:

     8 -CC=gcc

     9 -CXX=g++

    10 -AR=ar

    11 -RANLIB=ranlib

    12  INSTALL=install

    13  RM=rm

    14  RMFORCE=rm -f

    15 @@ -471,7 +467,7 @@

    16  

    17  createconf$(EXEPOSTFIX): createconf.o

    18  	- $(RMFORCE) createconf$(EXEPOSTFIX)

    19 -	$(CC) $(CFLAGS) $(DUMA_OPTIONS) createconf.o -o createconf$(EXEPOSTFIX)

    20 +	$(HOSTCC) $(HOSTCFLAGS) $(DUMA_OPTIONS) createconf.o -o createconf$(EXEPOSTFIX)

    21  

    22  tstheap$(EXEPOSTFIX): libduma.a tstheap.o

    23  	- $(RMFORCE) tstheap$(EXEPOSTFIX)

    24 @@ -532,7 +528,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