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: Fwd: gcc 4.2.0 compilation failing on x86_64 machine

From: Tim Prince <tprince at myrealbox dot com>
To: Ryan Propper <cardinalfan at gmail dot com>
Cc: gcc-help at gcc dot gnu dot org, Alexander Wieder <awieder at tempel dot dynamischer-diskord dot de>
Date: Wed, 18 Jul 2007 09:10:20 -0700
Subject: Re: Fwd: gcc 4.2.0 compilation failing on x86_64 machine
References: <627a240707161215v65a1a3f3v2ebef62b03039f36@mail.gmail.com> <469C8ADD.4040903@tempel.dynamischer-diskord.de> <627a240707180903i2c879834uccd4b6df22477c40@mail.gmail.com>
Reply-to: tprince at computer dot org

Ryan Propper wrote:

Hi all,

See the thread below.  It appears that not having "gnu/stubs-32.h" is
a common problem on some AMD and other 64-bit machines, resulting in
compilation errors.

The solution that worked for both me and Alexander was to use the
"--disable-multilib" configuration flag.  However, we did not see this
documented in any FAQs or in the output of "configure --help".  We
think other users might benefit if this solution was more widely
publicized.

Which situation? That x86-64 has optional 32-bit support, but attempting to use it without installing all bits is likely to fail?

Follow-Ups:
- Re: Fwd: gcc 4.2.0 compilation failing on x86_64 machine
  - From: Kai Ruottu

References:
- gcc 4.2.0 compilation failing on x86_64 machine
  - From: Ryan Propper
- Re: gcc 4.2.0 compilation failing on x86_64 machine
  - From: Alexander Wieder
- Fwd: gcc 4.2.0 compilation failing on x86_64 machine
  - From: Ryan Propper

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