[Top][All Lists]

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

Re: libltdl exports no symbols (cygwin)

From: Ralf Wildenhues
Subject: Re: libltdl exports no symbols (cygwin)
Date: Tue, 30 Jan 2007 20:29:48 +0100
User-agent: Mutt/1.5.13 (2006-08-11)

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.  The patches
were not introduced to fix a regression, rather something that we can
see as an improvement, i.e., a /new/ feature, but they cause regressions
for others.  I would like 1.5.24 to be a no-brainer for users, and I
would like to do it soon if possible.  If we require changes in user's
code, then it's better to make the change when going to 2.0; it's easier
for them if all changes occur at once.  And I'm easier with having
Gettext require HEAD Libtool than all users of libltdl.

For HEAD, guys, if you want this really fixed then may I suggest to take
another look at Bruno's suggestions:
Any way we go, we should do something more consistent than "you cannot
rely on auto-imports if you use libltdl".  And certainly we should
document user-level-required changes in NEWS.

Comments and suggestions appreciated.

Cheers, and thanks,

reply via email to

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