From: Andrew Stubbs <ams@codesourcery.com>
To: linux-sh@vger.kernel.org
Subject: Re: How can I undersatnd if the userland app is linked using uclibc
Date: Mon, 22 Mar 2010 10:24:31 +0000 [thread overview]
Message-ID: <4BA7455F.8060007@codesourcery.com> (raw)
In-Reply-To: <201003191808.00063.fabio.giovagnini@aurion-tech.com>
On 19/03/10 17:08, Fabio Giovagnini wrote:
> Codesurgery toolchain supplies both the library; how can I know building the
> application the linker used uclibc or glibc?
Answer 1: Use ldd (from glibc) to see what dynamic linker it uses.
Answer 2: The 'interpreter' (dynamic linker) is encoded into the binary
as a string. You can read it out with objdump, readelf or even just strings.
If a dynamic executable is linked against glibc it will use
ld-linux.so.2. If it's linked against uClibc it will use ld-uClibc.so.0.
For statically linked applications, use nm to read the symbol names. If
it has a symbol "__uClibc_main" then it's uClibc, otherwise it's Glibc.
Andrew
prev parent reply other threads:[~2010-03-22 10:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-19 17:08 How can I undersatnd if the userland app is linked using uclibc of glibc? Fabio Giovagnini
2010-03-22 10:24 ` Andrew Stubbs [this message]
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=4BA7455F.8060007@codesourcery.com \
--to=ams@codesourcery.com \
--cc=linux-sh@vger.kernel.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 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 NNTP newsgroup(s).