From: Florian Lohoff <flo@rfc822.org>
To: Tom Appermont <tea@sonycom.com>
Cc: Ralf Baechle <ralf@oss.sgi.com>, linux-mips@oss.sgi.com
Subject: Re: Binary compatibility break understood ?
Date: Wed, 9 May 2001 10:46:35 +0200 [thread overview]
Message-ID: <20010509104635.D12267@paradigm.rfc822.org> (raw)
In-Reply-To: <20010509095955.A8392@sonycom.com>; from tea@sonycom.com on Wed, May 09, 2001 at 09:59:55AM +0200
On Wed, May 09, 2001 at 09:59:55AM +0200, Tom Appermont wrote:
> On Tue, May 08, 2001 at 09:43:13PM -0300, Ralf Baechle wrote:
> > On Tue, May 08, 2001 at 08:25:18PM +0200, Florian Lohoff wrote:
> >
> > > > > compatibility. I read the whole thread on linux-mips but i didnt get the point
> > > > > why this has to happen - If we are repairing a real bug for it.
> > > > >
> > > > > Could someone please elaborate on whats going on as i feel i missed ~200 mails
> > > > > discussion and i dont want to purge the whole debian archive until i know
> > > > > what for we actually drop the compatibility.
> > > >
> > > > We don't.
> > >
> > > Could you explain a bit more - I'd like to understand the whole issue.
> >
> > The whole point was to switch from our IRIX ELF flavoured binaries to
> > standard ABI ELF. These two variants are close but not identical which
> > for example made modutils missbehave.
>
> What is the current status on this? The patches for the tools are already
> integrated in their cvs trees (right?). But I don't think everybody was
> happy with this in the end, aspecially the people wearing debian hats.
> Is anybody working on a solution, or are we waiting for the debian people
> to rebuild all the packages?
As the binary compatibility is not going to break we dont need to rebuild.
I wasnt really happy with the answer of ralf as it brought me nothing
nearer in the understanding of the whole issue. But asking 3 times
to get a fully explanation on where the problem is, what breaks,
and how to fix is enough.
I'll lean back, continue building .debs and wait for others to fix it.
Flo
--
Florian Lohoff flo@rfc822.org +49-5201-669912
Why is it called "common sense" when nobody seems to have any?
next prev parent reply other threads:[~2001-05-09 9:32 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 [this message]
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
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=20010509104635.D12267@paradigm.rfc822.org \
--to=flo@rfc822.org \
--cc=linux-mips@oss.sgi.com \
--cc=ralf@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