X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Fri, 1 Feb 2008 08:48:32 -0500
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Help with Make
Message-ID: <20080201134832.GA25481@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <loom DOT 20080201T113521-704 AT post DOT gmane DOT org> <200802011307 DOT 48192 DOT aluaces AT udc DOT es> <loom DOT 20080201T120840-659 AT post DOT gmane DOT org> <008101c864cd$ed519840$2e08a8c0 AT CAM DOT ARTIMI DOT COM> <loom DOT 20080201T130212-365 AT post DOT gmane DOT org> <008201c864d4$2295dbf0$2e08a8c0 AT CAM DOT ARTIMI DOT COM> <loom DOT 20080201T133907-987 AT post DOT gmane DOT org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <loom.20080201T133907-987@post.gmane.org>
User-Agent: Mutt/1.5.16 (2007-06-09)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
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 Fri, Feb 01, 2008 at 01:41:48PM +0000, Richard Head wrote:
>>   What kind of "not working"?  If it's still saying "Not found", then it's got
>> to be not in the path after all; if it's some other error message now, tell us
>> which?
>
>Still saying gcc: command not found, and d:\cygwin\bin is def in the path.

There isn't any mystery to how this works.  If you really have d:\cygwin\bin
in your path and gcc is really in d:\cygwin\bin then any application, whether
cygwin-based or not, will find gcc.

In Windows your path should look something like:

d:\cygwin\bin;c:\windows\system;...
             ^                 ^
                   semicolons

We've reached the point where you need to provide the details mentioned at
http://cygwin.com/problems.html.  The cygcheck output, in particular would
probably show what the problem is but you should run the cygcheck command
from outside of a cygwin shell.

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/