From: Ralf Baechle <ralf@oss.sgi.com>
To: "H . J . Lu" <hjl@lucon.org>
Cc: linux-mips@oss.sgi.com
Subject: Re: A new mips toolchain is available
Date: Tue, 12 Jun 2001 21:11:51 +0200 [thread overview]
Message-ID: <20010612211151.A27552@bacchus.dhis.org> (raw)
In-Reply-To: <20010612094055.B20012@lucon.org>; from hjl@lucon.org on Tue, Jun 12, 2001 at 09:40:55AM -0700
On Tue, Jun 12, 2001 at 09:40:55AM -0700, H . J . Lu wrote:
> FYI, my glibc includes
>
> * sysdeps/mips/dl-machine.h (MAP_BASE_ADDR): Commented out.
That means elf/dl-load.c will assume zero for the load address. That will
crash static programs which expect a value of 0x5ffe0000 and are trying to
dlopen a shared library which uses a different value. Most popular
example is rpm. So we need to keep ``#define MAP_BASE_ADDR(l) 0x5ffe0000''
in there until we've got a real fix, unfortunately.
ABI requires us to properly support DT_MIPS_BASE_ADDRESS, so that needs
to fixed for real anyway ...
> * sysdeps/mips/rtld-ldscript.in: Removed.
> * sysdeps/mips/rtld-parms: Likewise.
> * sysdeps/mips/mips64/rtld-parms: Likewise.
> * sysdeps/mips/mipsel/rtld-parms: Likewise.
>
> As I mentioned before, the resulting glibc works fine with the IRIX ABI
> executables. But I have no ideas about DSOs.
This rtld stuff was an IRIX-ism which made it into Linux without the necessary
reflection; nothing bad should happen if we remove it.
Ralf
next prev parent reply other threads:[~2001-06-12 19:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-12 4:03 A new mips toolchain is available H . J . Lu
2001-06-12 11:39 ` Ralf Baechle
2001-06-12 16:40 ` H . J . Lu
2001-06-12 19:11 ` Ralf Baechle [this message]
2001-06-12 19:38 ` H . J . Lu
2001-06-13 7:57 ` Maciej W. Rozycki
2001-06-13 15:08 ` H . J . Lu
2001-06-13 15:22 ` Maciej W. Rozycki
2001-06-13 15:24 ` H . J . Lu
2001-06-13 15:39 ` Maciej W. Rozycki
2001-06-13 15:44 ` H . J . Lu
2001-06-13 18:48 ` Jun Sun
2001-06-13 20:55 ` Harald Koerfgen
2001-06-14 10:26 ` Maciej W. Rozycki
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=20010612211151.A27552@bacchus.dhis.org \
--to=ralf@oss.sgi.com \
--cc=hjl@lucon.org \
--cc=linux-mips@oss.sgi.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