This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: FAQ: how to build a statically-linked gcc?


Jeff Sturm wrote:
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.

Hence my original post, which asked "How do I build a statically-linked gcc?" - Dan


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]