Sender: RUPP AT gnat DOT com
Message-ID: <3305B8F6.3A3C5027@gnat.com>
Date: Sat, 15 Feb 1997 13:24:06 +0000
From: Douglas Rupp <rupp AT gnat DOT com>
Organization: Ada Core Technologies
MIME-Version: 1.0
To: djgpp-workers AT delorie DOT com
Subject: fstat returns garbage
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

This is on NT 4.0 w/ djgpp v2.01.

On a recursive call to make to bootstrap gnat1, the just-built compiler
is getting bad information from fstat on it's first compilation for the
second compiler, e.g. gcc -c -B../stage1 ...

fstat is returning a normal successful error code on a valid file
descriptor for a regular file (ada.ads), but the st_mode field contains
a value of 0x21a4 (a character special device??) and an st_size of 0
bytes.

If I just start it up again it works fine, so it's not a bad stage1
compiler.  If I short-circuit the Makefile so that make.exe just
recursively calls itself without doing the intermediate compilations it
works fine, so it's not a problem with recursive make's per se.  I've
got the _default.pif file set up to use all available memory (32 Megs)
and lots of FILES= in config.sys.

I've insert a call to "mem.exe" in the default compilation rule and that
looks ok and I've monitored the go32-v2 status from another window (is
that valid?) and that looks ok.  I've also monitored the NT diagnostics
window and the Performance Monitor display for every conceivable
resource and it all looks ok.

I'm out of ideas, anybody got any?