Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Keith M Wesolowski <wesolows@foobazco.org>
To: Tom Appermont <tea@sonycom.com>
Cc: linux-mips@oss.sgi.com
Subject: Re: Binary compatibility break understood ?
Date: Fri, 11 May 2001 02:26:27 -0700	[thread overview]
Message-ID: <20010511022627.A17202@foobazco.org> (raw)
In-Reply-To: <20010511095628.D8495@sonycom.com>; from tea@sonycom.com on Fri, May 11, 2001 at 09:56:28AM +0200

On Fri, May 11, 2001 at 09:56:28AM +0200, Tom Appermont wrote:

> To avoid any further confusion, which then are the versions 
> ( & patches ) of binutils / gcc / libc needed to get a
> linux mips toolchain we can use until the end of time? 

I routinely publish just such a thing at
oss.sgi.com:/pub/linux/mips/mips-linux/simple/crossdev.  Many others
publish similar toolchains regularly - see the list archives for
pointers.  None of them have expiration dates; you are free to use
them forever.  If you never change software you'll never lose binary
compatibility.  Likewise, you'll never get any bug fixes or new
features either.

If you mean a set of tools and libraries with which everything in the
future will always be binary compatible, we should talk - I have a
very attractive bridge I'm looking to get rid of.

Binary compatibility is irrelevant in a source-enabled world and
exists only long enough to make sure the previous release that broke
compatibility finishes compiling before the next such release comes
out.

-- 
Keith M Wesolowski <wesolows@foobazco.org> http://foobazco.org/~wesolows
------(( Project Foobazco Coordinator and Network Administrator ))------
	"Nothing motivates a man more than to see his boss put
	 in an honest day's work." -- The fortune file

  reply	other threads:[~2001-05-11  9:26 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-05 12:47 Binary compatibility break understood ? Florian Lohoff
2001-05-07 19:32 ` Ralf Baechle
2001-05-08 18:25   ` Florian Lohoff
2001-05-09  0:43     ` Ralf Baechle
2001-05-09  7:59       ` Tom Appermont
2001-05-09  8:46         ` Florian Lohoff
2001-05-09 12:14           ` Steven J. Hill
2001-05-09 12:27             ` Andreas Jaeger
2001-05-09 12:51               ` Steven J. Hill
2001-05-09 12:45                 ` Andreas Jaeger
2001-05-09 13:59                   ` Steven J. Hill
2001-05-09 13:49                     ` Andreas Jaeger
2001-05-09 14:06                       ` Steven J. Hill
2001-05-09 14:15                         ` Andreas Jaeger
2001-05-09 13:07                 ` Maciej W. Rozycki
2001-05-09 13:18                   ` Andreas Jaeger
2001-05-09 13:37                     ` Maciej W. Rozycki
2001-05-09 18:09                     ` Ralf Baechle
2001-05-09 18:59                       ` Maciej W. Rozycki
2001-05-09 19:16                         ` Ralf Baechle
2001-05-09 19:43                           ` Maciej W. Rozycki
2001-05-10  2:11                             ` Ralf Baechle
2001-05-09 19:17                       ` Steven J. Hill
2001-05-09 19:24                         ` Ralf Baechle
2001-05-10 18:08             ` Ryan Murray
2001-05-10 19:22               ` Ralf Baechle
2001-05-11  7:56                 ` Tom Appermont
2001-05-11  9:26                   ` Keith M Wesolowski [this message]
2001-05-11 10:42                     ` Tom Appermont

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=20010511022627.A17202@foobazco.org \
    --to=wesolows@foobazco.org \
    --cc=linux-mips@oss.sgi.com \
    --cc=tea@sonycom.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