libtool-patches
[Top][All Lists]
Advanced

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

Re: changing compiler flags at configure time


From: Ralf Wildenhues
Subject: Re: changing compiler flags at configure time
Date: Tue, 13 Jun 2006 15:33:29 +0200
User-agent: Mutt/1.5.11

Hi Eric,

* Eric Blake wrote on Tue, Jun 13, 2006 at 03:26:25PM CEST:
> According to Ralf Wildenhues on 6/13/2006 6:49 AM:
> > 
> > Thanks for helping!
> 
> Thanks for the feedback. It will be a while before I can incorporate it
> all (and most importantly, add a testsuite case to exercise it all), but I
> appreciate your first read of my hastily written first cut.

I may pick it up eventually; but I have a list of other things first,
so certainly won't mind being beaten to.

> Oops.  I originally tried:
> 
> m4_define([_LT_OBSOLETE], [AU_DEFUN([$1], [$2])
> AC_DIAGNOSE([obsolete])])
> 
> But that killed aclocal.  I guess I didn't re-update changelog.

What's more is, you don't need that.  Autoconf has all the obsoletion
machinery in place already.

> > Why not just AU_ALIAS([AC_ENABLE_SHARED], [LT_ENABLE_SHARED])?
> > (four instances)
> > Except of course that AU_ALIAS is broken before Autoconf 2.59c, 
> 
> So should we just make libtool 2.0 AC_REQUIRE([2.59d])?

Not now, if we can avoid it.  I don't want to tighten the dependency
chain around the user's neck more than necessary.  In case you didn't
see this fleeting by: there are distributors out there patching Libtool
1.5.x to run with Autoconf 2.13...

Cheers,
Ralf




reply via email to

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