Complete.Org: Mailing Lists: Archives: discussion: October 1998:
Re: [aclug-L] gcc

Re: [aclug-L] gcc

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: aclug-L@xxxxxxxxxxxx
Subject: Re: [aclug-L] gcc
From: Bob Deep <bobd@xxxxxxxxxxxx>
Date: Fri, 16 Oct 1998 07:55:43 -0500
Reply-to: aclug-L@xxxxxxxxxxxx

jeffrey.hansen@xxxxxxxxxxx wrote:
> Anyone know why gcc in Redhat 5.1 would refuse to execute an executable?  I
> compiled it okay and it's in the working directory, but Linux tells me that
> the "command" isn't recognized.  I did a "file" and it is an executable.  I
> verified spelling and case until my eyes crossed.  Any ideas?

Two possibilities... 1.  The directory which holds your executable file
is not in your path, or 2. The shell you are running already tried to
run the file and thinks it remembers that it wa unable to find it (A
problem with a few shells, but I don't remember which ones)...

Either way, try to fully qualify the path and file name when you run
your command....(You can use some shorthand by using "./" for the
current directory if you like.)  So for a program named test in the
current directory type "./test" and your program should run.

You might like to make sure that the path "./" is in your path.  It
saves a lot of confusion because us x-dos folks are used to being able
to just type a command in the current directory and have it run.  I
usually put "./" first in my path for that reason.  Then I can just cd
to the proper directory and type in my command, which is usually what I

If you need help setting the path enviroment varable (usually it's
"PATH") see the man page for your specific shell..  It varies from shell
to shell how it gets done.

-=  bob =-
This is the Air Capitol Linux Users Group discussion list.  If you
want to unsubscribe, send the word "unsubscribe" to
aclug-L-request@xxxxxxxxxxxx.  If you want to post to the list, send your
message to aclug-L@xxxxxxxxxxxx.

[Prev in Thread] Current Thread [Next in Thread]