X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-0.3 required=5.0 tests=AWL,BAYES_00,FH_DATE_PAST_20XX,SARE_MSGID_LONG40,SPF_PASS X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: <4B3B8DC7.7030704@cygwin.com> References: <4B3B8DC7 DOT 7030704 AT cygwin DOT com> Date: Fri, 1 Jan 2010 21:00:43 +0000 Message-ID: <416096c61001011300r72916ae9j22d5109b6df280d5@mail.gmail.com> Subject: Re: Symbolic links problem with cygwin 1.7.1 in 64-bit Win7 Command Prompt From: Andy Koppe To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 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. > [...] >=C2=A0Another [solution] might be to set "winsymlinks" in the CYGWIN > environment > variable and recre= ate > 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?) Andy -- 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