Mercurialcrosstool-ng / file revision
summary | shortlog | changelog | graph | tags | branches | files | changeset | file | latest | revisions | annotate | diff | raw | help
patches/duma/2_5_8/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
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_8.orig/Makefile duma_2_5_8/Makefile

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

     3 +++ duma_2_5_8/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 @@ -281,7 +278,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 @@ -338,7 +335,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