From: Mumit Khan <khan@xraylith.wisc.EDU>
To: DJ Delorie <dj@delorie.com>
Cc: cygwin@sourceware.cygnus.com
Subject: Re: ld, dlls, and windows libraries
Date: Sat, 13 Feb 1999 10:02:00 -0000 [thread overview]
Message-ID: <199902131802.MAA20124@modi.xraylith.wisc.edu> (raw)
In-Reply-To: Your message of "Sat, 13 Feb 1999 12:51:58 EST." < 199902131751.MAA26487@envy.delorie.com >
DJ Delorie <dj@delorie.com> 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
WARNING: multiple messages have this Message-ID
From: Mumit Khan <khan@xraylith.wisc.EDU>
To: DJ Delorie <dj@delorie.com>
Cc: cygwin@sourceware.cygnus.com
Subject: Re: ld, dlls, and windows libraries
Date: Sun, 28 Feb 1999 23:02:00 -0000 [thread overview]
Message-ID: <199902131802.MAA20124@modi.xraylith.wisc.edu> (raw)
Message-ID: <19990228230200.2vQocD3ZZKDAeLmLFt3dgyAad9quLHjskAC2MmrVkFY@z> (raw)
In-Reply-To: <199902131751.MAA26487@envy.delorie.com>
DJ Delorie <dj@delorie.com> 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
next prev parent reply other threads:[~1999-02-13 10:02 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-12 8:40 John Fortin
[not found] ` < 36C4582C.A302D915@ibm.net >
1999-02-12 9:56 ` Mumit Khan
1999-02-12 10:06 ` John Fortin
1999-02-28 23:02 ` John Fortin
[not found] ` < Pine.SUN.3.93.990212113933.18731B-100000@modi.xraylith.wisc.edu >
1999-02-12 16:53 ` Geoffrey Noer
1999-02-28 23:02 ` Geoffrey Noer
1999-02-13 9:28 ` Re[2]: " Paul Sokolovsky
[not found] ` < 1809.990213@is.lg.ua >
1999-02-13 9:52 ` Mumit Khan
1999-02-28 23:02 ` Mumit Khan
1999-02-13 9:52 ` DJ Delorie
[not found] ` < 199902131751.MAA26487@envy.delorie.com >
1999-02-13 10:02 ` Mumit Khan [this message]
1999-02-13 10:40 ` Re[2]: " Paul Sokolovsky
[not found] ` < 13857.990213@is.lg.ua >
1999-02-13 10:48 ` DJ Delorie
1999-02-28 23:02 ` DJ Delorie
1999-02-28 23:02 ` Re[2]: " Paul Sokolovsky
1999-02-28 23:02 ` Mumit Khan
1999-02-28 23:02 ` DJ Delorie
1999-02-28 23:02 ` Re[2]: " Paul Sokolovsky
1999-02-28 23:02 ` Mumit Khan
1999-02-28 23:02 ` John Fortin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=199902131802.MAA20124@modi.xraylith.wisc.edu \
--to=khan@xraylith.wisc.edu \
--cc=cygwin@sourceware.cygnus.com \
--cc=dj@delorie.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).