On Thu, May 5, 2011 at 2:40 PM, Juho Snellman <jsnell@iki.fi> wrote:
On Wed, May 4, 2011 at 9:36 PM, Elliott Slaughter <elliottslaughter@gmail.com> wrote:
On Wed, May 4, 2011 at 12:31 PM, David Lichteblau <david@lichteblau.com> wrote:
Hi,

Quoting Elliott Slaughter (elliottslaughter@gmail.com):
> Could you please take a look at https://bugs.launchpad.net/sbcl/+bug/777339 ?
> I can't build on MinGW without this patch.

shouldn't it test whether the gcc in PATH is a cygwin gcc, rather than
just whether uname indicates cygwin?

Quite possibly. I could write such a patch for that later today if you think that's a better idea than my current patch.

That would be a nicer approach. If you have time to do it, that'd be great. If not, I can apply the existing patch.

How about this:

https://bugs.launchpad.net/sbcl/+bug/777339/+attachment/2115633/+files/patch2.txt

I checked gcc --version for the string "cygming". I'm not sure how dependable that is, but it works on my copy of Cygwin. At any rate, from the output of gcc --version (copied below) I don't think there is anything better to search for.

Cygwin:
$ gcc --version
gcc (GCC) 3.4.4 (cygming special, gdc 0.12, using dmd 0.125)
Copyright (C) 2004 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

MinGW:
$ gcc --version
gcc.exe (GCC) 4.5.2
Copyright (C) 2010 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

--
Elliott Slaughter

"Don't worry about what anybody else is going to do. The best way to predict the future is to invent it." - Alan Kay