X-Spam-Check-By:	sourceware.org
Message-ID:	<1133904002.439600829f26c@www.mailshell.com>
Date:	Tue, 06 Dec 2005 13:20:02 -0800
From:	<cyg_question AT slw DOT mailshell DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: 1.5.18-1 gcc path weirdness
In-Reply-To:	<BAY103-F174DAE04F58DB0C695AE3484400@phx.gbl>
MIME-Version:	1.0
User-Agent:	Mailshell.com
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
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

> Could it be possible that you are running the Jun 7 version of 
> gcc.exe when you are thinking that you are running the gcc 
> pointed to by the symlink? As a WAG I think you might be and 
> bash/cygwin is trying to figure out which command to ** actually ** use.

Excellent!  I just tried deleting gcc.exe and symlinking that name to
the i686-pc-cygwin-gcc.exe executable, and now it works fine.

Thank you for your help.

Steve Wootton






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