Re: removed many uses of HAVE_CONFIG_H from gnulib

2006-09-26 Thread Eric Blake
Paul Eggert CS.UCLA.EDU> writes: > > 2006-09-13 Paul Eggert cs.ucla.edu> > > * _fpending.c: Include unconditionally, since we no > longer worry about uses that don't define HAVE_CONFIG_H. Done likewise for the verror module. That leaves xasprintf, xstrndup, and xvasprintf as

Re: [bug-gnulib] removed many uses of HAVE_CONFIG_H from gnulib

2006-09-15 Thread Ralf Wildenhues
Hello Bruno, * Bruno Haible wrote on Fri, Sep 15, 2006 at 02:31:22PM CEST: > Ralf Wildenhues wrote: > > CVS Libtool's libltdl allows third-party user code to decide over the > > naming of the config header file it may share with it (and whether to > > use one) > The only project I know of which u

Re: [bug-gnulib] removed many uses of HAVE_CONFIG_H from gnulib

2006-09-15 Thread Bruno Haible
Ralf Wildenhues wrote: > CVS Libtool's libltdl allows third-party user code to decide over the > naming of the config header file it may share with it (and whether to > use one) Gettextize doesn't allow this choice, when including intl/ as a subdirectory, and I'm not aware that anybody complained

Re: removed many uses of HAVE_CONFIG_H from gnulib

2006-09-14 Thread Paul Eggert
Ralf Wildenhues <[EMAIL PROTECTED]> writes: > * Paul Eggert wrote on Thu, Sep 14, 2006 at 12:41:51AM CEST: >> Since nobody needs HAVE_CONFIG_H any more, [...] > > What makes you reach this conclusion (for third-party packages, not for > some well-maintained GNU packages)? I did a Google search "D

Re: [bug-gnulib] removed many uses of HAVE_CONFIG_H from gnulib

2006-09-14 Thread Bruno Haible
Paul Eggert wrote: > Since nobody needs > HAVE_CONFIG_H any more, I installed the following change into gnulib. I did the same for these files. 2006-09-14 Bruno Haible <[EMAIL PROTECTED]> * lib/allocsa.c: Include unconditionally. * lib/asnprintf.c: Likewise. * lib/aspr

Re: removed many uses of HAVE_CONFIG_H from gnulib

2006-09-13 Thread Ralf Wildenhues
Hello Paul, * Paul Eggert wrote on Thu, Sep 14, 2006 at 12:41:51AM CEST: > Since nobody needs HAVE_CONFIG_H any more, [...] What makes you reach this conclusion (for third-party packages, not for some well-maintained GNU packages)? Why was there a need at one time but not now? > If this is a re

Re: removed many uses of HAVE_CONFIG_H from gnulib

2006-09-13 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Paul Eggert on 9/13/2006 4:41 PM: > > If this is a real problem for anybody (which I think it won't be), > we can define a new no-config-h module which reverses the change. The only real problem I had was this typo, with the fix checked