Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <010401c2d041$e76060e0$78d96f83@pomello> From: "Max Bowsher" To: , References: <000901c2d022$869cbe80$0200a8c0 AT ufo> Subject: Re: cygwin symlink? bug Date: Sun, 9 Feb 2003 13:48:19 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Trevor Forbes wrote: > I am having problem with some of my build scripts and the following > demonstrates the problem: > > If run the following (as a script) I get -- /tmp/foo/bar > # !/bin/bash Are you sure? I can reproduce your results only if I change the shebang to /bin/sh. > cd /tmp; mkdir -p foo/bar; ln -f -s foo/bar bar; cd bar; pwd; cd .. > > If I type the line in a shell then I get what I expected -- /tmp/bar > > I am using cygwin-1.3.20-1 but do not I think it is a new feature. > > Is my logic correct? IIRC, Linux does this too - but I'm not easily able to test that at the moment. Max. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/