From: "H . J . Lu" <hjl@lucon.org>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Andreas Jaeger <aj@suse.de>,
GNU libc hacker <libc-hacker@sources.redhat.com>,
binutils@sourceware.cygnus.com, linux-mips@oss.sgi.com
Subject: Prelink for mips (Re: MIPS broken in 2.3)
Date: Mon, 17 Dec 2001 09:10:32 -0800 [thread overview]
Message-ID: <20011217091032.A29014@lucon.org> (raw)
In-Reply-To: <20011217123631.G542@sunsite.ms.mff.cuni.cz>; from jakub@redhat.com on Mon, Dec 17, 2001 at 12:36:31PM +0100
On Mon, Dec 17, 2001 at 12:36:31PM +0100, Jakub Jelinek wrote:
> instead (well, best would be if somebody ported prelink to mips;
> I'll try to answer any questions and help).
Do you have some documentations how prelink works?
> I skipped mips because it is way too different from how any other ELF
> architecture works (e.g. using a single dynamic reloc type for everything
> with various meanings, etc.) and I have no access to it.
That is what I am afraid of. The MIPS ABI supports "quickstart". I
don't know if we can add prelink to mips without breaking/changing
the MIPS ABI. I don't want to spend my time on it if it can't be done
at all.
H.J.
next parent reply other threads:[~2001-12-17 18:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <u8ellzsg3q.fsf@gromit.moeb>
[not found] ` <20011213093958.A6057@lucon.org>
[not found] ` <hou1uqclnk.fsf@gee.suse.de>
[not found] ` <20011217123631.G542@sunsite.ms.mff.cuni.cz>
2001-12-17 17:10 ` H . J . Lu [this message]
2001-12-17 17:52 ` Prelink for mips (Re: MIPS broken in 2.3) Jakub Jelinek
2002-01-07 21:16 ` H . J . Lu
2002-01-08 2:29 ` H . J . Lu
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=20011217091032.A29014@lucon.org \
--to=hjl@lucon.org \
--cc=aj@suse.de \
--cc=binutils@sourceware.cygnus.com \
--cc=jakub@redhat.com \
--cc=libc-hacker@sources.redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.