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: [patch] Fix i386-mingw32 build failure

From: Andreas Schwab <schwab at suse dot de>
To: Mark Mitchell <mark at codesourcery dot com>
Cc: Christopher Faylor <me at cgf dot cx>,GCC Development <gcc at gcc dot gnu dot org>,GCC Patches <gcc-patches at gcc dot gnu dot org>
Date: Thu, 11 Aug 2005 00:17:40 +0200
Subject: Re: [patch] Fix i386-mingw32 build failure
References: <42F4A108.1050903@gmail.com> <42F85C3F.5040602@lu.unisi.ch><20050809153745.GB29201@trixie.casa.cgf.cx><42FA33D6.8070505@codesourcery.com>

Mark Mitchell <mark@codesourcery.com> writes:

> The even more correct solution is to not build anything with the 
> compiler (including libgcc) until after it is installed.  Then, it will 
> just look where it would normally look, and all will be well.

You sure don't want to overwrite a compiler that is known to work with a
compiler that is incomplete, never tested, and perhaps completely broken.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

Follow-Ups:
- Re: [patch] Fix i386-mingw32 build failure
  - From: Mark Mitchell

References:
- [patch] Fix i386-mingw32 build failure
  - From: FX Coudert
- Re: [patch] Fix i386-mingw32 build failure
  - From: Paolo Bonzini
- Re: [patch] Fix i386-mingw32 build failure
  - From: Christopher Faylor
- Re: [patch] Fix i386-mingw32 build failure
  - From: Mark Mitchell

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