| To: | Jakub Jelinek <jakub@redhat.com> |
|---|---|
| Subject: | Prelink for mips (Re: MIPS broken in 2.3) |
| From: | "H . J . Lu" <hjl@lucon.org> |
| Date: | Mon, 17 Dec 2001 09:10:32 -0800 |
| Cc: | Andreas Jaeger <aj@suse.de>, GNU libc hacker <libc-hacker@sources.redhat.com>, binutils@sourceware.cygnus.com, linux-mips@oss.sgi.com |
| In-reply-to: | <20011217123631.G542@sunsite.ms.mff.cuni.cz>; from jakub@redhat.com on Mon, Dec 17, 2001 at 12:36:31PM +0100 |
| References: | <u8ellzsg3q.fsf@gromit.moeb> <20011213093958.A6057@lucon.org> <hou1uqclnk.fsf@gee.suse.de> <20011217123631.G542@sunsite.ms.mff.cuni.cz> |
| Sender: | owner-linux-mips@oss.sgi.com |
| User-agent: | Mutt/1.2.5i |
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. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: No bzImage target for MIPS, Maciej W. Rozycki |
|---|---|
| Next by Date: | Re: Prelink for mips (Re: MIPS broken in 2.3), Jakub Jelinek |
| Previous by Thread: | Kernel Wont Boot on I2 - Not the kernel!, Ian Chilton |
| Next by Thread: | Re: Prelink for mips (Re: MIPS broken in 2.3), Jakub Jelinek |
| Indexes: | [Date] [Thread] [Top] [All Lists] |