Hello Alexandre,
Alexandre Oliva <[EMAIL PROTECTED]> wrote:
AO> On Mar 29, 2000, Paul Sokolovsky <[EMAIL PROTECTED]> wrote:
>> But what was the problem with gcc in the first place?
AO> The problem was that, since the compiler would implicitly link in
AO> certain libraries, libtool couldn't apply whatever mechanisms it uses
AO> to verify whether the libraries are shared or not, where appropriate.
AO> And this is indeed necessary on some platforms.
Aha, keyword is "some platforms".
AO> Fortunately, thanks mainly to Ossama Othman, this will all be fixed in
AO> libtool 1.5, which is under development in the libtool multi-language
Oh, it seem it'll be a long time ;-) Or maybe I misunderstand
version numbering? What I have from MAIN CVS written 1.3d in NEWS.
What will be next - 1.4 made from MAIN CVS? And next - 1.5 from ML
CVS? Or 1.5 will be released when ML branch will be merged with main?
Anyway, if I'm interested in developing libtool, am I suggested
to look, or maybe even base, on ML branch?
AO> branch. Hopefully, when that work is completed, we'll always be able
AO> to use GCC to link libraries and programs, since libtool will learn
AO> which objects and libraries GCC links in, and will behave as
AO> appropriate.
That's nice. What I'd like to do now is try to make up-to-seamless
support for win32 dlls. I'm glad to know that there's no problem
with using gcc to link on *that platform*.
AO> --
AO> Alexandre Oliva Enjoy Guaran�, see http://www.ic.unicamp.br/~oliva/
--
Paul Sokolovsky, IT Specialist
http://www.brainbench.com/transcript.jsp?pid=11135
