[lldb-dev] Heads-up: FreeBSD LLDB CMake build broken by relative rpath change

Rafael EspĂ­ndola rafael.espindola at gmail.com
Wed Feb 26 14:48:00 PST 2014

> liblldb - here's what lld shows:
> bin/lldb:
>         liblldb.so.3.5 => not found (0)
>         librt.so.1 => /usr/lib/librt.so.1 (0x80082f000)
>         libtinfo.so.5.9 => /usr/local/lib/libtinfo.so.5.9 (0x800a34000)
>         <and system and Python-related libraries>
>> Is the rpath set correctly?
> It looks like it:
> feynman% readelf -d bin/lldb | grep PATH
>  0x000000000000000f (RPATH)              Library rpath: [$ORIGIN/../lib]
>  0x000000000000001d (RUNPATH)            Library runpath: [$ORIGIN/../lib]
>> Does it work with the configure build?
> The buildbot uses the configure build and is green, so it "works" I
> guess -- but I do not know if it's using $ORIGIN or an absolute rpath,
> and will have to wait until I can complete a configure build locally
> to find out.

That is so strange. The Makefile.rules used by the configure build has

  LD.Flags += $(RPATH) -Wl,'$$ORIGIN/../lib

so I would expect it to behave the same as the current cmake build.


More information about the lldb-dev mailing list