From: "Dave Korn" <dave.korn@artimi.com>
To: "'Mikhail Teterin'" <mi+kde@aldan.algebra.com>,
"'Jan-Benedict Glaw'" <jbglaw@lug-owl.de>
Cc: "'Daniel Jacobowitz'" <drow@false.org>, <binutils@sources.redhat.com>
Subject: RE: backward/forward compatibility of binutils
Date: Fri, 07 Jul 2006 15:40:00 -0000 [thread overview]
Message-ID: <00e901c6a1db$a99c2450$a501a8c0@CAM.ARTIMI.COM> (raw)
In-Reply-To: <200607071044.22680@aldan>
On 07 July 2006 15:44, Mikhail Teterin wrote:
> On Friday 07 July 2006 09:27, Jan-Benedict Glaw wrote:
> = Of course. I didn't mention that it would be a nice thing to have. I'm
> = actually opposed to it.
>
> Why not? How hard is it to keep API compatibility (no need for ABI)?
Fairly. If it was trivial, it would be that way already!
> Why do you insist on every tool bundling its own version?
Well, how about "Because if you bork your system shared libs, and you badly
need a get-out-of-jail-free card, having statically linked executables in your
toolchain may well save your life." ?
The toolchain binaries are so vital to the system that they should carry on
working no matter what else goes wrong. For me, that's well worth the
overhead of a bit of disk space. YMMV of course.
cheers,
DaveK
--
Can't think of a witty .sigline today....
next prev parent reply other threads:[~2006-07-07 15:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-07 6:50 Mikhail Teterin
2006-07-07 12:51 ` Jan-Benedict Glaw
2006-07-07 13:22 ` Daniel Jacobowitz
2006-07-07 13:28 ` Jan-Benedict Glaw
2006-07-07 14:44 ` Mikhail Teterin
2006-07-07 15:11 ` Daniel Jacobowitz
2006-07-07 15:32 ` Mikhail Teterin
2006-07-07 17:27 ` Ian Lance Taylor
2006-07-07 15:40 ` Dave Korn [this message]
2006-07-07 16:18 ` Mikhail Teterin
2006-07-07 16:30 ` Jan-Benedict Glaw
2006-07-07 16:39 ` Dave Korn
2006-07-07 18:42 ` Mikhail Teterin
2006-07-07 18:45 ` 'Daniel Jacobowitz'
2006-07-07 18:56 ` Mikhail Teterin
2006-07-07 18:58 ` 'Daniel Jacobowitz'
2006-07-07 19:02 ` Jan-Benedict Glaw
2006-07-07 19:46 ` Mikhail Teterin
2006-07-07 20:29 ` Jan-Benedict Glaw
2006-07-07 20:33 ` Ian Lance Taylor
2006-07-07 20:33 ` Christopher Faylor
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='00e901c6a1db$a99c2450$a501a8c0@CAM.ARTIMI.COM' \
--to=dave.korn@artimi.com \
--cc=binutils@sources.redhat.com \
--cc=drow@false.org \
--cc=jbglaw@lug-owl.de \
--cc=mi+kde@aldan.algebra.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).