Clint Adams wrote:

>>BTW anybody else working on 2.50? Else I hope to produce new configure.ac
>>next week. I cannot promise to resolve this issue with current configure.in
>>though (unless it happens as a side effect).
>>
> 
> If you remove the hunk beginning with
> 
> dnl The standard config.status is missing some essential features.
> dnl So add them now.  See the comment at the end of Src/mkmakemod.sh.
> 
> config.status will be happier.  I haven't looked into why.
> 
> 


"Curiouser and curiouser!" cried Alice.

Anyway - 2.50 generates totally different config.status and our 
modification breaks it. Moreover, as Akim said, 2.50 does not need this 
mod anymore. But what's worse - mkmakemod.sh relies on our mod so if we 
just leave it out it does not work any more :-) It does not work anyway 
because check for dynamic build does not work with 2.50 ...

Here is patch that

- checks for autoconf version. It thinks that anything <= 2.13 needs our 
hack, anything over - does not. It breaks with beta autoconf versions 
like 2.49f. It smells.

- adds a string to config.status and lets mkmakemod.sh grep for it to 
decide when to use this hack.

- adds check for 2.50-like subst's (t check for dynamic build).

This is intended for 4.0.x only, and just to allow some poor soul to 
compile off CVS when we advice it without much fuss. And to allow me to 
build both 4.0.x and HEAD without maintaining two autoconf versions. :-) 
This is an absolute hack. Should I commit it?

-andrej

P.S. I just built freshly checked out 4.0 branch in sepearate build 
directory with these mods.

P.P.S. 2.50 seems to not use cache by default - you need explicit option 
--cache-file (or --config-cache to default to config.cache). One more 
change in Makefiles.