reading.open?

[Øystein Johansen]

> Find the specs file, and make sure that it doesn't contain DOS style
> line-endings, ie., it should have '\n', not '\r\n' (or whatever the
> DOS sequence is). `gcc -print-file-name=specs` tells you where the
> file is. You can use recode to change this, or the simplest way is
> to load the file in vim, :set ff=unix, and write it back out (at least
> I think it works).

Except that I'm using Elvis. >:-)

But your tip worked perfect! How can I ever thank you!

> When developing on Cygwin, I strongly recommend using 
> binary-only mounts if you care about not wasting time on these > ridiculous issues.

That would be nice, at the Cygwin computer I got everyting on the C:
drive. How do mount (remount) this binary? Put something in
Cygwin.bat?

> At the
> same time, you need to make sure your code will work regardless of
> what EOLs are on the system. Unfortunately, lots of Unix code was
> not written to be portable in this regard.

I'll try to keep that in mind!

> 
> I have a another-yet-to-be submitted patch to make gcc specs reader > handle this issue.

Looking forward to that!
 
Thanks,
Øystein