X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Date: Fri, 9 Apr 2010 11:56:34 +0200 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: "GCC is not found" and "compiler cannot create executables" errors Message-ID: <20100409095634.GB1960@calimero.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <4BBDE46D.5070406@etr-usa.com> <20100408170304.GA4912@ghost.local.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.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