From mboxrd@z Thu Jan 1 00:00:00 1970 From: d_cary@my-deja.com To: help-gcc@gnu.org Subject: Re: Newbie - gcc apparently not building obj file Date: Wed, 05 Jan 2000 09:25:00 -0000 Message-id: <84vu46$565$1@nnrp1.deja.com> References: X-SW-Source: 2000-01/msg00053.html The first thing you need to do is ls -l to make sure that gcc is really creating the output file ``hello'', and setting the "executable" bit (there should be a "x" in the permissions column of the listing for ``hello'', but a '-' in the same column for ``hello.c''). On my machine, I used to have to type ./hello to execute a program in the current directory. My sysadmin claims it's a "security feature". Without the ``./'', my machine looks in the (supposedly "secure") locations for executables ( my ``path'' includes lots of directories that end in ``/bin/'' ). When it doesn't find it there, I get the ``command not found'' message. Don't tell him I added the "./" directory to the end of my path. By the way, folks around here use the term ``object file'' to talk about (non-executable) intermediate files sometimes generated by the compiler (if you use the -c option) and ending with the extension ``.o''. Richard De Berry , in frustration, wrote: > I enter > gcc -o hello hello.c ... >, then > hello ... > I get a command not found message. Sent via Deja.com http://www.deja.com/ Before you buy. From mboxrd@z Thu Jan 1 00:00:00 1970 From: d_cary@my-deja.com To: help-gcc@gnu.org Subject: Re: Newbie - gcc apparently not building obj file Date: Sat, 01 Apr 2000 00:00:00 -0000 Message-ID: <84vu46$565$1@nnrp1.deja.com> References: X-SW-Source: 2000-q1/msg00053.html Message-ID: <20000401000000.VE7-S2xPvG9kRPoBp-06E7_IfA5VEBCUYcTCa3Gcrhc@z> The first thing you need to do is ls -l to make sure that gcc is really creating the output file ``hello'', and setting the "executable" bit (there should be a "x" in the permissions column of the listing for ``hello'', but a '-' in the same column for ``hello.c''). On my machine, I used to have to type ./hello to execute a program in the current directory. My sysadmin claims it's a "security feature". Without the ``./'', my machine looks in the (supposedly "secure") locations for executables ( my ``path'' includes lots of directories that end in ``/bin/'' ). When it doesn't find it there, I get the ``command not found'' message. Don't tell him I added the "./" directory to the end of my path. By the way, folks around here use the term ``object file'' to talk about (non-executable) intermediate files sometimes generated by the compiler (if you use the -c option) and ending with the extension ``.o''. Richard De Berry , in frustration, wrote: > I enter > gcc -o hello hello.c ... >, then > hello ... > I get a command not found message. Sent via Deja.com http://www.deja.com/ Before you buy.