Delivered-To: listarch-cygwin AT sourceware DOT cygnus DOT com Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com Message-Id: <199902131802.MAA20124@modi.xraylith.wisc.edu> X-Authentication-Warning: modi.xraylith.wisc.edu: LOCALHOST.xraylith.wisc.edu [127.0.0.1] didn't use HELO protocol To: DJ Delorie cc: cygwin AT sourceware DOT cygnus DOT com Subject: Re: ld, dlls, and windows libraries In-reply-to: Your message of "Sat, 13 Feb 1999 12:51:58 EST." <199902131751 DOT MAA26487 AT envy DOT delorie DOT com> Date: Sat, 13 Feb 1999 12:02:07 -0600 From: Mumit Khan DJ Delorie writes: > It's in our master sources, it's all a matter of when we do the next > full beta. I'm not sure about the "--export-all" part; you may need > to do "-Wl,--export-all" as that's a linker-specific option. Unless > someone wants to get it into egcs (hint). I have it in my local sources, but I haven't submitted it yet. I'm trying to figure out a way currently to have both the existing and the new method coexist in the SPECS, and my conditionals came out wrong last time I tried. Basically, it's a nested conditional based on whether '--dll' or '--shared' is specified. Any idea what I should call the --export-all option when invoked via GCC? Leave as is or something else like -mexport-all?? GCC specs will essentially translate this to --export-all when calling the linker. > It's *supposed* to only export non-static functions, not non-static > data. Ah, yes. Thanks. Regards, Mumit