[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [bug-gnulib] inline.m4: use compiler, not cpp
From: |
Bruno Haible |
Subject: |
Re: [bug-gnulib] inline.m4: use compiler, not cpp |
Date: |
Tue, 14 Nov 2006 11:51:39 +0100 |
User-agent: |
KMail/1.9.1 |
Paul Eggert wrote:
> whenever you get into trouble, just do "make clean"
> and then make with the CFLAGS you prefer.
Many hackers probably use the same approach... Since "make CFLAGS=..." does
not pass the CFLAGS down to subdirectories, the user of a package with
- its main sources in the main directory,
- gnulib sources in a subdirectory,
will, after doing
$ ./configure
$ make
$ make clean
$ make CFLAGS="-g -O0"
be trapped in the link error: xmalloc.c, compiled with optimization, will
not define xnmalloc, whereas the main sources, compiled without optimization,
will require it.
So I think it's more robust (i.e. it will minimize user frustration) if
we test __NO_INLINE__ at configure time, not at compile time.
Bruno
Re: inline.m4: use compiler, not cpp, Eric Blake, 2006/11/11
- Re: inline.m4: use compiler, not cpp, Paul Eggert, 2006/11/11
- Re: [bug-gnulib] inline.m4: use compiler, not cpp, Bruno Haible, 2006/11/13
- Re: [bug-gnulib] inline.m4: use compiler, not cpp, Paul Eggert, 2006/11/13
- Re: [bug-gnulib] inline.m4: use compiler, not cpp, Bruno Haible, 2006/11/13
- Re: [bug-gnulib] inline.m4: use compiler, not cpp, Paul Eggert, 2006/11/13
- Re: [bug-gnulib] inline.m4: use compiler, not cpp,
Bruno Haible <=
- Re: [bug-gnulib] inline.m4: use compiler, not cpp, Paul Eggert, 2006/11/14