[Top][All Lists]

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

Re: libltdl exports no symbols (cygwin)

From: Bob Friesenhahn
Subject: Re: libltdl exports no symbols (cygwin)
Date: Tue, 30 Jan 2007 23:43:34 -0600 (CST)

On Wed, 31 Jan 2007, Charles Wilson wrote:

Ralf Wildenhues wrote:
Hello Eric, Charles, all,

* Eric Blake wrote on Tue, Jan 30, 2007 at 06:00:00PM CET:
Should we also mention the side effect that you must now mark
explicit exports, since you can no longer rely on auto-imports?

This whole issue seems not good for branch-1-5.  I'm pondering backing
out all related changes from branch-1-5; that is, the NEWS update and
the LT_GLOBAL_DATA/LT_SCOPE change of 2007-01-28, as well as the
DLL_EXPORT change of 2006-06-01.  We cannot do such a big change for
1.5.24, that will affect all users of --with-included-ltdl.

And this decision solves the problem for MinGW how? Remember that part of the justification for the 2006-06-01 change was that at least that way, we have the same behavior on all win32 variants. If you revert 2006-06-01, cygwin != mingw, and mingw still #defines DLL_EXPORT for all "PIC" -- which would simply push CVS M4's problems into the future, when somebody tries to compile it on MinGW.

I agree that it does not make sense to change the behavior of libtool in order to accommodate the development version of one package. The only packages that libtool must pay homage to are autoconf and automake. Restrictions are good if they help assure the overall portability of dependent packages going into the future.

It seems that this one package (albeit an important one) has made some wrong assumptions and should either require CVS libtool (if it works) or correct the wrong assumptions and use a different approach. If CVS libtool ever gets released, then it may become a non-issue.

Bob Friesenhahn
GraphicsMagick Maintainer,

reply via email to

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