This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Issues upgrading to GCC3.0
- To: gcc at gcc dot gnu dot org
- Subject: Issues upgrading to GCC3.0
- From: "George Yohng" <yohng at drivex dot dosware dot 8m dot com>
- Date: Wed, 11 Jul 2001 20:01:42 +0200 (CEST)
> Hello there!
>
>
> I downloaded gcc-3.0.tar.gz and made
> ./configure --prefix=/usr; make; make install
>
> Programs I compile, go with "undefined symbol: __dso_handle" at
> startup. This concerns both shared libraries and C++ programs.
>
> Prior to gcc3.0, I had gcc2.95.2 installed
>
> GLIBC version 2.1.3
> binutils 2.9.5
>
> Possibly I have to upgrade binutils? no?
>
> I would like to stay at current version of GLIBC (as you know, how
> unpleasant is the complete system upgrade).
>
> Can you please help me?
>
> ----
>
> I seen, that GCC3.0 introduces libgcc_s.so. What is that one? Possibly,
> I'm unable to link that one? Or vice versa - this library can't link
> something else?
>
> I'm really eager to know, whether it is possible to link libstdc++ and
> all other GCC3.0 dependent stuff statically, so that customers with
> GCC2.95.2 installed can run my binaries without installing additional
> libraries. However, I would like to keep libc.so.6 shared linkage.
>
> Thanks,
> George.
>