Delivered-To: listarch-cygwin AT sourceware DOT cygnus DOT com
Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
From: Christopher Faylor <cgf AT cygnus DOT com>
Message-ID: <19990203215336.B12292@cygnus.com>
Date: Wed, 3 Feb 1999 21:53:36 -0500
To: mlx AT san DOT rr DOT com, gnu-win32 AT cygnus DOT com
Subject: Re: Soft links givin' me as hard time !!!
References: <199902031736 DOT JAA07743 AT proxyb1-atm DOT san DOT rr DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93i
In-Reply-To: <199902031736.JAA07743@proxyb1-atm.san.rr.com>; from Steve Biskis on Wed, Feb 03, 1999 at 09:36:53AM -0800

On Wed, Feb 03, 1999 at 09:36:53AM -0800, Steve Biskis wrote:
>Hi all,
>
>Trying to build the 20.1 development sources and keep
>hitting a snag.  Seems to involve soft links.  I didn't
>realize the CygWin stuff supported them - cool, EXCEPT.
>
>After configuring make will choke on any of the little 
>"!<symlink> ..." magic files it comes accross.
>
>For instance, during a make, the egcs distribution sets up 
>an "ln -s" of ./gcc.c to ./g++.c .  This causes the file: g++.c
>with the following contents: !<symlink>./gcc.c .
>
>Now, when make come accross this file, I get:
>
>g++.c:1 parse error before '!'
>
>Now, if I edit the makefile, stopping it from deleting & then
>recreating this "link" and either copy gcc.c to g++.c or do
>an actual UNIX ln -s on the fileserver, I'm OK.
>
>I should mention that all the target files are actually on a
>FreeBSD file system shared with Samba.  All the binary
>tools and headers are on the win32 compile host.

Symbolic links need to have the "S"ystem bit set.  That probably
is not happening on a Samba drive.
--
cgf AT cygnus DOT com
http://www.cygnus.com/