Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender:	cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin AT sourceware DOT cygnus DOT com
Message-ID:	<376E2969.4AA1BA97@mvt.tu-clausthal.de>
Date:	Mon, 21 Jun 1999 14:00:41 +0200
From:	Ulrich Koehler <koehler AT mvt DOT tu-clausthal DOT de>
Organization:	Technische Universit"at Clausthal
X-Mailer:	Mozilla 4.5 [en] (X11; I; HP-UX B.10.20 9000/715)
X-Accept-Language:	de-DE, de, en
MIME-Version:	1.0
To:	cygwin AT sourceware DOT cygnus DOT com
Subject:	LF vs. CR/LF (WAS: Problems with libtiff!)

Hello,

first of all: thank you for your help!
This RTFM! goes to me. I was not aware of the CR/LF
problem and the differences between text and binary
mode because I never browsed through the documentation.
I did not even know that you can open files in text-mode,
it sounds like a strange idea to me. Because I'm working
on many platforms, I create and edit only text files with
UNIX-style line-endings on Windows and I'm trying to keep
my environment CR/LF-free.

Will I experience problems within the cygwin-environment,
if I use only text=binary mounts?

BTW:
I've changed the single open() call in the libtiff-source to
open the file as binary ( If I remember correctly the value
O_BINARY is defined, I added '|0x100000' to the mode bits).
It now seems to work now even with
my default text!=binary mount. I could compile and link
my application and used it without problems.
I wrote 'it seems to work', because the 'thumbnail' binary
still does not work. Maybe there is another reason why,
'tiff2ps' does work.
I do not have the knowlegde to make a complete port using
the configure script and I still want to be sure that I did
the right thing.

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -