Mailing-List: contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm Sender: cygwin-apps-owner AT sourceware DOT cygnus DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com X-Authentication-Warning: hp2.xraylith.wisc.edu: khan owned process doing -bs Date: Mon, 23 Jul 2001 10:53:55 -0500 (CDT) From: Mumit Khan To: CA List Subject: Re: ld --auto-import for cygwin and libtool In-Reply-To: <3B5C2779.A26BC5FF@yahoo.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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