Q: generate config.h.in automatically (was: Re: [PATCH] intl: reintroduce unintentionally disabled optimization)

[Dmitry V. Levin]

On Mon, Feb 22, 2016 at 03:05:47PM +0100, Florian Weimer wrote:
> * Dmitry V. Levin:
> >> Is config.h.in regenerated by autoreconf and similar tools?
> >
> > No, it's supported manually and therefore permanently out of sync.
> > For example,
> >
> > $ grep -i strerror config.h.in 
> > #undef	HAVE_STRERROR
> > #define	HAVE_STRERROR	1
> > find -name configure.ac | xargs grep -i strerror | wc -l
> > 0
> 
> Can we have autoreconf automatically generate config.h.in, like other
> GNU projects do?

I suppose we can use autoheader like other projects do.

I can't recollect why don't we use it in the first place.  Is there
anybody around who can sched some light on the history of not using
autoheader in glibc?


-- 
ldv
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://sourceware.org/pipermail/libc-alpha/attachments/20160222/14c5aa7a/attachment.sig>