X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
Date:	Fri, 9 Apr 2010 11:56:34 +0200
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: "GCC is not found" and "compiler cannot create executables" errors
Message-ID:	<20100409095634.GB1960@calimero.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<k2i7758a5c31004080511r876491dfy6326bb0712dca648 AT mail DOT gmail DOT com> <4BBDE46D DOT 5070406 AT etr-usa DOT com> <v2w7758a5c31004080736ja46e3d08q602c97313e945408 AT mail DOT gmail DOT com> <m2o1ef5a52f1004080818v2cb7ef14ke2b22a5f450b7bfb AT mail DOT gmail DOT com> <h2w7758a5c31004080825m884404f6jbf0108177af1229b AT mail DOT gmail DOT com> <v2r1ef5a52f1004080849z1693fc01v3b2d924f2c04b91 AT mail DOT gmail DOT com> <20100408170304 DOT GA4912 AT ghost DOT local DOT lan> <p2j7758a5c31004090226u2f58a2a5ia6259a78cec8faf5 AT mail DOT gmail DOT com>
MIME-Version:	1.0
In-Reply-To:	<p2j7758a5c31004090226u2f58a2a5ia6259a78cec8faf5@mail.gmail.com>
User-Agent:	Mutt/1.5.20 (2009-06-14)
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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

On Apr  9 11:26, david sastre wrote:
> So now I have a question:
> What's the problem with C:\cygwin\usr\local\bin\cygmpfr-1.dll being a symlink
> instead of a file?
> Is it related to the fact that cygcheck's output uses DOS pathnames
> and/or doesn't
> understand POSIX pathnames? (note that I'm totally ignorant about
> cygcheck internals)
> 
> BTW ldd output doesn't know about symlinks either.

The problem is that the Windows DLL loader doesn't know about symlinks,
nor about Windows shortcuts.  If at all, it might understand native NTFS
symlinks starting with Windows Vista.  But as long as we don't become
super-rich and purchase Windows from Microsoft, it won't understand
Cygwin symlinks.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

--
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

- Raw text -