X-Spam-Check-By: sourceware.org
From: "Dave Korn" <dave DOT korn AT artimi DOT com>
To: <cygwin AT cygwin DOT com>
References: <BF28B531A8C7E3409A8AC9C741CB580004BA0895 AT nwhqsemail01 DOT WSDOT DOT LOC> <461D6DBB DOT 1000301 AT cygwin DOT com> <BF28B531A8C7E3409A8AC9C741CB580004BA08C3 AT nwhqsemail01 DOT WSDOT DOT LOC> <461D7F29 DOT 10405 AT cygwin DOT com> <BF28B531A8C7E3409A8AC9C741CB580004BA0932 AT nwhqsemail01 DOT WSDOT DOT LOC>
Subject: RE: bash: tar: command not found
Date: Thu, 12 Apr 2007 16:26:57 +0100
Message-ID: <014a01c77d17$0206ac20$2e08a8c0@CAM.ARTIMI.COM>
MIME-Version: 1.0
Content-Type: text/plain; 	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <BF28B531A8C7E3409A8AC9C741CB580004BA0932@nwhqsemail01.WSDOT.LOC>
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

On 12 April 2007 16:19, Cheney, Christian wrote:

>>> Don't extract things using non-Cygwin tools unless you really know what
>>> you're doing (or have been told to do so).  You can make a real mess doing
>>> this.
> I would've used CYGWIN, but, unfortunately, tar didn't work ;)

  You've destroyed your installation.

  See, we told you it was bad.

  Specifically, you've gone and created a real /usr/bin directory, when
normally it is only a mount point that mirrors /bin.  That's because winzip
doesn't know about cygwin mountpoints.  If it had been untarred by an earlier
cygwin tar, or by setup.exe which *does* respect cygwin mountpoints, it would
have ended up in the right place: /bin, and been *visible* in /usr/bin too.

  This means that tar.exe has been unpacked into C:\cygwin\usr\bin.  That's
why setup thinks it's installed.  But you can't find it in your $PATH or
anything, because when cygwin goes to look in /usr/bin (which is where tar.exe
has been put by winzip), it actually looks in your /bin dir.  And doesn't find
it.

  That's why setup thinks it's installed but cygcheck reports "Not Found:
tar".

  The fix would be to go into your C:\cygwin\usr directory, using a DOS shell
or windows explorer, and delete the bin dir.  Then re-run setup.exe, telling
it to "install from local directory", just click on ok to everything all the
way through, and it should reinstall everything that you deleted to the
correct place.


>>> FWIW, 'setup.exe' reports 'tar-1.16.1-1.tar.bz2' as a 696K file.
> I guess it doesn't really make sense to send the unzipped file, but I
> was referring to tar-1.16.1-1.tar, which is 2MB.

  Whatever you do, please do not send this to the list!  (And I don't want it
either; I suspect the file itself is good, and it's only your use of winzip
that has caused the problem).


    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....


--
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/