libtool
[Top][All Lists]
Advanced

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

Re: conditionally disabling libltdl subconfigure


From: Nick Bowler
Subject: Re: conditionally disabling libltdl subconfigure
Date: Wed, 22 Aug 2012 15:05:48 -0400
User-agent: Mutt/1.5.21 (2010-09-15)

On 2012-08-22 20:26 +0200, Brice Goglin wrote:
> Le 22/08/2012 19:44, Nick Bowler a écrit :
> > On 2012-08-22 18:32 +0200, Brice Goglin wrote:
> >> Le 22/08/2012 16:32, Nick Bowler a écrit :
[...]
> > Other than adding -I$(top_builddir) to CPPFLAGS, as a workaround you
> > could probably add something like this just before AC_OUTPUT (untested):
> >
> >   LT_CONFIG_H=`expr "$LT_CONFIG_H" : '.*/\(.*\)'`
> >
> 
> Your analysis looks correct but the workaround doesn't seem to work. It
> looks like LT_CONFIG_H is set inside AC_OUTPUT.

Indeed, it looks like LT_CONFIG_H is set using AC_CONFIG_COMMANDS_PRE,
so it does in fact get set "inside" AC_OUTPUT.  I guess you could write

  AC_CONFIG_COMMANDS_PRE([LT_CONFIG_H=`expr "$LT_CONFIG_H" : '.*/\(.*\)'`])

and hope that it runs after libltdl's registration.  Unfortunately,
the autoconf manual does not appear to specify the order in which
multiple AC_CONFIG_COMMANDS_PRE registrations are run, so this might not
be the most robust approach.  Perhaps someone on the autoconf list can
clarify.

It would be prudent to report the issue to the address@hidden
mailing list, ideally with a small test case.  Obviously if you can wait
for an upstream fix and avoid any hack workarounds for old versions
that'd be ideal...

Cheers,
-- 
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)




reply via email to

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