Surprises running gcc 3.2 configure on Cygwin

2002-09-22 Thread David A. Cobb
The first surprise was that everything (configure, make-bootstrap, make-check) worked! That's a surprise because it was consistantly failing only a few days ago and I didn't notice anything changing except the phase of the moon. The following observations may not be bugs (except the first).

Re: Surprises running gcc 3.2 configure on Cygwin

2002-09-22 Thread Tim Prince
On Sunday 22 September 2002 17:20, you wrote: IN THE VERY FIRST COMPILER TEST, I get these: ignoring nonexistent directory ../../include/w32api ^^^ GNU CPP version 3.2 20020912 (prerelease) (cpplib) (80386, BSD syntax) GNU C version 3.2 20020912 (prerelease)

Re: Surprises running gcc 3.2 configure on cygwin

2002-09-22 Thread Christopher Faylor
On Sun, Sep 22, 2002 at 07:08:21PM -0700, Tim Prince wrote: SEEMS STRANGE to have one and not the other. DOES IT MATTER? Since vfork is not a standard C function, no one says there need be such a header. There are bigger isssues with vfork on Windows, see the list archive. I'm not aware of

Re: Surprises running gcc 3.2 configure on Cygwin

2002-09-22 Thread Nathanael Nerode
A lot of the weirdness in configure and make is due to the weird non-autoconf configure script used at the top level. I'm working on autoconfiscating it, though it takes a while. This probably accounts for the missubstitution in the Makefile, and some of the false negatives. --Nathanael Nerode