zsh-workers
 help / color / mirror / code / Atom feed
From: "Vin Shelton" <acs@alumni.princeton.edu>
To: cygwin@cygwin.com
Cc: zsh-workers@sunsite.dk
Subject: Re: gunzip 1.3.5 error reading from stdin on Cygwin
Date: Sun, 29 Oct 2006 08:14:27 -0500	[thread overview]
Message-ID: <20a807210610290514k7f17abdfja21c611b45ff468b@mail.gmail.com> (raw)

(added cc: to zsh-workers.  The original message can be found at
http://www.mail-archive.com/cygwin@cygwin.com/msg73620.html )

Vin Shelton wrote:
> After upgrading my system this morning, I'm getting an error running
> gunzip when it reads from stdin.
>
> Steps to reproduce:
>
>     wget ftp://ftp.gnu.org/gmp/gmp-4.2.1.tar.gz
>     gunzip < gmp-4.2.1.tar.gz >/dev/null
>
> This sequence yields the following errors:
>
>     gunzip: stdin: invalid compressed data--crc error
>
>     gunzip: stdin: invalid compressed data--length error
>
>
> Interestingly,
>
>     gunzip gmp-4.2.1.tar.gz
>
> works.

I've narrowed this down a little bit.  It only happens under zsh;
under bash, the recipe works without error.  Thinkging that for some
reason, stdin was being opened in a text mode, I tried setting
CYGWIN=binmode before starting zsh, but that had no effect on this
problem.

I believe the upgrade that broke this was the most recent
gettext/libintl upgrade.  In order to link against the most recent
libintl, I have rebuilt zsh from source (both from the cygwin source
tarball and also from the latest zsh sources in CVS), but still the
problem persists.

I would appreciate any help that can be offered.

Thanks,
  Vin

-- 
The Journey by Mary Oliver
http://www.poemhunter.com/p/m/poem.asp?poet=6771&poem=30506


             reply	other threads:[~2006-10-29 13:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-29 13:14 Vin Shelton [this message]
2006-10-29 17:52 ` Bart Schaefer

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=20a807210610290514k7f17abdfja21c611b45ff468b@mail.gmail.com \
    --to=acs@alumni.princeton.edu \
    --cc=cygwin@cygwin.com \
    --cc=zsh-workers@sunsite.dk \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).