From: Joe Buck <jbuck@synopsys.com>
To: pkoning@xedia.com (Paul Koning)
Cc: jbuck@synopsys.com, jhpb@sarto.gaithersburg.md.us, egcs@cygnus.com
Subject: Re: need for flag for incompatible-changes
Date: Wed, 28 Jan 1998 12:09:00 -0000 [thread overview]
Message-ID: <199801282008.MAA03266@atrus.synopsys.com> (raw)
In-Reply-To: <9801281938.AA14865@kona.>
> If object files contained version numbers, you wouldn't have to break
> anything. (More precisely, you would only have to break things that
> are older than the oldest version you want to continue supporting in
> the linker.)
Where we have control over the linker (Linux, or platforms where GNU ld
will work), we could use the linker to handle some types of
incompatibilities. In many cases, I'm afraid that all it will lets
us do is say "sorry, incompatible object files".
next prev parent reply other threads:[~1998-01-28 12:09 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <January_28_1998_at_05_17_03_18503_Joseph_H._Buehler@altera>
1998-01-28 6:10 ` Joseph H. Buehler
1998-01-28 9:12 ` Joe Buck
1998-01-28 14:23 ` Paul Koning
1998-01-28 12:09 ` Joe Buck [this message]
1998-01-28 15:03 ` Paul Koning
1998-01-29 14:41 ` Andi Kleen
1998-01-28 15:03 ` Jeffrey A Law
1998-01-28 15:03 Joe Buck
1998-01-29 6:24 ` Paul Koning
1998-01-29 11:20 ` Joe Buck
1998-01-29 11:20 ` Richard Henderson
1998-01-29 13:44 ` Joe Buck
1998-01-29 14:41 ` Paul Koning
1998-01-29 13:44 ` Joe Buck
1998-01-29 13:44 ` Paul Koning
1998-01-29 14:41 ` Fred Eisele
1998-01-29 16:16 ` Joe Buck
-- strict thread matches above, loose matches on Subject: below --
1998-01-27 19:15 Mike Stump
1998-01-27 16:18 Per Bothner
1998-01-27 16:52 ` Joe Buck
1998-01-27 17:03 ` Per Bothner
1998-01-27 19:15 ` Joe Buck
1998-01-28 7:10 ` Paul Koning
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=199801282008.MAA03266@atrus.synopsys.com \
--to=jbuck@synopsys.com \
--cc=egcs@cygnus.com \
--cc=jhpb@sarto.gaithersburg.md.us \
--cc=pkoning@xedia.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).