[Top][All Lists]

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

Re: libtool-2.0 release [WAS per-deplib static/dynamic flags]

From: Bob Friesenhahn
Subject: Re: libtool-2.0 release [WAS per-deplib static/dynamic flags]
Date: Thu, 2 Feb 2006 10:53:35 -0600 (CST)

On Thu, 2 Feb 2006, Gary V. Vaughan wrote:

According to:, the
three remaining release blockers for 2.0 are:

* <!> libtool.m4 macro ordering/requirement audit. pending
* <!> LT_WITH_LTDL should build libltdl by default; currently
      nothing happens unless LTDL_CONVENIENCE or LTDL_INSTALLABLE
      is also given.
* <!> fix potential denial of service with compilers that do not
      understand "-c -o".
      * not very likely to happen

I know that Ralf is aware of a few more release-blocking issues than these. One of them is to be able to libtoolize with a libltdl directory using the non-recursive option and end up with a subordinate which works. Currently the generated takes some hand-tweaking.

I have also noticed some disturbing "leakage" of default compiler (GCC) path information into the build which causes -m64 to not work properly (at least under Solaris, but seems likely to impact other targets as well). This bug did not used to exist on the 2.0 branch. In my test case, the compiler is always run via a shell script wrapper (gcc-64) which always runs gcc with -m64 so I am not sure what libtool did to encourage gcc to undo the effect of that option.

I have been re-libtoolizing various projects with libtool 2.0 and have encountered resounding success with MinGW (very good!).

Bob Friesenhahn
GraphicsMagick Maintainer,

reply via email to

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