Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
From:	Chris Faylor <cgf AT cygnus DOT com>
Date:	Wed, 12 Jul 2000 13:44:41 -0400
To:	Cygwin <cygwin AT sourceware DOT cygnus DOT com>
Subject:	Re: untarring gcc-2.95.2-2 (howto use md5 ?)
Message-ID:	<20000712134441.A2450@cygnus.com>
Reply-To:	cygwin AT sourceware DOT cygnus DOT com
Mail-Followup-To:	Cygwin <cygwin AT sourceware DOT cygnus DOT com>
References:	<NDBBJCODCILMGGMPECDMOEFACIAA DOT mvdv AT bigfoot DOT com> <396C93E5 DOT 5EC54FB4 AT ece DOT gatech DOT edu>
Mime-Version:	1.0
User-Agent:	Mutt/1.2i
In-Reply-To:	<396C93E5.5EC54FB4@ece.gatech.edu>; from cwilson@ece.gatech.edu on Wed, Jul 12, 2000 at 11:51:01AM -0400

On Wed, Jul 12, 2000 at 11:51:01AM -0400, Charles Wilson wrote:
>Mark -
>  this error is because /libiberty (the directory) is created as a link
>to ../../libiberty or something like that. Remove the libiberty link,
>and 'mkdir libiberty' instead. Then, 'tar xvzf gcc-2.95.2-2/libiberty/*'
>
>  This isn't technically a packaging error, because the src tarball is
>built to be unpackaged as part of a larger 'src' directory including
>binutils and cygwin/winsup, which all use a shared libiberty directory.

It is a packaging error.  The symbolic link should not have made it into
the tar ball.  The source files in libiberty are in the tar file but the
symbolic link masks that.

You should be able to get around this by first creating the libiberty directory
and then do the extraction.  You should get an error but then the extraction
should proceed as normal.

I'm intrigued by the mention of "Mumit's patch" here, though.  What is this
patch?  Is Mumit ready to take back the gcc reins?

cgf
>Mark Van De Vyver wrote:
>> 
>> Hi,
>> I've had trouble untarring gcc-2.95.2-2-src.tar.gz (13,077,613 bytes)
>> the type of message I get is:
>> tar: gcc-2.95.2-2/libiberty/xstrerror.c: Could not create file: No such file
>> or directory
>> 
>> Things went fine for gcc-2.95.2 tho after applying Mumit's patch and the
>> pgcc patch (without errors) the make failed (configure went ok) so I thought
>> I'd try and build a vanilla gcc before asking what went wrong there...
>> So pulled the latest sources down from aarnet.edu.au now tar zxf ... fails
>> as a 'check' I tried opening up the gz file with winzip and sure enough it
>> complained about the libiberty directory.
>> 
>> The only thing I can think of is that the mirror is bad? but I'm not sure
>> how to use md5 to check (which I'm assuming is the purposes of the md5.sum
>> files).  Is there any receipe for using md5?  Found nought in quick search
>> of the User guide web pages or archives.
>> 
>> Note I've built the autoconf, perl and automake files (I think) without
>> error

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -