Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Message-ID: <396F2A0D.26D755CD@ece.gatech.edu> Date: Fri, 14 Jul 2000 10:56:13 -0400 From: Charles Wilson X-Mailer: Mozilla 4.73 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Mark Van De Vyver CC: Cygwin , nso@manbw.dk, "Craveiro, Marco" Subject: Re: gcc-2.95.2-2 build problem (src tar ball problem?) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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@sourceware.cygnus.com