This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Issues upgrading to GCC3.0
- To: "George Yohng" <yohng at drivex dot dosware dot 8m dot com>
- Subject: Re: Issues upgrading to GCC3.0
- From: Alexandre Oliva <aoliva at redhat dot com>
- Date: 12 Jul 2001 18:09:28 -0300
- Cc: gcc at gcc dot gnu dot org
- Organization: GCC Team, Red Hat
- References: <1402.194.85.255.1.994874502.squirrel@mail.allweb.se>
On Jul 11, 2001, "George Yohng" <yohng@drivex.dosware.8m.com> wrote:
>> Can you please help me?
Upgrade binutils.
>> I seen, that GCC3.0 introduces libgcc_s.so. What is that one?
It's a shared version of libgcc.a. By default, it's only linked in
when creating a shared library with gcc, i.e., when running gcc
-shared. There's some option in the manual that can override the
choice between the shared and the static libgcc. I don't recall the
exact spelling at the moment.
>> 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.
-static.
> However, I would like to keep libc.so.6 shared linkage.
Oh. Then, you may have to mention libstdc++.a explicitly. Try `gcc
-print-file-name=libstdc++.a'
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist *Please* write to mailing lists, not to me