On 3/23/06, <b class="gmail_sendername">Vladimir Prus</b> <<a href="mailto:ghost@cs.msu.su">ghost@cs.msu.su</a>> wrote:<div><span class="gmail_quote"></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> the test results for OSL-V2 and CalebEpstein-V2 suggest problems with gcc<br>LD_LIBRARY_PATH setup.</blockquote><div><br>The joint gcc 3.4.3 + 4.1.0 test runs appear to have turned up a bug (which you have since fixed I believe) in the LD_LIBRARY_PATH handling of BBv2. <br><br>When tests were run, I would get an LD_LIBRARY_PATH that included <span style="font-weight: bold;">both </span>the 4.1.0 and 3.4.3 libdirs, and due to the issue in the next paragraph, this broke many of the 3.4.3 tests. <br><br>I've had to discontinue testing on gcc 4.1.0 for now due to it not supporting wide-characrter strings or streams on Solaris versions less than 10 (see <a href="http://gcc.gnu.org/bugzilla/show_bug.cgi?id=6702">http://gcc.gnu.org/bugzilla/show_bug.cgi?id=6702 </a>). This is why, when the 3.4.3 tests were picking up the 4.1.0 libstdc++, they were hitting missing symbol errors.<br><br>Here's my current test-config.jam:<br><br>--- cut ---<br>using gcc : 3.4.3_sunos : /home/ietdev/tools/sunos-sparc/gcc- 3.4.3/bin/g++ : <linker-type>sun ;<br>using gcc : 4.1.0_sunos : /home/ietdev/tools/sunos-sparc/gcc-4.1.0/bin/g++ : <linker-type>sun ;<br>using python : 2.4 : /home/ietdev/tools/sunos-sparc/python-2.4 ;<br>--- cut ---- <br></div><br>Perhaps the value of LD_LIBRARY_PATH should be reported along with the rest of the test output?<br><br></div>-- <br>Caleb Epstein<br>caleb dot epstein at gmail dot com