Date: Wed, 5 Dec 2007 23:51:01 -0500
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Installing on a Samba share drive
Message-ID: <20071206045101.GA5219@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <475712A9 DOT 5010800 AT hawaiian DOT net> <47577067 DOT 2070404 AT cygwin DOT com> <20071206042618 DOT GA4580 AT ednor DOT casa DOT cgf DOT cx> <47577CDE DOT 9050507 AT cygwin DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <47577CDE.9050507@cygwin.com>
User-Agent: Mutt/1.5.16 (2007-06-09)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

On Wed, Dec 05, 2007 at 11:38:54PM -0500, Larry Hall (Cygwin) wrote:
> Christopher Faylor wrote:
>> On Wed, Dec 05, 2007 at 10:45:43PM -0500, Larry Hall (Cygwin) wrote:
>>> Tom Leonard wrote:
>>>> Hi,
>>>> I created a Samba share on my Debian system, mapped it to a drive letter 
>>>> on my XP Home system and did a full network install of Cygwin on the 
>>>> root of the mapped drive.  When I tried to use Cygwin to compile some 
>>>> programs, I found that a number of the symbolic links from the install 
>>>> (eg all of the low level .exe's like am.exe from gcc) could not be 
>>>> found.  While I could manually create the necessary symbolic links, it 
>>>> was impossible to know what exactly was broken.  I resolved the issue by 
>>>> "uninstalling" from the Samba drive and reinstalling on a local XP 
>>>> drive.
>>>> Can anyone shed some light on why the symbolic links might be broken.  
>>>> Because I need to support different library configurations, I'd like to 
>>>> use the technique of maintaining a number of different Cygwin 
>>>> environments on my Debian system where I have lots of disk space, and 
>>>> map to XP as and when needed.
>>>
>>> System attribute of the symlinks weren't/couldn't be set?
>> You're showing your age, Larry.  :-) .lnk files shouldn't have system
>> attributes.  They should just be readonly.  But that would be the case if
>> a *cygwin* cp/tar/cpio/etc. command was used to create the files.
>
>
> Has 'setup.exe' finally been updated to create .lnk file style symlinks?
> Guess it has been a while since I've wandered through that code. :-)

Ah, good point.  I was actually thinking this might have been the same
thing that as someone on IRC was reporting where I thought they said
that they just saw .lnk files but I see now that this wasn't mentioned
above.  Sorry about that.

Same answer, though.  Using cygwin utiltities to create the files should
rectify the problem.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/