This is the mail archive of the
mailing list for the Cygwin project.
Re: FIXED: GCC can't find its header directoriescy
- From: "Larry Hall (Cygwin Developers)" <lhall at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Thu, 11 Apr 2013 22:27:04 -0400
- Subject: Re: FIXED: GCC can't find its header directoriescy
- References: <FF69919A71D5744E85EFB23F2761448B132609 at svrmintecexch dot mintecsys dot local> <CAEhDDbBquP=3XU9N3GTyz+OAh+KSaxLkL975kqsd3XQvn5X7zg at mail dot gmail dot com> <FF69919A71D5744E85EFB23F2761448B132628 at svrmintecexch dot mintecsys dot local>
- Reply-to: cygwin-developers at cygwin dot com
On 4/11/2013 8:05 PM, Duncan Roe wrote:
On Thu, Apr 11, 2013 at 8:08 AM, Duncan Roe wrote:
Thanks Dave - removing the old cygwin dlls from C:\WINDOWS fixed gcc
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,
Adding c:\cygwn\bin to the Windows PATH might be a better solution;
that's what I did.
OK I'm convinced. But ... how do I do it? Registry? autoexec.bat? other?
If you always want Cygwin to be available, just set it in your environment
with the rest of your settings. Run "systemPropertiesAdvanced.exe", click
the "Environment Variables..." button, and either append to the PATH
variable in "System variables" (if you want everyone to see Cygwin) or
add PATH to your user environment variables.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple