On Sun, May 30, 2010 at 2:18 PM, physicist25 <alemsahle2...@gmail.com> wrote: > > > I just realized what you ment. Okay, this is how I tried to run a cpp file. > > -sh-3.2# ls c:/cygwin/home > -sh: ls: command not found > -sh-3.2# ls/ c:/cygwin/home > cygwin warning: > MS-DOS style path detected: c:/cygwin/home > Preferred POSIX equivalent is: /home > CYGWIN environment variable option "nodosfilewarning" turns off this > warning. > Consult the user's guide for more details about POSIX paths: > http://cygwin.com/cygwin-ug-net/using.html#using-pathnames > hello.cpp > -sh-3.2# ls/ /home > hello.cpp > -sh-3.2# g++ hello.cpp -o hello > -sh: g++: command not found > -sh-3.2# g++/ hello.cpp -o hello > : hello.cpp: No such file or directory > : no input files > -sh-3.2# ./hello > -sh: ./hello: No such file or directory > -sh-3.2# > > I have no idea what is going on!!!
Hello! Friend what version (so to speak) of Cygwin are you running? How did you install it? For myself, and I suspect that it may not be appropriate for all, I typically run the actual setup program from the website and follow its urging to download itself to a folder, and then install it. Wait for that to happen and finally check to see if the simple program ls for list files works, and then repeat setup, but do so off-line working from the folder. Then repeat to see if the build utilities like Gcc and friends have arrived. That prompt resembles something from the Beta series of Cygwin or perhaps from one of the terminals that doesn't recognize how BASH constructs a (normal) prompt. ----- Gregg C Levine gregg.drw...@gmail.com "This signature fought the Time Wars, time and again." -- 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