Re: autoheader question

2000-04-25 Thread Akim Demaille
| > The problem was that Lars was AC_DEFINE($var), which unfortunately | > is not extensible in 2.13. It is now, and autoheader, IMHO, achieves | > that end for both the maintainer, *and* the end user. I personally | > consider it is a requirement that all the #undef templates be | > documented

Re: autoheader question

2000-04-25 Thread Lars Hecking <[EMAIL PROTECTED]>
> The problem was that Lars was AC_DEFINE($var), which unfortunately > is not extensible in 2.13. It is now, and autoheader, IMHO, achieves > that end for both the maintainer, *and* the end user. I personally > consider it is a requirement that all the #undef templates be > documented/described

Re: autoheader question

2000-04-25 Thread Akim Demaille
> "T" == T E Dickey <[EMAIL PROTECTED]> writes: T> the point would be to reduce effort (it appears that autoheader T> doesn't achieve that end) :P :) The problem was that Lars was AC_DEFINE($var), which unfortunately is not extensible in 2.13. It is now, and autoheader, IMHO, achieves tha

Re: autoheader question

2000-04-25 Thread T.E.Dickey
> > Hm, I might be over picky, but I would have answered no. autoheader > > 2.13 is including all the paragraphs which are related to something > > which is AC_DEFINE'd, which is not necessarily all the content of > > acconfig.h. > > What about AC_DEFINE_UNQUOTED? And, shouldn't autoheader

Re: autoheader question

2000-04-25 Thread Akim Demaille
> "Lars" == Lars Hecking <[EMAIL PROTECTED]> writes: >> Hm, I might be over picky, but I would have answered no. >> autoheader 2.13 is including all the paragraphs which are related >> to something which is AC_DEFINE'd, which is not necessarily all the >> content of acconfig.h. Lars> What a

Re: autoheader question

2000-04-25 Thread Lars Hecking
> Hm, I might be over picky, but I would have answered no. autoheader > 2.13 is including all the paragraphs which are related to something > which is AC_DEFINE'd, which is not necessarily all the content of > acconfig.h. What about AC_DEFINE_UNQUOTED? And, shouldn't autoheader check aclocal.m

Re: autoheader question

2000-04-25 Thread Akim Demaille
> "Alexandre" == Alexandre Oliva <[EMAIL PROTECTED]> writes: One thing I can't seem to figure out: if acconfig.h exists, is autoheader supposed to add all its contents to config.h.in? Alexandre> Yup >> Hm, I might be over picky, but I would have answered no. >> autoheader 2.13 is

Re: autoheader question

2000-04-25 Thread Alexandre Oliva
On Apr 25, 2000, Akim Demaille <[EMAIL PROTECTED]> wrote: >> "Alexandre" == Alexandre Oliva <[EMAIL PROTECTED]> writes: Alexandre> On Apr 25, 2000, Lars Hecking <[EMAIL PROTECTED]> wrote: >>> One thing I can't seem to figure out: if acconfig.h exists, is >>> autoheader supposed to add all its

Re: autoheader question

2000-04-25 Thread Akim Demaille
> "Alexandre" == Alexandre Oliva <[EMAIL PROTECTED]> writes: Alexandre> On Apr 25, 2000, Lars Hecking <[EMAIL PROTECTED]> wrote: >> One thing I can't seem to figure out: if acconfig.h exists, is >> autoheader supposed to add all its contents to config.h.in? Alexandre> Yup Hm, I might be ove

Re: autoheader question

2000-04-25 Thread Mo DeJong
Perhaps this is a stupid question, but did you remember to add the following to the top of your configure.in file? I made a simmilar mistake when writing my configure.in. AC_CONFIG_HEADER(config.h) Mo Dejong Red Hat Inc. On Tue, 25 Apr 2000, Lars Hecking wrote: > > $ autoheader --version > Au

Re: autoheader question

2000-04-25 Thread Alexandre Oliva
On Apr 25, 2000, Lars Hecking <[EMAIL PROTECTED]> wrote: > One thing I can't seem to figure out: if acconfig.h exists, is > autoheader supposed to add all its contents to config.h.in? Yup > And if this doesn't happen, is there a way to find out why? Run it with `sh -x'. -- Alexandre Oliva