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: me at cgf dot cx
Cc: gcc at gcc dot gnu dot org, rridge at csclub dot uwaterloo dot ca, cgf at gnu dot org
Date: Thu, 25 Aug 2005 16:00:53 -0400
Subject: Re: [patch] Fix i386-mingw32 build failure
References: <20050810212033.83073A8549@perpugilliam.csclub.uwaterloo.ca> <200508102130.j7ALU3hP009749@greed.delorie.com> <20050811182004.GA13060@trixie.casa.cgf.cx> <20050825185200.GB32464@trixie.casa.cgf.cx> <200508251859.j7PIxOkh005144@greed.delorie.com> <20050825195423.GB998@trixie.casa.cgf.cx>

> So, should it default to finding an executable on the path first and
> then look for MinGW/MSYS versions of the program if it can't find
> the executable on the path?

Hmmm... 99% of the cases will be "#!/bin/sh" anyway.  What's the
"right" shell to run for that in MinGW?  If you can detect MinGW[*],
and check the right MinGW places first, that's probably the best
solution.

[*] I'm thinking of an #ifdef in libiberty, nothing fancy.

Follow-Ups:
- Re: [patch] Fix i386-mingw32 build failure
  - From: Christopher Faylor

References:
- Re: [patch] Fix i386-mingw32 build failure
  - From: Ross Ridge
- Re: [patch] Fix i386-mingw32 build failure
  - From: DJ Delorie
- Re: [patch] Fix i386-mingw32 build failure
  - From: Christopher Faylor
- Re: [patch] Fix i386-mingw32 build failure
  - From: Christopher Faylor
- Re: [patch] Fix i386-mingw32 build failure
  - From: DJ Delorie
- Re: [patch] Fix i386-mingw32 build failure
  - From: Christopher Faylor

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