From: Ulrich Koehler <koehler@mvt.tu-clausthal.de>
To: cygwin@sourceware.cygnus.com
Subject: LF vs. CR/LF (WAS: Problems with libtiff!)
Date: Wed, 30 Jun 1999 22:10:00 -0000 [thread overview]
Message-ID: <376E2969.4AA1BA97@mvt.tu-clausthal.de> (raw)
Message-ID: <19990630221000.9p5kzfuo1I-34PSoWXNYrGNngKt0QT6OkIA2nj4rcSE@z> (raw)
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@sourceware.cygnus.com
next reply other threads:[~1999-06-30 22:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-21 5:02 Ulrich Koehler [this message]
1999-06-30 22:10 ` Ulrich Koehler
-- strict thread matches above, loose matches on Subject: below --
1999-06-30 22:10 Parker, Ron
1999-06-21 9:17 Earnie Boyd
1999-06-30 22:10 ` Earnie Boyd
1999-06-21 8:19 Peter Ring
1999-06-30 22:10 ` Peter Ring
1999-06-21 7:22 Earnie Boyd
1999-06-30 22:10 ` Earnie Boyd
1999-06-21 7:10 Earnie Boyd
1999-06-30 22:10 ` Earnie Boyd
1999-06-21 5:10 Demmer, Thomas
1999-06-30 22:10 ` Demmer, Thomas
1999-06-18 12:14 Parker, Ron
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=376E2969.4AA1BA97@mvt.tu-clausthal.de \
--to=koehler@mvt.tu-clausthal.de \
--cc=cygwin@sourceware.cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).