Mail Archives: cygwin/2008/04/13/23:45:18
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Charles Wilson wrote:
| I believe this was an attempt at optimization: avoid testing for
| specific tools need only on one platform, unless libtool has been told
| that it is ON that platform. Oddly, you'd think that libtool would
| figure that out from $build/$host/$target, and not [win32-dll].
More than that, is AC_LIBTOOL_WIN32_DLL (now [win32-dll]) actually
necessary anymore? Cygwin doesn't need it, but I don't know about MinGW.
| Which is also odd. I wonder why linux uses objdump...maybe this is a
| dead code path?
I'm not sure; AFAICS such a test didn't exist for linux in libtool 1.5.
| [*] Having heard no objections, and a few votes in favor, I'm leaning
| towards replacing both libtool1.5 and libtool2.2 with a single
| "libtool" package, with 1.5-derived versions remaining "curr:" for the
| near-term.
With my patch to libtool and some tweaking of cygport, libtool 2.2 seems
to be working pretty well. I will need to know your final decision
before committing the cygport patches, and I'll try to push an update as
soon as possible thereafter.
Yaakov
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFIAtMzpiWmPGlmQSMRCE3eAJ9mQXitBbfqWUnLRFL7HmalQaG2fgCeLd/A
yA/G/Orc2yZcwB7GVikWUI4=
=N1Er
-----END PGP SIGNATURE-----
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -