From: Thiemo Seufer <ths@networkno.de>
To: Hiroki Kaminaga <kaminaga@sm.sony.co.jp>
Cc: linux-mips@linux-mips.org
Subject: Re: MIPS prelink question
Date: Tue, 18 Mar 2008 11:19:15 +0000 [thread overview]
Message-ID: <20080318111914.GH26619@networkno.de> (raw)
In-Reply-To: <20080318.154701.74743177.kaminaga@sm.sony.co.jp>
Hiroki Kaminaga wrote:
>
> Hi!
>
> I'm not sure if this is the right ML to ask, but since I've found
> discussion about MIPS prelink here, I'm posting here...
The binutils list would be a better place.
> In the below thread, patch for MIPS prelink was posted.
> http://www.linux-mips.org/archives/linux-mips/2006-11/msg00034.html
>
> I've tried this patch, but I got below error when I tried to do prelink.
>
> No space in ELF segment table to add new ELF segment
A bit more of the output would help with isolating the problem.
Anyway, IIRC there are two effects which cause this error:
- Linking in binary objects which were built by a toolchain without
prelink support, probably one of the compiler-internal startup files.
- Use of an older version on binutils (from the time when the prelink
patches went in), which still had a few issues with handling the
additional segment.
> On the montavista pro 5.0 note, I found that they have fixed above
> prelink error, but I could not find the patch. Could someone give
> me pointer to address this issue?
I believe binutils 2.18 works fine WRT prelinking. I don't remember
the particular patches to watch out for, though.
Thiemo
next prev parent reply other threads:[~2008-03-18 11:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-18 6:47 MIPS prelink question Hiroki Kaminaga
2008-03-18 11:19 ` Thiemo Seufer [this message]
2008-03-18 12:33 ` Daniel Jacobowitz
2008-03-19 5:21 ` Hiroki Kaminaga
2008-03-19 8:53 ` Hiroki Kaminaga
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=20080318111914.GH26619@networkno.de \
--to=ths@networkno.de \
--cc=kaminaga@sm.sony.co.jp \
--cc=linux-mips@linux-mips.org \
/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.