This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: compilation problems with gcc 3.0
- To: gcc-help at gcc dot gnu dot org
- Subject: Re: compilation problems with gcc 3.0
- From: Anupam Kapoor <anupamkap at earthlink dot net>
- Date: Fri, 22 Jun 2001 00:20:51 -0700
- Cc: Michael Jarvis <michael at jarvis dot com>
- References: <20010621113529.A7009@dragon.jarvis.com>
On Thursday 21 June 2001 09:35, Michael Jarvis wrote:
> I think you need to specify "--enable-shared" when you configure in order
> to build a shared libstdc++.
>
> I built gcc-2.95.3 with:
>
> ../gcc-2.95.3/configure --prefix=/home/gcc --with-gnu-as --with-gnu-ld \
> --enable-threads=posix --enable-version-specific-runtime-libs \
> --enable-languages=c++ --enable-shared
>
> I'm still trying to get gcc-3.0 to build. :-)
>
> Good luck!
no actually you don't have to explicitly specify building the shared
libraries. they are enabled by default (this has been enabled from
the current release of gcc. earlier releases warranted an explicit
decleration to this effect, as you have shown above). if your target cannot
generate shared objects, then static libs will be generated for you. however,
you can explicitly control, what libs are generated from the compile e.g.
gcc, libstdc++, gc-boehm etc.
i would be glad to know, of any eoe in the statment above though.
thanks
anupam