The mystery of the missing library.

Bryan Drewery bdrewery at FreeBSD.org
Wed Jul 29 16:33:49 UTC 2015


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 7/28/15 10:43 PM, David Naylor wrote:
> On Tuesday, 28 July 2015 17:08:37 Bryan Drewery wrote:
> 
>> On 7/28/15 11:46 AM, David Naylor wrote:
> 
>>> Why would the shared library be found when using a relative
>>> path but not
> 
>>> when using an absolute path? Is this a bug in FreeBSD?
> 
>> 
> 
>> What is the output for readelf?
> 
>> 
> 
>> readelf -d `which pypy`|grep -i libr
> 
> 
> 
> ```
> 
> # readelf -d `which pypy` | grep -i libr
> 
> 0x0000000000000001 (NEEDED) Shared library: [libpypy-c.so]
> 
> 0x0000000000000001 (NEEDED) Shared library: [libthr.so.3]
> 
> 0x0000000000000001 (NEEDED) Shared library: [libc.so.7]
> 
> 0x000000000000000f (RPATH) Library rpath: [$ORIGIN/]
> 
> 0x000000000000001d (RUNPATH) Library runpath: [$ORIGIN/]
> 
> ```
> 

I don't know what $ORIGIN is here but it is very suspicious to me (I
haven't looked into it). I would have expected an actual path. This is
likely the reason for the behavior you are seeing.

- -- 
Regards,
Bryan Drewery
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJVuQBnAAoJEDXXcbtuRpfPg1wH/izfjQfsBQ5Rw5lz3jxhl2rw
vEf/BZGwz8rLLoLa1fSR56jQH4KGpGjzmQ3+r0HFVDNuwJty9Wxz6KUxScINFnTF
YmZHXQ3aKPUnb4ZGZjB3sCiPLMqmxdFdMbGUfzhNRK6pKiM4JQEtklYvmjOCljry
XOf+juiJDq0klD7icRWmfmxSSje0SU7Ct8pP15twCwRGDnQ60vjtu8veU/wvIxHi
9BNdOhp44yh+d6F7qHNLSykfa/gL5k64/B5lYWMdg/Tch83tlqoHhH4Lmxd4+tv7
HUbh2ICjaD+efLrnYzq8HeyCIuw87P5YQJHpCBfngxhh7dCAx+tv3Vfz9g4VwFY=
=//3J
-----END PGP SIGNATURE-----


More information about the freebsd-ports mailing list