This is the mail archive of the
libstdc++@sourceware.cygnus.com
mailing list for the libstdc++ project.
Re: bugs: gcc with stdc++-v3, rawhide's gcc, stlport, cxxrt
- To: brent verner <brent at rcfile dot org>
- Subject: Re: bugs: gcc with stdc++-v3, rawhide's gcc, stlport, cxxrt
- From: Benjamin Kosnik <bkoz at redhat dot com>
- Date: Thu, 6 Jul 2000 09:52:40 -0700 (PDT)
- cc: Levente Farkas <lfarkas at mindmaker dot hu>, stdc++ <libstdc++ at sourceware dot cygnus dot com>
Levente,
Instead of using an rpm, the instructions for using libtdc++-v3 are
geared toward using source distributions. Becase of this, they depend on
the stability of gcc, et. al. Figuring out what sources to use is a bit
of an art....
> grab gcc-20000619 snapshot (either cvs or via ftp)
> rm -rf libstdc++-v3 from the snapshot
> cvs the most recent libstdc++-v3
> make a build dir parallel to the $SRC_DIR and configure it with:
> ../${SRC_DIR}/configure --prefix=${INSTALL_PREFIX} \
> --enable-libstdcxx-v3 --enable-threads=posix \
> --enable-long-long --enable-cshadow-headers \
> --enable-namespaces --enable-languages=c,c++
>
> this works for me. you may get snagged by the -Werror failure,
> but can circumvent this.
>
> also, my binutils have been patched as suggested in
> http://sourceware.cygnus.com/ml/libstdc++/2000-06/msg00138.html
> (versions binutils-2.10.0.9 and binutils-2.9.5.0.46, known to work
> with this patch, though not _sure_ if it's necessary for the
> 2.10.9 release)
This seems to be the current state of the art...
> btw, I'm writing a script that will automate these steps, so if you'd
> like I can send it to you later (for me) today after I get time to
> finish it.
might as well just post it for everybody...
thanks,
benjamin