Re: configure.lineno and config.status

[Ralf Wildenhues]

Hi Eric,

* Eric Blake wrote on Mon, Oct 27, 2008 at 07:22:37PM CET:
> So, even though config.status has code in place to check for a broken
> lineno, the check passes rather than fails, because it doesn't contain
> instances of $LINENO any more; also, error messages printed on behalf
> of config.status are reported from the line number in configure where
> the message was generated in the here-doc, rather than the resulting
> line number in config.status.  And even though I was expecting the
> creation of config.status.lineno, it was never created.

FWIW, I remember config.status.lineno files being generated whiles ago
(but maybe that was a bug?).

> For the unquoted here-docs used to generate config.status, I suppose we could 
> use m4_pushdef([LINENO], [LINE${empty}NO]) for the duration of the here-doc, 
> to 
> force the resulting config.status to have a literal $LINENO that bypassed the 
> configure.lineno sed script, and make the config.status.lineno generation 
> trigger.

Please don't.  Reread the bug about large here documents in the Autoconf
manual node Here-Documents, about expanding ${mpty} at block boundaries.
That was an ugly bug to debug, let's not go there again.

Cheers,
Ralf