X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-0.6 required=5.0 	tests=AWL,BAYES_00,FH_DATE_PAST_20XX,SPF_HELO_PASS
X-Spam-Check-By: sourceware.org
Message-ID: <4B3E6E98.8000109@veritech.com>
Date: Fri, 01 Jan 2010 16:52:24 -0500
From: Lee Rothstein <lee AT veritech DOT com>
Reply-To: lee AT veritech DOT com
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Symbolic links problem with cygwin 1.7.1 in 64-bit Win7 Command   	Prompt
References: <aba0e6770912300530t25e03d0fhb9d258e95571eb5 AT mail DOT gmail DOT com> 	 <4B3B8DC7 DOT 7030704 AT cygwin DOT com> <416096c61001011300r72916ae9j22d5109b6df280d5 AT mail DOT gmail DOT com>
In-Reply-To: <416096c61001011300r72916ae9j22d5109b6df280d5@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

Andy Koppe wrote:
> 2009/12/30 Larry Hall (Cygwin):
>>> I've been using gcc and other tools in older versions of cygwin with
>>> 32-bit Windows XP and Vista from windows command prompt (cmd.exe)
>>> without problems. But now I'm using 64-bit Windows 7, and some command
>>> line tools like gcc.exe do not work anymore (from cmd.exe). They do
>>> work ok from Cygwin's bash.
>
>> [...]
>>  Another [solution] might be to set "winsymlinks" in the CYGWIN
>> environment
>> variable <http://cygwin.com/cygwin-ug-net/using-cygwinenv.html> and recreate
>> the symlinks you want that way.
>
> That won't work. The option causes symlinks to be represented by
> Windows shortcuts, which do work in Explorer, but not in cmd.exe where
> they appear as .lnk files instead. (Lame, eh?)

Will Windows junctions (for the path; plus the file name) work, here, Andy?
(http://technet.microsoft.com/en-us/sysinternals/bb896768.aspx)

(Admittedly, a kludge, but this is Windows, after all. ;-))

Lee


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