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
Message-ID:	<396F2A0D.26D755CD@ece.gatech.edu>
Date:	Fri, 14 Jul 2000 10:56:13 -0400
From:	Charles Wilson <cwilson AT ece DOT gatech DOT edu>
X-Mailer:	Mozilla 4.73 [en] (Windows NT 5.0; U)
X-Accept-Language:	en
MIME-Version:	1.0
To:	Mark Van De Vyver <mvdv AT bigfoot DOT com>
CC:	Cygwin <cygwin AT sourceware DOT cygnus DOT com>, nso AT manbw DOT dk,
	"Craveiro, Marco" <Marco DOT Craveiro AT solvay DOT com>
Subject:	Re: gcc-2.95.2-2 build problem (src tar ball problem?)
References:	<NDBBJCODCILMGGMPECDMOEHBCIAA DOT mvdv AT bigfoot DOT com>

Mark Van De Vyver wrote:
> 
> actually I've created common/liberty just about everywhere (they are not
> mounted - matters?)
> 
> /common/libiberty
> /src/common/libiberty
> /src/gcc-2.95.2-2/common/libiberty
> /usr/common/libiberty  (!)
> 

No no no. You don't need to create the *target* of the symlink. Create a
directory: 'gcc-2.95.2-2/libiberty'. Then, when tar tries to unpack the
symlink, *that* operation will fail, but then unpacking
gcc-2.95.2-2/libiberty/* will work okay.

--Chuck

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

- Raw text -