This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: FAQ: how to build a statically-linked gcc?
- From: Jeff Sturm <jsturm at one-point dot com>
- To: Marc Kleine-Budde <kleine-budde at gmx dot de>
- Cc: "Wolcott, Ken (MED, Compuware)" <Ken dot Wolcott at med dot ge dot com>, Ronald Landheer-Cieslak <blytkerchan at users dot sourceforge dot net>, Dan Kegel <dank at kegel dot com>, GCC Mailing List <gcc at gcc dot gnu dot org>, crossgcc <crossgcc at sources dot redhat dot com>
- Date: Wed, 15 Oct 2003 16:49:16 -0400 (EDT)
- Subject: Re: FAQ: how to build a statically-linked gcc?
On Wed, 15 Oct 2003, Marc Kleine-Budde wrote:
> Hmm - We should perhaps discuss what the --enable/disable-shared/static
> switches are supposed to do......:) Should they affect the 'target' (the
> bins gcc will generate) or the 'host' (the resultung gcc/g++)?
I haven't read much of this thread, but I'm a bit surprised that
anyone expects --disable-shared to do other than what is documented, i.e.
gcc:
--disable-shared don't provide a shared libgcc
libstdc++-v3:
--enable-shared=PKGS build shared libraries default=yes
libjava:
--enable-shared[=PKGS] build shared libraries [default=yes]
libf2c:
--enable-shared[=PKGS] build shared libraries [default=yes]
libobjc:
--enable-shared[=PKGS] build shared libraries [default=no]
None of this suggests that any behavior resembling the `-static' compiler
switch is intended.
Jeff