Ralf Wildenhues wrote:
Hello Michael,
* Michael Eager wrote on Fri, Oct 22, 2010 at 10:35:48PM CEST:
Paolo Carlini wrote:
On 10/22/2010 08:43 PM, Michael Eager wrote:
I'm seeing test suite failures in g++ caused by
linking with the wrong libstdc++.so.
It looks like g++.exp always appends the
Hello Michael,
* Michael Eager wrote on Fri, Oct 22, 2010 at 10:35:48PM CEST:
> Paolo Carlini wrote:
> >On 10/22/2010 08:43 PM, Michael Eager wrote:
> >>I'm seeing test suite failures in g++ caused by
> >>linking with the wrong libstdc++.so.
> >>
> >>It looks like g++.exp always appends the defaul
On Fri, Oct 22, 2010 at 1:35 PM, Michael Eager 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
>>
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 -
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${gcc
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}//libstdc++-v3/src/.libs
Has anyone else run into this p