From: Kurt Roeckx <kurt@roeckx.be>
To: Nick Clifton <nickc@redhat.com>
Cc: binutils@sourceware.org
Subject: Re: Defined symbols requiring an other library
Date: Fri, 11 Jan 2008 00:04:00 -0000 [thread overview]
Message-ID: <20080110004506.GA23178@roeckx.be> (raw)
In-Reply-To: <m38x2z7yk8.fsf@redhat.com>
On Wed, Jan 09, 2008 at 04:28:55PM +0000, Nick Clifton wrote:
> Hi Kurt,
>
> > Does anybody know if there will be other things that might be a problem
> > we have doing this?
>
> I suspect that you might encounter similar problems with dynamic relocs for
> other targets, not just the COPY reloc. (I do not have proof of this, but it
> seems reasonable, since ABIs vary from target to target).
>
> > Or is there a better of doing this?
>
> Wouldn't it be easier to use the loader to resolve this problem for you ? ie
> have the loader perform a dry run and tell you exactly where it found all the
> symbols ? (You may need to add code to the loader in order to do this, or you
> may be able to use a tool like strace or systemtap). Or you could look at the
> prelinker and possibly parse prelinked binaries ? (The point being that these
> tools already know how to resolve dynamic relocs and find libraries, so why not
> make use of them).
Atleast prelink is not very portable. It only seems to be available on:
Architecture: alpha amd64 i386 powerpc ppc64
systemtap has a simular problem:
Architecture: i386 amd64 ia64 s390 powerpc arm armel armeb
Changing the dynamic loader might be a good way to do this.
Kurt
next prev parent reply other threads:[~2008-01-10 0:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-10 21:58 Nick Clifton
2008-01-11 0:04 ` Kurt Roeckx [this message]
2008-01-11 9:19 ` Daniel Jacobowitz
-- strict thread matches above, loose matches on Subject: below --
2008-01-07 18:27 Kurt Roeckx
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=20080110004506.GA23178@roeckx.be \
--to=kurt@roeckx.be \
--cc=binutils@sourceware.org \
--cc=nickc@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).