Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sourceware.cygnus.com Delivered-To: mailing list cygwin@sourceware.cygnus.com Message-ID: <38AAFA18.3DF063A0@wxs.nl> Date: Wed, 16 Feb 2000 20:27:20 +0100 From: paul van der Meij X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: cygwin Subject: tar problem Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Note-from-DJ: This may be spam I reported tar not working after applying snapshot 20000131 (stack dump on 'tar -xf , of a previous correct archive) which I think is related to the cygwin1.dll. I tried regenerating tar from 'gnu tar-1.13' which did not work. After checking the source distribution of B20, I realized that this was because B20 uses a modified 'tar-1.12' version. This raises the question will in the future the standard 'GNU' products support the 'cygwin' environment under NT 4.0 (and Win2000) ?? After regenerating 'tar' from the B20 source it worked fine again. However there is a problem with 'cat' and 'binary' versus 'text' mode. tar -cf - xxx | cat | tar -tf will result in "tar: Skipping to next file header" error, because the 'cat' replaces LF with CR/LF. I think 'cat' should not interfere 'binary' versus text. How do you change stdin and stdout to process in O_BINARY mode, ioctl .... ??? Paul -- name: Paul van der Meij email: phjvdmeij@wxs.nl -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com