Return to BSD News archive
Newsgroups: comp.unix.bsd.freebsd.misc Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.rmit.EDU.AU!goanna.cs.rmit.EDU.AU!munnari.OZ.AU!spool.mu.edu!howland.reston.ans.net!ix.netcom.com!netcom.com!dhawk From: dhawk@netcom.com (David H) Subject: Re: compiled program won't run. Message-ID: <dhawkDHvzsq.F5r@netcom.com> Organization: Decline to State References: <480g7u$t2e@news.csus.edu> Date: Sat, 11 Nov 1995 16:14:50 GMT Lines: 22 Sender: dhawk@netcom16.netcom.com In article <480g7u$t2e@news.csus.edu>, WEE-KING LEONG <wleong@sfsu.edu> wrote: > I got the freeBSD up but I have a problem in getting something >to work. I have written a simple program and it compile nicely with >gcc. But when I tried to run it, I got error saying "command not >found" Any idea what went wrong? If you're doing this as root, note that root doesn't have "." in its PATH. If you compile a program, try ./program_name to run it. Or create a user account and put "." in its PATH and use it for testing. If security is not a concern, set path = ( $path . ) as root to add the current directory to its path and if you install a binary somewhere type rehash later, david -- David Hawkins dhawk@netcom.com "Half of our mistakes in life arise from feeling where we ought to think, and thinking where we ought to feel." -- John Churton Collins