> > That's a known Cygwin bug. Basically, they changed the default file > > mode to binary but didn't fix the rest of their software to only > > output \n instead of \r\n. > > > > The fallback code should be picking up the proper defaults, however. > > I beleive that Cygwin updated on this issue. The current installer > offers to automatically change line endings or stick with Unix line > endings. Doing something "automatically" usually means "hiding it > from the user", so please choose "keep Unix line endings" instead and > update to the newest Cygwin. > > Let me know it that fixes your issues.
For the record, I don't have any problems building the 1.1.x-current branch with cygwin enabled or disabled. Yes, I remember all too well. At the time I was concerned it would be the last straw for cygwin support. I do always use "the Unix line endings" but maybe it is time for a full rebuild instead of just an update. I am using the latest setup.exe as well. I think you are correct that this has been address by the CygWin folks. If I remember correctly, I used to get the problem with both --enable and --disable. Believe me, I've been following all along. I read the newsgroup with my coffee every morning. :) Mark _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
