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 15:49:43 +0200 [thread overview]
Message-ID: <hor8xybpjc.fsf@gee.suse.de> (raw)
In-Reply-To: <3AF94D3C.98A4E8@cotw.com> ("Steven J. Hill"'s message of "Wed, 09 May 2001 08:59:24 -0500")
"Steven J. Hill" <sjhill@cotw.com> writes:
> Andreas Jaeger wrote:
> >
> > > There's the patch. It's not much but it is correct. I have built multiple
> >
> > But it's not complete. AFAIK remember you posted a patch with some
> > more changes and HJ even suggested to remove the rtld-ldscript.in file.
> >
> I had this discussion with Ralf. He had reasons to not remove this
> file altogether. Perhaps some input from him would be prudent. Ralf?!
So the one-liner you mailed should be all that has to be added?
> > I need an update for the FAQ that explains which binutils version is
> > required for MIPS and I prefer to have a test that checks on
> > MIPS-Linux for the correct emulation in ld.
> >
> As far as the versions for binutils:
>
> HJLu binutils-2.11.90.0.5 or greater
> CVS binutils
> binutils 2.11.1? (I'm not sure what the next release number is)
>
> For the correct ld emulation, I assume you mean make changes in glibc
> to check for the proper target 'elf[32|64]trad[little|big]mips'?
That's what I mean,
Andreas
--
Andreas Jaeger
SuSE Labs aj@suse.de
private aj@arthur.inka.de
http://www.suse.de/~aj
next prev parent reply other threads:[~2001-05-09 13:49 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 [this message]
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=hor8xybpjc.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