Aleksey Gurtovoy wrote:
We seem to have an alarming number of new regression with two Linux toolsets, "gcc-2.95.3-stlport-4.5.3-linux" and "intel-8.0-linux" -- http://tinyurl.com/5p5ru. Intel looks particularly bad, due to what seems to be a problem with system headers:
Ahh, some problems were caused by the switch from icc to icpc. My workaround for finding the system headers only worked for icc. I'll patch icpc accordingly and we'll see which problems will remain.
The problems with GCC/STLPort are different: the linker cannot find a number of different _STL:: symbols that supposedly should be present in the library:
Linker output [2004-10-02 04:30:36 UTC]: [...]
It might be a problem with the toolset, but it's hard to say without seeing the linker's command line. Martin, would it be possible for you to modify your regression driver to always run with "-d2" flag?
In case of an error, the command line is printed below the error messages: 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++" -g -pthread -o "../bin/boost/libs/date_time/test/testdate.test/gcc-2.95.3-stlport-4.5.3-linux/debug/testdate" -L"../bin/boost/libs/date_time/build/libboost_date_time.a/gcc-2.95.3-stlport-4.5.3-linux/debug" -L"/usr/local/gcc-2.95.3/stlport-4.5.3/lib" -L"/usr/local/gcc-2.95.3/lib" "../bin/boost/libs/date_time/test/testdate.test/gcc-2.95.3-stlport-4.5.3-linux/debug/testdate.o" "../bin/boost/libs/date_time/build/libboost_date_time.a/gcc-2.95.3-stlport-4.5.3-linux/debug/libboost_date_time-gcc295-gdp-1_32.a" "../bin/boost/libs/date_time/build/libboost_date_time.a/gcc-2.95.3-stlport-4.5.3-linux/debug/libboost_date_time-gcc295-gdp-1_32.a" -lrt -Wl,-rpath-link,. Looks like there's neither -llibstlport_gcc nor -llibstlport_gcc_stldebug anywhere in the commandline. The search path is set up correctly. Regards, m