Mercurialcrosstool-ng / file revision
summary | shortlog | changelog | graph | tags | branches | files | changeset | file | latest | revisions | annotate | diff | raw | help
patches/duma/2_5_15/110-separate_cpp.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 747 d3e603e7c17c
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	2009-06-19 16:41:53.000000000 +0200

     3 +++ duma_2_5_15/GNUmakefile	2009-06-19 16:43:53.000000000 +0200

     4 @@ -289,9 +289,13 @@

     5  	dumatest.c tstheap.c thread-test.c testmt.c dumatestpp.cpp testoperators.cpp \

     6  	createconf.c

     7  

     8 -OBJECTS=dumapp.o duma.o sem_inc.o print.o

     9 +OBJECTS = duma.o sem_inc.o print.o

    10 +SO_OBJECTS = duma_so.o sem_inc_so.o print_so.o

    11  

    12 -SO_OBJECTS=dumapp_so.o duma_so.o sem_inc_so.o print_so.o

    13 +ifeq ($(DUMA_CPP),1)

    14 +OBJECTS += dumapp.o

    15 +SO_OBJECTS += dumapp_so.o

    16 +endif

    17  

    18  # Make all the top-level targets the makefile knows about.

    19  all:	libduma.a tstheap$(EXEPOSTFIX) dumatest$(EXEPOSTFIX) thread-test$(EXEPOSTFIX) testmt$(EXEPOSTFIX) dumatestpp$(EXEPOSTFIX) testoperators$(EXEPOSTFIX) $(DUMA_DYN_DEPS)
crosstool-ng