Ralf Wildenhues mailto:[EMAIL PROTECTED] wrote:
Hello Markus,
* Duft Markus wrote on Fri, Jan 19, 2007 at 05:28:41PM CET:
Sorry, i must correct myself. $EXEEXT *is* used *sometimes* and as
far as my situation is concerned, completely in the wrong places...
Well, it matches the Cygwin
Hi Ralf, Chuck,
I am a bit wary that it may cause regressions in users' packages, as
they may be using LT_SCOPE. But I see that with the other change, this
is needed.
User-package use of internal libtool macros (e.g. LT_SCOPE) is outside
libtool's control.
Hmm, yes. I've never
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
* Duft Markus wrote on Tue, Jan 30, 2007 at 09:02:24AM CET:
Ralf Wildenhues mailto:[EMAIL PROTECTED] wrote:
* Duft Markus wrote on Fri, Jan 19, 2007 at 05:28:41PM CET:
Sorry, i must correct myself. $EXEEXT *is* used *sometimes* and as
far as my situation is concerned, completely in the
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Charles Wilson on 1/30/2007 10:10 PM:
Hello everyone,
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
