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
