> $ uname -r > 1.3.18(0.69/3/2) $ uname -r 1.3.19(0.71/3/2)
> One fix is to use such a Cygwin version; however, if this behaviour is > not a bug, then this fix has no future. Since it is difficult to go backwards with cygwin, I'd discourage that! > Another fix is to delete the cygwin special-casing in configure.in. That fixed it! Thanks! ;) > > Maybe it's not recognizing > > that this is in fact a Unix derivative? > > Actually we are special-casing Cygwin to make Gforth behave like a > good Windows application (e.g., CRLF newlines). I guess most Gforth > users on Windows don't view Cygwin as a Unix and expect Windows-like > behaviour. So far, I have had to treat gforth on cygwin as Unix, with CR line terminators and / path separators. If this is changing, I won't be happy with all the changes I will probably have to make, but I recognize that it may be easier for you to support. I notice that I haven't had to play the same games with line terminators this time that I had to mess with last time. So I guess that means you have fixed the problems on your end. Still, it looks like there is still a hole with the latest cygwin release. You know my vote! > - anton DaR --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
