Re: [bug-gnulib] inline.m4: use compiler, not cpp

[Bruno Haible]

Paul Eggert wrote:
> A downside of this approach is that if I compile the xalloc module
> with optimization (so that it does not bother to to generate a extern
> xmalloc function, but simply assumes it's inline) but then compile an
> xalloc user without optimization (so that it assumes there's an extern
> xmalloc function), then the build won't link.

Right. And unfortunately, a link error is more troublesome than a few
out-of-line copies of a function. Therefore I'd say, it's more important
that HAVE_INLINE stays constant across the entire compilation, than that
it's defined in a locally optimal way.

If you want to force it to a certain value, I think we can consider a
--enable/--disable-inlining configure option.

> But that's OK with me; 
> I can deal with that, just as I can deal with other problems that
> arise when I change CFLAGS without rerunning 'configure'.

How would you deal with such a link error situation? Is that something than
can be automated or explained to someone who doesn't know the sources well?

Bruno