From: john_r_velman@mail.hac.com
To: gnu-win32@cygnus.com
Subject: \r\n, DJGPP and gnu-win (Was: Re[2]: tar, zip, gzip troubles
Date: Thu, 15 Oct 1998 06:06:00 -0000 [thread overview]
Message-ID: <0F0T0097FXQ5Q4@mail.hac.com> (raw)
I used the DJGPP environment under dos for years without ever having
to worry about this problem. In addition to all the ports working as
promised, I was able to successfully do some ports myself (the most
exotic being scm). The applications I used with no problems included
bash, emacs, vim, less, genscript, TeX, autoconfig, configure, make,
various shell scripts, perl, my own perl scripts, and on and on. I
simply never worried about the \r\n issue. I did see it discussed
occaisionally on the DJGPP newsgroup. My setup was a very standard
dos 6.something, windows3.something (both plain and for work groups at
various times).
On NT with gnu-win, I've finally made things work by setting my entire
cygnus tree to text = binary in the mount table. I'll admit that I
now have few problems, but I really should be able to run with no
problems without messing with the registry.
Can someone explain why there are few if any problems with the way
DJGPP handles this, and why there is a more or less continuous stream
of problems with this in gnu-win?
Well, I hope this doesn't sound like a major complaint. I give hearty
thanks to all the people who have done so much to provide the cyg-win and
gnu-win environment, and realize that this is still early in its
evlolution.
John Velman
jrvelman@mail.hac.com
______________________________ Reply Separator
_________________________________
Subject: RE: tar, zip, gzip troubles
Author: Hoenicka@pbmail.me.kp.dlr.de at mime
Date: 10/13/98 7:19 AM
>>This smacks of the old binary/text problem. It doesn't sound like you
have set your mounts (mount -b) or CYGWIN32 (binmode) variable to binary
mode so I suggest you look there first.<<
Oh yes, this cured the problem (although I had to strip the \r's from my
.bashrc to restart bash successfully). However, as Earnie Boyd pointed out,
this seems to be more a workaround than a fix and I'll try to modify the
zip/unzip sources to fix the problem (may take years, though).
Thanks a lot
Markus
_________________________
Dr. Markus Hoenicka
DLR Inst. Aerospace Medicine
D-51170 Cologne, Germany
Hoenicka@pbmail.me.kp.dlr.de
Phone: ++49-2203-601-3101
Fax: ++49-2203-61159
_________________________
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
reply other threads:[~1998-10-15 6:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=0F0T0097FXQ5Q4@mail.hac.com \
--to=john_r_velman@mail.hac.com \
--cc=gnu-win32@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).