setting EXECUTABLE_OUTPUT_PATH in tier1/ tests ?
Stephen Kelly
steveire at gmail.com
Thu May 10 21:39:23 UTC 2012
David Faure wrote:
> On Thursday 10 May 2012 23:21:55 Stephen Kelly wrote:
>> David Faure wrote:
>> >> Now we don't do that anymore.
>> >> So for Windows the dlls and the exes have to go into the same
>> >> directory.
>> >
>> > And how will the libs be found on Unix, given that they are under lib/
>> > and not bin/?
>> >
>> > Putting all executables in bin doesn't remove the need for wrapper
>> > scripts, on unix.
>>
>> We have RPATH for that. Is that enough?
>
> Doesn't seem to work currently.
>
> Apply attached patch in kcoreaddons, make, then try to run
> ./krandomsequencetest:
>
> ./krandomsequencetest: symbol lookup error: ./krandomsequencetest:
> undefined symbol: _ZN7KBackup10helloSteveEv
>
helloDavid();
:)
>
> Hmm, let's investigate:
>
> ldd ./krandomsequencetest | grep kcoreadd
> libkcoreaddons.so.5 =>
> /d/kde/inst/kde_frameworks/lib64/libkcoreaddons.so.5
> (0x00007ff56b385000)
>
> objdump -p krandomsequencetest | grep PATH
> RPATH
> /d/qt/4/qt-for-trunk/lib:/d/kde/build/5/kdelibs-
frameworks/tier1/kcoreaddons/src:/d/kde/build/5/kdelibs-
frameworks/libinqt5/src:/d/kde/build/5/kdelibs-
frameworks/libkdeqt5staging/src
> RUNPATH
> /d/qt/4/qt-for-trunk/lib:/d/kde/build/5/kdelibs-
frameworks/tier1/kcoreaddons/src:/d/kde/build/5/kdelibs-
frameworks/libinqt5/src:/d/kde/build/5/kdelibs-
frameworks/libkdeqt5staging/src
>
> Hmm, so this comes from $LD_LIBRARY_PATH pointing to $KDEDIR/lib64.
> Emptying it works: LD_LIBRARY_PATH= ldd ./krandomsequencetest | grep
> kcoreadd
> libkcoreaddons.so.5 =>
> /d/kde/build/5/kdelibs-
frameworks/tier1/kcoreaddons/src/libkcoreaddons.so.5
> (0x00007f506c524000)
>
> But wasn't RPATH supposed to take precedence over $LD_LIBRARY_PATH?
>
Yes, but RUNPATH takes precedence over LD_LIBRARY_PATH. Maybe RUNPATH takes
precedence over LD_LIBRARY_PATH?
emit thanks();
Steve.
More information about the Kde-frameworks-devel
mailing list