Tim Rowledge wrote:

> One reason I have seen for this appearing to happen is
> the line-ends being wrong. Some compilers will read the file but 'ignore' it.
> They don't report not being able to open the file, but they behave
> as if it wasn't there!

Something similar happens with gcc 2.7.2 on OS/2 when compiling
interp.c.
gcc complains on the first line if fed with the generated interp.c, but
if I add an empty line at the very top of the file, everything seems OK.
(In fact I don't know why this is so.)

Boris