From: DJ Delorie <dj@delorie.com>
To: jason@cygnus.com
Cc: egcs@cygnus.com
Subject: Re: Wanted: ETA for working friendly template support in EGCS.
Date: Wed, 03 Feb 1999 08:26:00 -0000 [thread overview]
Message-ID: <199902031626.LAA25613@envy.delorie.com> (raw)
In-Reply-To: < u9n22vu2k9.fsf@yorick.cygnus.com > (message from Jason Merrill on03 Feb 1999 03:52:38 -0800)
> But it does work in NT. PE has .linkonce, which is roughly equivalent to
> what we do on ELF. Does DJGPP support .linkonce?
DJGPP currently uses binutils 2.8.1 - was support in there? Is it in
binutils-2.9.1?
WARNING: multiple messages have this Message-ID
From: DJ Delorie <dj@delorie.com>
To: jason@cygnus.com
Cc: egcs@cygnus.com
Subject: Re: Wanted: ETA for working friendly template support in EGCS.
Date: Sun, 28 Feb 1999 22:53:00 -0000 [thread overview]
Message-ID: <199902031626.LAA25613@envy.delorie.com> (raw)
Message-ID: <19990228225300.LqLb9GM8dkjie6bGNpmCjCsAVAh6v3jYAh7kFJ1mynk@z> (raw)
In-Reply-To: <u9n22vu2k9.fsf@yorick.cygnus.com>
> But it does work in NT. PE has .linkonce, which is roughly equivalent to
> what we do on ELF. Does DJGPP support .linkonce?
DJGPP currently uses binutils 2.8.1 - was support in there? Is it in
binutils-2.9.1?
next prev parent reply other threads:[~1999-02-03 8:26 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3.0.6.32.19990202201918.007fabb0@pop.netaddress.com>
[not found] ` <8936.918004642@hurl.cygnus.com>
1999-02-02 18:15 ` Paul Derbyshire
[not found] ` < 3.0.6.32.19990202211508.0092cb00@pop.netaddress.com >
1999-02-02 18:28 ` Jeffrey A Law
1999-02-28 22:53 ` Jeffrey A Law
[not found] ` <9120.918008699.cygnus.egcs@hurl.cygnus.com>
[not found] ` <36B7D8D4.7A7F1028@delorie.com>
1999-02-03 3:52 ` Jason Merrill
[not found] ` < u9n22vu2k9.fsf@yorick.cygnus.com >
1999-02-03 7:35 ` Mumit Khan
[not found] ` < Pine.SUN.3.93.990203093359.28218C-100000@modi.xraylith.wisc.edu >
1999-02-03 14:12 ` Mark E.
[not found] ` < 36b8c8c2.1604849@smtp1.ibm.net >
1999-02-03 14:21 ` Richard Henderson
1999-02-28 22:53 ` Richard Henderson
1999-02-28 22:53 ` Mark E.
1999-02-28 22:53 ` Mumit Khan
1999-02-03 8:26 ` DJ Delorie [this message]
1999-02-03 11:21 ` Jason Merrill
[not found] ` < u9iudjthrm.fsf@yorick.cygnus.com >
1999-02-03 11:24 ` DJ Delorie
1999-02-28 22:53 ` DJ Delorie
1999-02-28 22:53 ` Jason Merrill
1999-02-28 22:53 ` DJ Delorie
1999-02-28 22:53 ` Jason Merrill
1999-02-28 22:53 ` Paul Derbyshire
[not found] <199902032255.OAA19389@kankakee.wrs.com>
1999-02-04 10:19 ` Mark E.
1999-02-28 22:53 ` Mark E.
1999-02-02 18:10 Paul Derbyshire
1999-02-28 22:53 ` Paul Derbyshire
-- strict thread matches above, loose matches on Subject: below --
1999-02-02 17:44 Mike Stump
1999-02-28 22:53 ` Mike Stump
1999-02-02 16:38 Paul Derbyshire
[not found] ` < 3.0.6.32.19990202193758.007f1d80@pop.netaddress.com >
1999-02-02 16:44 ` Jeffrey A Law
[not found] ` < 8772.918002415@hurl.cygnus.com >
1999-02-04 13:26 ` J. Kean Johnston
1999-02-28 22:53 ` J. Kean Johnston
1999-02-28 22:53 ` Jeffrey A Law
1999-02-02 16:52 ` Zack Weinberg
[not found] ` < 199902030052.TAA08307@rabi.phys.columbia.edu >
1999-02-02 18:08 ` Paul Derbyshire
1999-02-28 22:53 ` Paul Derbyshire
1999-02-28 22:53 ` Zack Weinberg
1999-02-28 22:53 ` Paul Derbyshire
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=199902031626.LAA25613@envy.delorie.com \
--to=dj@delorie.com \
--cc=egcs@cygnus.com \
--cc=jason@cygnus.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).