Cleaning up libtool.m4, ltdl.m4 and configure.ac (Was: Re: FYI: Fixlet for missing braces around sys_search_path)

[Dalibor Topic]

Ralf Wildenhues wrote:
> Hi Dalibor,
>
> * Dalibor Topic wrote on Thu, Apr 28, 2005 at 06:20:34PM CEST:
>
> > here is another patch from Kaffe's libtool patch chest, which adds the 
> > missing braces around $sys_search_path in the definition of 
> > LTDL_SYSSEARCHPATH. That fixes libtool for at least one platform, though 
> > I don't recall which any more :(
>
>
> That does not matter.  I hate inconsistent macro option quoting, one
> should do it even for the trivial cases just to get used to it, because
> the times when an option should _not_ be quoted are very much exceptions
> and should IMNSHO be clearly documented so.

Moin Ralf,

Thanks a lot for fixing the quotes on all of them!

On a side note, would there be some interest in patches cleaning up 
libtool.m4 / ltdl.m4 for autoconf 2.59 warnings? I run the latest 
released autotools with -Wall in kaffe's developers/autgen.sh script, 
and a lot of the pages and pages of warnigns for deprecated autoconf 
constructs come from libtool.m4. :(

Unfortunately, while it is possible to simply autoupdate configure.ac 
and ltdl.m4 (by calling it configure.ac) [1], it is not possible to 
autoupdate libtool.m4 as the hacks around the lack of support for the 
java language in autoconf seem to whack autoupdate into some endless m4 
loop. Well, at least 17 h long loop that I chose to terminate this 
morning :)

My amateur suggestion would be to try to split libtool.m4 into several 
m4 files, like gettext does it for their m4 macros. That would make 
autoupdating parts of it at least feasible.

> Many thanks for reporting all these bugs.  Are there any other
> libtool-related patches you have in kaffe?  (The static *BSD dlopen bug
> is still open, I don't know yet how to fix it.)

Those were the three ones I had for 1.5. Thanks for the fast reply!

cheers,
dalibor topic

[1] autoupdate makes the updated files require autoconf 2.59, though, I 
don't know if that's a problem for the 1.5 branch.