[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Reliance on <config.h>

From: Ralf Wildenhues
Subject: Re: Reliance on <config.h>
Date: Tue, 28 Aug 2007 18:36:26 +0200
User-agent: Mutt/1.5.16 (2007-07-25)

Hello Ludovic,

* Ludovic Courtès wrote on Tue, Aug 28, 2007 at 02:32:12PM CEST:
> address@hidden (Ludovic Courtès) writes:
> > Ralf Wildenhues <address@hidden> writes:
> >
> >> Another possibility is to generate lib/config.h.in from
> >> some-special-name.h.in, say, by some sed script or an autoheader
> >> invocation with arguments and output redirection.
> >
> > Good point.  I ended up using `AC_CONFIG_LINKS' to have a `config.h'
> > linked to `some-special-name.h'.
> Actually, it just occurred to me that `AC_CONFIG_LINKS' doesn't work
> here when builddir != srcdir, because both the source and destination of
> the link (namely `some-special-name.h' and `config.h') are under
> builddir, whereas `AC_CONFIG_LINKS' looks for the source file under
> `srcdir'.

AFAIR, this bug of AC_CONFIG_LINKS has been fixed in CVS Autoconf
but not yet in 2.61a.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]