Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
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
Date:	Tue, 28 Dec 2004 13:11:27 -0500
From:	Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: gcc installation problem and solution
Message-ID:	<20041228181127.GA5767@trixie.casa.cgf.cx>
Reply-To:	cygwin AT cygwin DOT com
References:	<1849635026 AT web DOT de> <41D19E50 DOT 301 AT familiehaase DOT de>
Mime-Version:	1.0
In-Reply-To:	<41D19E50.301@familiehaase.de>
User-Agent:	Mutt/1.4.1i

On Tue, Dec 28, 2004 at 06:56:32PM +0100, Gerrit P. Haase wrote:
>There are two kinds of symlinks, Windows style (with .lnk ending)
>and pure Cygwin symlinks, binutils obviously contains Cygwin stlye
>symlinks.

setup.exe only creates pure cygwin symlinks.  I suspect that the
original report of "These are supposed to be symbolic links to the
executables in the /usr/bin directory, but - for whatever reason - the
setup program +did not install them in a way that they were used as
symlinks afterwards" translates to:

http://www.cygwin.com/faq/faq_3.html#SEC66

Which would have been made clear if the guidelines specified in
http://cygwin.com/problems.html had been followed.

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/

- Raw text -