[Thread] GCC 2.95/STLPort/Linux static lib failures
Is it the test environment that is at failt here (from http://tinyurl.com/5t5mf): /usr/bin/ld: cannot find -lstlport_gcc_stldebug_static collect2: ld returned 1 exit status set -e LD_LIBRARY_PATH=/usr/local/gcc-2.95.3/stlport-4.5.3/lib:/usr/local/gcc-2.95.3/lib:$LD_LIBRARY_PATH export LD_LIBRARY_PATH "/usr/local/gcc-2.95.3/bin/g++" -static -g -pthread -pthread -o "../bin/boost/libs/thread/test/test_barrier_lib.test/gcc-2.95.3-stlport-4.5.3-linux/debug/runtime-link-static/threading-multi/test_barrier_lib" -L"../bin/boost/libs/thread/build/libboost_thread.a/gcc-2.95.3-stlport-4.5.3-linux/debug/runtime-link-static/threading-multi" -L"../bin/boost/libs/test/build/libboost_unit_test_framework.a/gcc-2.95.3-stlport-4.5.3-linux/debug/runtime-link-static/threading-multi" -L"/usr/local/gcc-2.95.3/stlport-4.5.3/lib" -L"/usr/local/gcc-2.95.3/lib" "../bin/boost/libs/thread/test/test_barrier_lib.test/gcc-2.95.3-stlport-4.5.3-linux/debug/runtime-link-static/threading-multi/test_barrier.o" "../bin/boost/libs/thread/test/test_barrier_lib.test/gcc-2.95.3-stlport-4.5.3-linux/debug/runtime-link-static/threading-multi/tss_null.o" "../bin/boost/libs/thread/build/libboost_thread.a/gcc-2.95.3-stlport-4.5.3-linux/debug/runtime-link-static/threading-multi/libboost_thread-gcc295-mt-sgdp-1_32.a" "../bin/boost/libs/test/build/libboost_unit_test_framework.a/gcc-2.95.3-stlport-4.5.3-linux/debug/runtime-link-static/threading-multi/libboost_unit_test_framework.a" "../bin/boost/libs/thread/build/libboost_thread.a/gcc-2.95.3-stlport-4.5.3-linux/debug/runtime-link-static/threading-multi/libboost_thread-gcc295-mt-sgdp-1_32.a" "../bin/boost/libs/test/build/libboost_unit_test_framework.a/gcc-2.95.3-stlport-4.5.3-linux/debug/runtime-link-static/threading-multi/libboost_unit_test_framework.a" -lrt -lstlport_gcc_stldebug_static -lrt -Wl,-rpath-link,. ? -- Aleksey Gurtovoy MetaCommunications Engineering
Aleksey Gurtovoy wrote:
Is it the test environment that is at failt here (from http://tinyurl.com/5t5mf):
/usr/bin/ld: cannot find -lstlport_gcc_stldebug_static
There is no file named "libstlport_gcc_stldebug_static.a" here. Instead, there is "libstlport_gcc_stldebug.a". Is the library name being generated incorrectly, or would the additional "static" in the library name indicate something different than what the ".a" indicates in contrast to the ".so" extension used by shared libraries?
collect2: ld returned 1 exit status
set -e LD_LIBRARY_PATH=/usr/local/gcc-2.95.3/stlport-4.5.3/lib:/usr/local/gcc-2.95.3/lib:$LD_LIBRARY_PATH
The path is being set correctly. Regards, m
Folks, Could somebody familiar with the gcc-stlport toolset answer Martin's question below? Martin Wille writes:
Aleksey Gurtovoy wrote:
Is it the test environment that is at failt here (from http://tinyurl.com/5t5mf): /usr/bin/ld: cannot find -lstlport_gcc_stldebug_static
There is no file named "libstlport_gcc_stldebug_static.a" here. Instead, there is "libstlport_gcc_stldebug.a". Is the library name being generated incorrectly, or would the additional "static" in the library name indicate something different than what the ".a" indicates in contrast to the ".so" extension used by shared libraries?
collect2: ld returned 1 exit status set -e LD_LIBRARY_PATH=/usr/local/gcc-2.95.3/stlport-4.5.3/lib:/usr/local/gcc-2.95.3/lib:$LD_LIBRARY_PATH
The path is being set correctly.
Regards, m
Thanks in advance, -- Aleksey Gurtovoy MetaCommunications Engineering
Martin Wille <mw8329@yahoo.com.au> writes:
There is no file named "libstlport_gcc_stldebug_static.a" here. Instead, there is "libstlport_gcc_stldebug.a". Is the library name being generated incorrectly, or would the additional "static" in the library name indicate something different than what the ".a" indicates in contrast to the ".so" extension used by shared libraries?
The last four lines of tools/build/v1/stlport.jam show the relationship between build properties and the name of the stlport library being loaded. If the name is wrong, either it was always wrong, or STLPort changed the names of the libraries they build. -- Dave Abrahams Boost Consulting http://www.boost-consulting.com
David Abrahams writes:
Martin Wille <mw8329@yahoo.com.au> writes:
There is no file named "libstlport_gcc_stldebug_static.a" here. Instead, there is "libstlport_gcc_stldebug.a". Is the library name being generated incorrectly, or would the additional "static" in the library name indicate something different than what the ".a" indicates in contrast to the ".so" extension used by shared libraries?
The last four lines of tools/build/v1/stlport.jam show the relationship between build properties and the name of the stlport library being loaded. If the name is wrong, either it was always wrong, or STLPort changed the names of the libraries they build.
Should be fixed in the CVS now. Martin, just in case, could you please remove the binaries for "gcc-2.95.3-stlport-4.5.3-linux" to force bjam to recognize the change? -- Aleksey Gurtovoy MetaCommunications Engineering
participants (3)
-
Aleksey Gurtovoy -
David Abrahams -
Martin Wille