On Fri, Oct 22, 2010 at 1:35 PM, Michael Eager <ea...@eagerm.com> wrote:
> Paolo Carlini wrote:
>>
>> On 10/22/2010 08:43 PM, Michael Eager wrote:
>>>
>>> Hi --
>>>
>>> I'm seeing test suite failures in g++ caused by
>>> linking with the wrong libstdc++.so.
>>>
>>> It looks like g++.exp always appends the default
>>> directory
>>> append flags -L${gccpath}/libstdc++-v3/src/.libs
>>> instead of
>>> append flags -L${gccpath}/<multilib>/libstdc++-v3/src/.libs
>
>> Without having looked into the issue in any detail, the issue seems
>> weird to me: for sure many people regularly build multilib (myself and
>> HJ on gcc-testresults included, for example) without any problem
>> whatsoever. I would suggest figuring out first what's special about your
>> setup.
>
> I don't know that there's anything special about my setup.
> g++.exp is adding -L paths to the wrong libstdc++ directory.
> When running GCC tests, only the -B option is added. The
> correct multilib directory is selected by the gcc driver.
>
> Do you run "make check" with default options, or do you
> specify compiler options which should result in linking
> non-default c++ libraries?
I use
# make check RUNTESTFLAGS="--target_board 'unix{-m32,}'"
to test both 32bit/64bit on Intel64.
H.J.
