On Tue, Feb 3, 2015 at 7:24 PM, Corentin Desfarges wrote:
I'm not sure to know what log you asked me to check. I get this build
log with "sudo pdebuild -us -uc -nc" :
http://www.corentindesfarges.fr/buildlog.txt
That is the log I am talking about. This appears to be the part where
fwLauncher is linked:
/usr/bin/c++ -g -O2 -fstack-protector-strong -Wformat
-Werror=format-security -D_FORTIFY_SOURCE=2 -O3 -DNDEBUG
-Wl,-z,relro -Wl,--no-as-needed -Wl,-rpath=/usr/lib/fw4spl -ldl
CMakeFiles/fwLauncher.dir/src/ProfileRunner.cpp.o -o
bin/fwLauncher-0.1 -rdynamic ../lib/fw4spl/libfwCore.so.0.1
../lib/fw4spl/libfwRuntime.so.0.3 -lboost_filesystem
-lboost_program_options ../lib/fw4spl/libfwCore.so.0.1 -lboost_chrono
-lboost_log -lboost_log_setup -lboost_thread -lpthread -lxml2
-lboost_regex -lboost_filesystem -lboost_date_time -lboost_system
-Wl,-rpath,/home/corentin/dev1/fw4spl/obj-x86_64-linux-gnu/lib/fw4spl
That has two different rpaths in it, confusing. After you have done a
build, what do these commands print?
objdump -x /home/corentin/dev1/fw4spl/debian/fw4spl/usr/bin/fwLauncher
| grep -i rpath
objdump -x /home/corentin/dev1/fw4spl/debian/fw4spl/usr/bin/fwLauncher-0.1
| grep -i rpath
objdump -x /home/corentin/dev1/fw4spl/obj-x86_64-linux-gnu/fwLauncher/bin/fwLauncher-0.1
| grep -i rpath
objdump -x /home/corentin/dev1/fw4spl/obj-x86_64-linux-gnu/fwLauncher/bin/fwLauncher-0.1
| grep -i rpath
Leopold: we are talking about a private library here, rpath is what
you set for private libraries.