[Top][All Lists]

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


From: Ralf Wildenhues
Subject: Re: Calling AC_CONFIG_HEADERS from LT_INIT?
Date: Fri, 23 Sep 2005 18:39:39 +0200
User-agent: Mutt/1.5.9i

Hi Gary,

* Gary V. Vaughan wrote on Fri, Sep 23, 2005 at 06:17:48PM CEST:
> I think this represents a thinko in the way LT_INIT decides
> whether to call AC_CONFIG_HEADERS, but I'm not sure I follow
> what the intention is supposed to be.  Could you enlighten me?

Well, it was you that introduced the code into Libtool, I only "fixed"
it, in the sense that it worked with documented Autoconf interfaces.

*snip code*

(In the example, you should have run autoheader...
or plainly: autoreconf; but I see your point)

> How do we fix this code to DTRT (and I'm not sure what TRT is!):
> # In order that ltdl.c can compile, run AC_CONFIG_HEADERS for the user
> # if they did not call it themself.  This is so that ltdl.h can pick up
> # the parent projects config.h file, The first file in AC_CONFIG_HEADERS
> # must contain the definitions required by ltdl.c.

Well, first I believed you introduced this so libltdl can work as
non-subpackage.  In _that_ case, surely libltdl needs to know the name
of the config header.  I'm not sure it would need to _call_
AC_CONFIG_HEADERS if the parent package does not use AC_CONFIG_HEADERS
itself.  I assumed you found some reason when introducing the behavior?
If not: let's just remove the call to AC_CONFIG_HEADERS in ltdl.m4.

This answers part of your question, I think.  The other part is: if
libltdl is a subpackage.  Then, fussing with AC_CONFIG_HEADERS at all is
none of our business.  :-)

Would you agree?


reply via email to

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