X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=x0biA3DlStbpIVFwUNjdETNpTcsxpQHFX0ze93C/h/G
	uJyp/AURAJcwulCxRufLeb+WC67jsWift32nF0rmmkxoy9w9m5voifImOMXd78sp
	gAbKHywjWtcieXmc9VVPddsE8r5h8rOlKuKf1P6OF++pSPIcWR2ZsTvniStp++LU
	=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 s=default; bh=gb4nuDWDOVIPDbPvKBUzZh5en3w=; b=qebhSOa2kQM5pAOp3
	xHT9EAIyM7XKt/0+ac1YXopnPPWOCc6xQhCxJVk9cff17e7Jn/yk5vDJiX+IgfHX
	7d6aKWTx6S/mBcuLNnfFGyepY1Xntxim3N2uD9JxsMsiK57+F3/u8QlDd6/8mnHd
	6fTWs0k3H2/NNKivHAzr/blu+o=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.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
X-Spam-SWARE-Status: No, score=-5.3 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,KHOP_RCVD_TRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE autolearn=ham version=3.3.1
X-Received: by 10.194.237.40 with SMTP id uz8mr2746728wjc.49.1365660959708;        Wed, 10 Apr 2013 23:15:59 -0700 (PDT)
Message-ID: <516655CB.9090108@gmail.com>
Date: Thu, 11 Apr 2013 07:18:51 +0100
From: Dave Korn <dave DOT korn DOT cygwin AT gmail DOT com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: FIXED: GCC can't find its header directoriescy
References: <FF69919A71D5744E85EFB23F2761448B132609 AT svrmintecexch DOT mintecsys DOT local>
In-Reply-To: <FF69919A71D5744E85EFB23F2761448B132609@svrmintecexch.mintecsys.local>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

On 11/04/2013 07:08, Duncan Roe wrote:
> Thanks Dave - removing the old cygwin dlls from C:\WINDOWS fixed gcc &
> alternatives.

  Glad to hear it!

> I put them there because I like to have the odd cygwin utility available
> to CMD.EXE. 
> 
> May put them back - but will take more care with them in future,

  The better way to do that is just to add your cygwin\bin dir to your PATH in
the Windows environment variables.  That way you get all your cygwin stuff
available in cmd.exe but it's always the up-to-date stuff from your main
installation.

  (The only problem I've ever run into in this approach is that both Cygwin
and MSVC have a "link.exe" command, so you can end up getting the wrong one.
You can avoid this by any combination of specifying full paths to the
particular one you want, choosing whether to put cygwin\bin at the start or
end of your Windows PATH, or customising your vcvars.bat to make sure the MSVC
version is earlier in the PATH when you launch it.  I've never found it to be
a big problem compared to the convenience of having a real grep available in
cmd.exe!)

    cheers,
      DaveK


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