from David Given:
Is anyone aware of any problems with the file system (potentially only
showing up on slow machines) where closing a file and then immediately
reopening it will fail?
The context is: I am the sort of maintainer for a compiler suite, the
Amsterdam Compiler Kit: http://tack.sourceforge.net/
This is failing to build, in a rather odd fashion --- I'm getting spurious
file-not-found errors as one stage of the compiler is failing to open an
intermediate file provided by a previous stage.
The way the ACK works is that there are lots of different passes, all
running one after the other, all communicating via quite a lot of temporary
files; e.g. the optimiser stage uses five or so files *per stage*, and
there are six or seven stages. So it's possible that the ACK is exercising
this part of the system rather harder than, say, gcc is.
And, of course, this only manifests during a full build. Just running the
compiler from the command line doesn't make this happen.
Has anyone observed anything similar?