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: DJ Delorie <dj at redhat dot com>
To: mark at codesourcery dot com
Cc: drow at false dot org, me at cgf dot cx, gcc at gcc dot gnu dot org, gcc-patches at gcc dot gnu dot org
Date: Wed, 10 Aug 2005 14:35:41 -0400
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> <20050810173305.GA29723@nevyn.them.org> <42FA3B92.6040200@codesourcery.com>

> I still think it's a bad solution, though; it's imposing special
> semantics for process execution in libiberty, rather than the normal
> ones that you would expect from the OS.

Doing that is part of the purpose of libiberty.  If the OS does
something unusual, we try to make it act in a conforming way, so that
the rest of the tools need not worry about the OS differences.  Adding
support for #! scripts is one of the ways we can make MinGW more
conforming (Cygwin and DJGPP already support #!) to the norm.

Follow-Ups:
- Re: [patch] Fix i386-mingw32 build failure
  - From: Joe Buck

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