This is the mail archive of the gcc-help@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: Cross gcc build problem

From: NightStrike <nightstrike at gmail dot com>
To: "David Daney" <ddaney at avtrex dot com>
Cc: "Laine Walker-Avina" <lwalkera at ieee dot org>, gcc-help at gcc dot gnu dot org
Date: Tue, 10 Jul 2007 23:40:38 -0400
Subject: Re: Cross gcc build problem
References: <1183746611.24944.5.camel@Anor> <468EB4B1.AF8FB4F4@dessent.net> <77172DF1-FA30-43D7-8CB4-496CCF8E3A24@ieee.org> <46933F1B.9020707@mbnet.fi> <E58D6F68-60CE-4259-9FBD-F39FD49342B8@ieee.org> <4693F48C.1060205@avtrex.com>

On 7/10/07, David Daney <ddaney@avtrex.com> wrote:

If that is because you are bootstrapping a toolchain, then you should
disable the generation of a shared version of libgcc by supplying
something like --disable-shared to the GCC configure.


Would you need just "disable-shared", or both that as well as
"enable-static"?  Is specifying both required, or is that redundant?

Follow-Ups:
- Re: Cross gcc build problem
  - From: Kai Ruottu

References:
- Cross gcc build problem
  - From: Laine Walker-Avina
- Re: Cross gcc build problem
  - From: Brian Dessent
- Re: Cross gcc build problem
  - From: Laine Walker-Avina
- Re: Cross gcc build problem
  - From: Kai Ruottu
- Re: Cross gcc build problem
  - From: Laine Walker-Avina
- Re: Cross gcc build problem
  - From: David Daney

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