From: "Earnie Boyd" <earnie_boyd@hotmail.com>
To: vischne@ibm.net
Cc: gnu-win32@cygnus.com
Subject: Re: Output redirection, file creation, and libjpeg.a
Date: Mon, 13 Oct 1997 05:07:00 -0000 [thread overview]
Message-ID: <19971013115458.20362.qmail@hotmail.com> (raw)
How is your filesystems mounted? If they are mounted text!=binary then
you will have a \r (^M) prepended to any \n. If they are mounted
text=binary, then someone else will have to give you an answer.
To mount / as text=binary:
1) cd to the bin directory
2) umount /
3) mount -b c:\\ /
- \\||//
---o0O0--Earnie--0O0o----
-earnie_boyd@hotmail.com-
------ooo0O--O0ooo-------
>Date: Sun, 12 Oct 1997 17:20:07 GMT
>To: gnu-win32@cygnus.com
>From: Victor Schneider <vischne@ibm.net>
>Subject: Output redirection, file creation, and libjpeg.a
>
>There's a curious problem with porting the jpeg-6 and jpeg-6a libraries
to
>cygwin32: They compile with no problem, and running `make test'
confirms
>that they work, but the `cjpeg' and `djpeg' utilities appear to have
>problems (a) creating files and (b) using the input and output
redirection
>operators (`<' and `>').
>
>When you generate a .gif file from a .jpg file using djpeg, you get
>`spurious symbol' error messages from lview31.exe on the resulting .gif
>file. I think that results from some problem using `>' to generate the
>resulting .gif file. I get the impression that cygwin32 uses the Dos
'>'
>operator and gets junk added in to the redirection process. Either
that, or
>bash.exe is doing something.
>
>Using the `-outputfile' option in djpeg yields an output file of zero
>length. Since this all works under other operating systems like Linux,
I
>have to assume that the problem is somewhere in the buck-passing
between
>native Dos and cygwin32.
>
>-
>For help on using this list (especially unsubscribing), send a message
to
>"gnu-win32-request@cygnus.com" with one line of text: "help".
>
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
next reply other threads:[~1997-10-13 5:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-10-13 5:07 Earnie Boyd [this message]
-- strict thread matches above, loose matches on Subject: below --
1997-10-13 10:28 Earnie Boyd
1997-10-13 9:19 Larry Hall
1997-10-13 14:33 ` Alex
1997-10-12 10:20 Victor Schneider
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=19971013115458.20362.qmail@hotmail.com \
--to=earnie_boyd@hotmail.com \
--cc=gnu-win32@cygnus.com \
--cc=vischne@ibm.net \
/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).