Mail Archives: cygwin/2009/05/31/03:11:41
On Sun, May 31, 2009 at 1:49 AM, Larry Hall wrote:
> Roger Head wrote:
>>
>> Hi All,
>>
>> I'm a noob to Cygwin and all things non-Windows. I installed Cygwin on my
>> Win2k system (a couple of hiccups, but nothing major), then installed the
>> GCC. When that completed, I did g++ -v in a bash window, and got the
>> expected response. I am *sure* (99% anyway) that I was also able to do i=
t in
>> a normal CMD window amd get the identical response. I then proceeded to
>> install X-Windows with no problems, and it appears to work (i.e. can bri=
ng
>> up calc, etc). However, if I now try to invoke g++ from a CMD window I g=
et
>> the usual message '... not recognized as an internal or external command
>> ...blah blah blah'. It still works in a bash window.
>>
>> Am I dreaming that I was able to use it in a CMD window before installing
>> X Windows, or has something been changed during that installation? If so,
>> what?
>>
>> I have done all the above while logged on as Administrator. After the
>> initial Cygwin installation I had to manually add \Cygwin\bin and
>> \Cygwin\usr\bin to the PATH. That hasn't been altered. It doesn't matter
>> what directory I am in when using the CMD window, g++ isn't recognized.
>>
>> I would sure appreciate some help.
>
> If you want Windows applications to be able to see Cygwin apps without
> adding explicit paths to the invocation, you'll need to add 'C:\cygwin\bi=
n'
> or equivalent to your Windows PATH environment variable. =C2=A0You can do=
so
> using the "System" applet from the "Control Panel".
Don't have a cygwin install in front of me ATM, but - isn't g++ a
cygwin symlink these days? cmd.exe can't follow those even if they're
in the path, of course.
~Matt
--
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 -