This is the mail archive of the
mailing list for the libstdc++ project.
Re: Thread deadlock problem with cout
- To: lfarkas at mindmaker dot hu
- Subject: Re: Thread deadlock problem with cout
- From: dek_ml at konerding dot com
- Date: Fri, 21 Jul 2000 07:30:09 -0700
- cc: STDC++ <libstdc++ at sources dot redhat dot com>, dek_ml at adsl-63-202-25-210 dot dsl dot snfc21 dot pacbell dot net
Levente Farkas writes:
>Craig Rodrigues wrote:
>> I downloaded the latest snapshots of libstdc++ from rawhide.redhat.com.
>> I am running:
>> gcc-2.96-33 .i386.rpm
>this is NOT a libstdc++-v3 !!! this is the v2 version!
>I discuss it with jakub and the current (internal) rawhide rpms
>descriptions fix not to state as it's a libstdc++-v3.
>redhat currently not and in 7.0 won't suuport v3.
Understandably so. libstdc++-v3 has a long way to go before it's release quality,
and it's going to break everybody's code who's been writing against libstdc++-v2
(even though it libstdc++-v3 aspires to be standard-compliant and people *should*
be writing standard-compliant code, the reality is that people wrote their code
to compile with libstdc++-v2).
Furthermore, the gcc-2.96 series is highly experimental and I don't think Red Hat
would want to commit to compiling their whole distribution (including the kernel,
which may have some weird interactions with the new compilers).
There's no real challenge to building and using a libstdc++-v3 on the same system as the
normal (old) gcc RPMs. I just install the new CVS compilers in /usr/local (or /usr/local/gcc)
and use the PATH variable to select which g++ (and libstdc++) gets used.