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

Rafael EspĂ­ndola rafael.espindola at gmail.com
Thu Feb 27 04:49:01 PST 2014

On 26 February 2014 21:40, Ed Maste <emaste at freebsd.org> wrote:
> On 26 February 2014 17:48, Rafael EspĂ­ndola <rafael.espindola at gmail.com> wrote:
>> 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.
> This at least has a straightforward explanation -- for the configure
> build my binary ends up with an rpath containing both the
> $ORIGIN-based relative path as well as an absolute path:
> feynman% readelf -d ./Debug+Asserts/bin/lldb | grep PATH
>  0x000000000000000f (RPATH)              Library rpath:
> [$ORIGIN/../lib:/tank/emaste/src/llvm/build-make/Debug+Asserts/lib]
>  0x000000000000001d (RUNPATH)            Library runpath:
> [$ORIGIN/../lib:/tank/emaste/src/llvm/build-make/Debug+Asserts/lib]

OK. We should probably get the same to happen with cmake. What is the
command line used to link ./Debug+Asserts/bin/lldb? I assume the
relative path is being added by llvm's Makefile.rules. Is the absolute
one being added by lldb's?

Brand, is there a way to add to rpath from an inner CMakeLists.txt?


More information about the lldb-dev mailing list