Purpose of --static and Requires.private

Niklas Gürtler profclonk at gmx.de
Fri Sep 28 11:11:14 PDT 2012


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 09/28/2012 08:03 PM, Tollef Fog Heen wrote:
> ]] Niklas Gürtler 
>
>> ... and then analyzing the library dependencies of the resulting
files ...
>> ~ $ ldd helloworld1 | sort
>
> ldd traverses the dependency chain, so that they are the same is not
> surprising. Look at the DT_NEEDED entries from each library and they're
> likely to be different.
>
~ $ objdump -p helloworld1 | grep NEEDED
  NEEDED               libpango-1.0.so.0
  NEEDED               libgobject-2.0.so.0
  NEEDED               libglib-2.0.so.0
  NEEDED               libpthread.so.0
  NEEDED               libc.so.6
~ $ objdump -p helloworld2 | grep NEEDED
  NEEDED               libpango-1.0.so.0
  NEEDED               libgmodule-2.0.so.0
  NEEDED               libdl.so.2
  NEEDED               libgobject-2.0.so.0
  NEEDED               libffi.so.6
  NEEDED               libglib-2.0.so.0
  NEEDED               librt.so.1
  NEEDED               libpcre.so.1
  NEEDED               libpthread.so.0
  NEEDED               libc.so.6


Oh, looks like you're right...
Is it strictly needed for some case that helloworld1 doesn't depend on
libgmodule-2.0.so.0, or is this a rather cosmetic feature?
Is this to allow pango to drop the "libgmodule" dependency and probably
replace it by something else, without the need to recompile helloworld1?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iEYEARECAAYFAlBl6EIACgkQfNJK65aYbI4nQgCfUvX8c1H3muWg1JmWrw+H5cHM
mTcAnjvwzWyF4dKmCk4LXpIfQYxCl0sx
=JAW7
-----END PGP SIGNATURE-----



More information about the pkg-config mailing list