Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Andreas Jaeger <aj@suse.de>
To: sjhill@cotw.com
Cc: Florian Lohoff <flo@rfc822.org>, Tom Appermont <tea@sonycom.com>,
	Ralf Baechle <ralf@oss.sgi.com>,
	linux-mips@oss.sgi.com
Subject: Re: Binary compatibility break understood ?
Date: 09 May 2001 14:27:39 +0200	[thread overview]
Message-ID: <hoeltyemh0.fsf@gee.suse.de> (raw)
In-Reply-To: <3AF934AE.38AB0089@cotw.com> ("Steven J. Hill"'s message of "Wed, 09 May 2001 07:14:38 -0500")

"Steven J. Hill" <sjhill@cotw.com> writes:

> Florian Lohoff wrote:
> > 
> > > > 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.
> > >
> I will expound a bit more. When I made the changes to fix binutils and switch
> us from the IRIX to ABI ELF flavoured binaries the default target names
> changed from 'elf[32|64][little|big]mips' to 'elf[32|64]trad[little|big]mips'
> in binutils. This has the effect of breaking linker scripts but not a whole
> lot else. These will be the new targets for MIPS/Linux work. Binaries should
> still run just fine if you compile glibc-2.2.2 with the old or new tools.
> Future work though should use the 'elf[32|64]trad[little|big]mips' targets.

Ok, I finally understand.  Can you send a new patch for glibc with an
update for the FAQ?  I'll add it this time.

Andreas
-- 
 Andreas Jaeger
  SuSE Labs aj@suse.de
   private aj@arthur.inka.de
    http://www.suse.de/~aj

  reply	other threads:[~2001-05-09 12:27 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 [this message]
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=hoeltyemh0.fsf@gee.suse.de \
    --to=aj@suse.de \
    --cc=flo@rfc822.org \
    --cc=linux-mips@oss.sgi.com \
    --cc=ralf@oss.sgi.com \
    --cc=sjhill@cotw.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