Re: understanding statically-linked binaries
From: Philipp Buehler (pb_at_usenet-oct-2003.fips.de)
Date: 10/06/03
- Next message: Ralf Fassel: "Re: Asynchronous socket IO"
- Previous message: Balan: "Re: Asynchronous socket IO"
- In reply to: Peter: "understanding statically-linked binaries"
- Next in thread: Jerry Feldman: "Re: understanding statically-linked binaries"
- Reply: Jerry Feldman: "Re: understanding statically-linked binaries"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Mon, 6 Oct 2003 08:10:08 +0000 (UTC)
* Peter (usenet@ointment.org) wrote:
> If 'ldd' can show you what libs an executable is dynamically linked
> against, is there a way to determine after the fact what libs a given
> statically-linked binary was built with? I'm really trying to figure out
> a way to ensure that nothing gets left out when I upgrade packages like
> OpenSSL (without using RPMs).
"no way" as in "easy command to use". ld will pick the needed functions
from the lib, link it and then any direct trace is gone.
With some clue about how executables are linked together on your
system, nm(1) and objdump(1) you might figure out (if these or
similar tools are existent on your system - but I guess so from 'RPM' :))
IF there are nice programmers, what(1) could work, too. Or in last
consequence strings(1).
More ways? Probably..
ciao
-- "Unix was the first OS where you could carry the media and system documentation around in a briefcase. This was fixed in BSD4.2."
- Next message: Ralf Fassel: "Re: Asynchronous socket IO"
- Previous message: Balan: "Re: Asynchronous socket IO"
- In reply to: Peter: "understanding statically-linked binaries"
- Next in thread: Jerry Feldman: "Re: understanding statically-linked binaries"
- Reply: Jerry Feldman: "Re: understanding statically-linked binaries"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|