ok - i fixed the problem in the ghostscript port - how do i go about getting the fix back into the cygwin distro?
p.s. the link you sent me to is very clear about what the CYGWIN=binmode achieves - however, another part of the cywin manual (the one i happened to be reading: http://cygwin.com/cygwin-ug-net/using-textbinary.html) is not nearly so clear which led to my confusion > On Fri, Dec 07, 2001 at 10:43:11AM -0500, Gregory W. Bond wrote: > > thanks for the reply larry - i realize that fixing the ghostscript port would > > be a solution, but my impression from reading the cygwin user manual is that > > setting CYGWIN to binmode could serve as a workaround - in my case it didn't > > and i don't understand why - i'm beginning to suspect that cygwin is ignoring > > that i've set CYGWIN to binmode which would be a cygwin bug > > That's not what the CYGWIN=binmode setting is for. > > http://cygwin.com/cygwin-ug-net/using-cygwinenv.html > > The workaround you're talking about would be to use binary mount points. > > Corinna > -- Gregory W. Bond AT&T Labs - Research 180 Park Avenue, Rm. D273, Bldg. 103 P.O. Box 971, Florham Park, NJ, 07932-0971, USA tel: (973) 360 7216 fax: (973) 360 8187 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
