Mercurialcrosstool-ng / file revision
summary | shortlog | changelog | graph | tags | branches | files | changeset | file | latest | revisions | annotate | diff | raw | help
patches/duma/2_5_14/100-cross-compile.patch
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Sun Jan 17 23:06:02 2010 +0100 (2010-01-17)
changeset 1740 c57458bb354d
permissions -rw-r--r--
configure: do not require hg when configuring in an hg clone

When configuring in an hg clone, we need hg to compute the version string.
It can happen that users do not have Mercurial (eg. if they got a snapshot
rather that they did a full clone). In this case, we can still run, of
course, so simply fill the version string with a sufficiently explicit
value, that does not require hg. The date is a good candidate. 
     1 diff -durN duma_2_5_14.orig/Makefile duma_2_5_14/Makefile

     2 --- duma_2_5_14.orig/Makefile	2008-03-13 00:54:10.000000000 +0100

     3 +++ duma_2_5_14/Makefile	2008-06-17 10:28:45.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 @@ -317,7 +313,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 @@ -378,7 +374,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