Date: prev next · Thread: first prev next last
2015 Archives by date, by thread · List index


On 10/16/2015 07:19 PM, sibu wrote:
On Friday 16 October 2015 13:45:41 Stephan Bergmann wrote:
LD_LIBRARY_PATH=/home/linteg/BUILD_LO/libreoffice-5.0.2.2/instdir/program
ldd
/home/linteg/BUILD_LO/libreoffice-5.0.2.2/workdir/LinkTarget/CppunitTest
/libtest_vcl_app_test.so

root [ /home/linteg ]#
LD_LIBRARY_PATH=/home/linteg/BUILD_LO/libreoffice-5.0.2.2/workdir/LinkTarget/CppunitTest/libtest_vcl_app_test.so
\
ldd
/home/linteg/BUILD_LO/libreoffice-5.0.2.2/workdir/LinkTarget/CppunitTest/libtest_vcl_app_test.so

That's not the LD_LIBRARY_PATH setting I'd asked for (better copy/paste the requested command lines), but the output is also no longer relevant given the next command's output.

root [ /home/linteg ]#
LD_LIBRARY_PATH=/home/linteg/BUILD_LO/libreoffice-5.0.2.2/instdir/program:/home/linteg/BUILD_LO/libreoffice-5.0.2.2/workdir/UnpackedTarball/cppunit/src/cppunit/.libs
ldd
/home/linteg/BUILD_LO/libreoffice-5.0.2.2/workdir/LinkTarget/CppunitTest/libtest_vcl_app_test.so
         linux-vdso.so.1 (0x00007fff069f5000)
         libcppunit-1.12.so.1 => /usr/lib/libcppunit-1.12.so.1
(0x00007fdae26ca000)

So you're using the system's libcppunit-1.12.so.1, and all needed libs are found fine. Hmm. Maybe

LD_LIBRARY_PATH=/home/linteg/BUILD_LO/libreoffice-5.0.2.2/instdir/program ldd -r 
/home/linteg/BUILD_LO/libreoffice-5.0.2.2/workdir/LinkTarget/CppunitTest/libtest_vcl_app_test.so

gives some helpful output.

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.