Gettext build/use issue on Cygwin

[Eric Blake]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

According to Mark Moriarty on 3/14/2006 8:01 PM:
> With older cygwin gettext, 0.14.1, during the bootstrap the autopoint would
> generate:
> tar: Skipping to next header
> tar: Archive contains obsolescent base-64 headers
> gzip: stdin: invalid compressed data--crc error
> gzip: stdin: invalid compressed data--length error
> tar: Error exit delayed from previous errors Copying file ABOUT-NLS 

Which version of tar?  Following the directions here:
> Problem reports:       http://cygwin.com/problems.html

and including a text attachment of cygcheck -svr output would have been
helpful.  Also, I wonder if you are experiencing data corruption due to a
text mount (again, cygcheck output would have made that obvious).

At any rate, I don't know if the gettext archive really does have weird
stuff in it, or if tar is mishandling a valid archive.  I am currently
working on putting together a tar 1.15.90 release, which has a number of
bug fixes beyond the current 1.15.1, so maybe that will help your issue.

- --
Life is short - so eat dessert first!

Eric Blake             ebb9@byu.net
volunteer cygwin tar maintainer
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.1 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEF5n684KuGfSFAYARAuZuAJwMTt97srAClNHnGlvZBIWqB6edaACgi28u
SI24++Ku4TEhRsZfa+fJPl8=
=JNm7
-----END PGP SIGNATURE-----

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/