From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-return-84058-listarch-gcc=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 24160 invoked by alias); 15 Oct 2003 20:53:58 -0000
Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Archive: <http://gcc.gnu.org/ml/gcc/>
List-Post: <mailto:gcc@gcc.gnu.org>
List-Help: <http://gcc.gnu.org/ml/>
Sender: gcc-owner@gcc.gnu.org
Received: (qmail 24151 invoked from network); 15 Oct 2003 20:53:56 -0000
Received: from unknown (HELO racerx.ixiacom.com) (64.60.75.69)
  by sources.redhat.com with SMTP; 15 Oct 2003 20:53:56 -0000
Received: from ixiacom.com (dank.ixiacom.com [192.168.3.117]) by racerx.ixiacom.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id 4KS8TVWP; Wed, 15 Oct 2003 13:54:04 -0700
Message-ID: <3F8DB165.6040903@ixiacom.com>
Date: Wed, 15 Oct 2003 22:25:00 -0000
From: Dan Kegel <dkegel@ixiacom.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030617
X-Accept-Language: en
MIME-Version: 1.0
To: Jeff Sturm <jsturm@one-point.com>
CC: Marc Kleine-Budde <kleine-budde@gmx.de>, 
 "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?
References: <Pine.LNX.4.44.0310151639020.576-100000@ops2.one-point.com>
In-Reply-To: <Pine.LNX.4.44.0310151639020.576-100000@ops2.one-point.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-SW-Source: 2003-10/txt/msg00613.txt.bz2

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