This is the mail archive of the
cygwin-apps@cygwin.com
mailing list for the Cygwin project.
Re: ld --auto-import for cygwin and libtool
- To: CA List <Cygwin-Apps at Cygwin dot Com>
- Subject: Re: ld --auto-import for cygwin and libtool
- From: Mumit Khan <khan at NanoTech dot Wisc dot EDU>
- Date: Mon, 23 Jul 2001 10:53:55 -0500 (CDT)
On Mon, 23 Jul 2001, Earnie Boyd wrote:
> > It's possible that I might be convinced to include Paul's patches in the
> > next binutils release if they are not incorporated into the official
> > release. However, I would rather use the official CVS release, if
> > possible.
> >
>
> Don't be too hastily convinced. I believe there to be problems of
> exporting too much in lots of cases.
For those porting from Unix, that's the expected state of affairs, and
usually things just work. However, Earnie's right that it may cause
problems because of the way Windows DLL linking works -- all symbols
must be resolved at link time, not at run time, and this may cause
the incorrect symbol to be resolved if there are multiple DLLs exporting
symbols with the same name (quite common in Unix based software, and
sometimes by design). Also potentially cause all sorts of multiple symbol
errors.
Earnie, do you have a test case where this is a problem? I've been trying
to come up with a simple few liner one, but it's just not happening.
Of course, since it won't be turned on by default, what's the harm?
Provided of course it's not adding bugs when it's *not* enabled.
Regards,
Mumit