On 26 February 2014 21:40, Ed Maste <[email protected]> wrote: > On 26 February 2014 17:48, Rafael Espíndola <[email protected]> > 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? Cheers, Rafael _______________________________________________ lldb-dev mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
