From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21123 invoked by alias); 30 Jul 2007 16:36:20 -0000 Received: (qmail 21112 invoked by uid 22791); 30 Jul 2007 16:36:20 -0000 X-Spam-Check-By: sourceware.org Received: from an-out-0708.google.com (HELO an-out-0708.google.com) (209.85.132.247) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 30 Jul 2007 16:36:15 +0000 Received: by an-out-0708.google.com with SMTP id d14so307376and for ; Mon, 30 Jul 2007 09:36:13 -0700 (PDT) Received: by 10.100.135.16 with SMTP id i16mr4692829and.1185813373250; Mon, 30 Jul 2007 09:36:13 -0700 (PDT) Received: from ?192.168.1.238? ( [66.194.253.20]) by mx.google.com with ESMTPS id h16sm2531989wxd.2007.07.30.09.36.12 (version=SSLv3 cipher=RC4-MD5); Mon, 30 Jul 2007 09:36:12 -0700 (PDT) Message-ID: <46AE1380.10107@kitware.com> Date: Mon, 30 Jul 2007 16:36:00 -0000 From: Bill Hoffman User-Agent: Thunderbird 1.5.0.12 (Windows/20070509) MIME-Version: 1.0 To: cygwin-apps@cygwin.com Subject: Re: CMake 2.4.7-1 ready References: <46A4BECD.2020404@kitware.com> <20070723151059.GE19692@calimero.vinschen.de> <46AA0F00.6060507@kitware.com> <46AA45A9.9010503@kitware.com> <46ACABB7.3030609@rajaratnam.dk> <46ADF9D5.9080301@kitware.com> <46AE0CE2.FEE13138@dessent.net> In-Reply-To: <46AE0CE2.FEE13138@dessent.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-apps-help@cygwin.com; run by ezmlm Precedence: bulk Sender: cygwin-apps-owner@cygwin.com List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Mail-Followup-To: cygwin-apps@cygwin.com X-SW-Source: 2007-07/txt/msg00240.txt.bz2 Brian Dessent wrote: > Bill Hoffman wrote: > > >> OK, I am lost here. Apparently my recent CMake 2.4.7 files are broken >> for cygwin setup for some reason. Has anything changed in cygwin setup >> recently in the untar section? Is there a more verbose mode that setup >> can be run in? >> > > No, nothing's changed in the untar code in forever. I debugged it and > the problem is that setup does not recognise the file as a valid tar > archive. What version of tar did you use to create it? > > We are using lib tar to create it. It is part of CMake called CPack which is used to create various packages automatically. It worked fine for the last release of cmake, and it works fine from tar on the command line. The command line tar must be more forgiving. I will try to figure out where the magic has gone... Thanks much, for looking into this for me. -Bill