public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Sturm <jsturm@one-point.com>
To: Marc Kleine-Budde <kleine-budde@gmx.de>
Cc: "Wolcott, Ken (MED, Compuware)" <Ken.Wolcott@med.ge.com>,
	Ronald Landheer-Cieslak <blytkerchan@users.sourceforge.net>,
	Dan Kegel <dank@kegel.com>, GCC Mailing List <gcc@gcc.gnu.org>,
	crossgcc <crossgcc@sources.redhat.com>
Subject: Re: FAQ: how to build a statically-linked gcc?
Date: Wed, 15 Oct 2003 22:23:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.44.0310151639020.576-100000@ops2.one-point.com> (raw)
In-Reply-To: <20031015170433.GA10769@timberwolf.dyndns.org>

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

  reply	other threads:[~2003-10-15 20:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-15 17:04 Dan Kegel
2003-10-15 17:14 ` Ronald Landheer-Cieslak
2003-10-15 17:24   ` Wolcott, Ken (MED, Compuware)
2003-10-15 18:05     ` Marc Kleine-Budde
2003-10-15 22:23       ` Jeff Sturm [this message]
2003-10-15 22:25         ` Dan Kegel
2003-10-16 14:16         ` Ronald Landheer-Cieslak
2003-10-15 22:33 ` Greg Schafer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.44.0310151639020.576-100000@ops2.one-point.com \
    --to=jsturm@one-point.com \
    --cc=Ken.Wolcott@med.ge.com \
    --cc=blytkerchan@users.sourceforge.net \
    --cc=crossgcc@sources.redhat.com \
    --cc=dank@kegel.com \
    --cc=gcc@gcc.gnu.org \
    --cc=kleine-budde@gmx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).