Re: Problems upgrading from 2.95.3-5 to 3.X on cygwin

I suggest you remove all '\r' characters from i386.md, so that the newlines consist of '\n' only. That will likely solve your problem. You needn't bother with insn-flags.h; that looks to be only a warning and once you get stage1 built of 3.0, it won't have problems with '\r' (but the .md file st

Re: Problems building cross compiler on NT

Mack Lobell wrote:- > Hi, > > i'm trying to build a gcc 3.0.3 cross compiler on a NT machine. Target is > powerpc, host is cygwin on a NT 4.0 workstation with SP6. > insn-flags.h:73: warning: carriage return in preprocessing directive > insn-flags.h:75: warning: carriage return in preprocessi

Re: bootstrap/5149: gcc-20011217 reads beyond EOF on cygwin

Christopher Faylor wrote:- > Can I ask why we'd be reading beyond EOF? Is it guaranteed that bytes beyond > EOF will be zero on UNIX? This was discussed in September (see thread in gcc@ entitled "Bumming cycles out of parse_identifier"). It was decided that all known current Unix implementatio