problem running progs compiled with g++

nautilus_1987 · 10-06-2002, 03:35 AM

Yes you are

To compile win10.cpp - gcc -o test win10.cpp
Then chmod 777 win10
To execute write : ./win10
I think you got it

underdog · 10-06-2002, 03:37 AM

My computer is having a problem running programs I compiled using g++. For example, I compiled a program called win10.cpp. It compiles fine, and the binary is called win10. When I type win10, the computer says:

bash: win10: command not found

I even compiled my program on another computer (via ssh). It ran fine, so I downloaded the compiled program to my computer. When I tried to run it on my computer, I got the same old error message.

Any ideas what I'm doing wrong?

acid_kewpie · 10-06-2002, 06:45 AM

you shouldn't normally need to use the chmod command. and of course in your example, you called the output file "test" so ./win10 will obviously not exist. and also gcc is primarily a c compiler, not c++, but that doesn't matter really.

nautilus_1987 · 10-06-2002, 06:56 AM

Oh I am very sorry............
Ofcourse it should be ./test
thnx acid!!!

adam_boz · 10-06-2002, 07:20 AM

do this (i don't know if this is all clear yet or not?)

g++ -o win10 win10.cpp
./win10

It should work o.k. (assuming that your code is correct ;-)

by the way... watch out with gcc 3.1.... There is a (at least one) bug in it with using the header <string.h> and the getline function from that

jetblackz · 10-06-2002, 09:23 AM

"assuming that your code is correct" and if it isn't and you got it compiled, I'd like to ask how. ;-)

Or you mean logic errors.

adam_boz · 10-06-2002, 11:52 AM

Can't you make "logic errors" and still get it to compile? It just seems to me (newbie) that the two terms mean the same thing.

what IS the difference?

adam_boz · 10-06-2002, 11:54 AM

p.s. do you all see nautilus as the first message here?

acid_kewpie · 10-06-2002, 12:00 PM

yes, it's been reported to jeremy.

a logic error is going to be something like

var = 3 * 4 * bignumber * 0;

or somethign equally stupid.

jetblackz · 10-06-2002, 01:34 PM

Thanks.

A logic error is not a problem to the computer, like acid pointed out. But it IS a problem to the end user. For example, you want to calculate the average salary, instead you put in a code that does hourly rate. You get it compiled.

In short, a logic error is an unexpected result.

Design-time errors can't get past compilers.

And there are run-time errors. Like legal code, but it produces a number bigger than your variable can hold. Boom!

underdog · 10-06-2002, 03:01 PM

OK. Chmod didn't do anything because win10 was already -rwxrwxrwx. So I
tried ./win10 and it worked!!!! I am so happy. Thanks to everyone for your
help.

underdog

Oh, by the way. Does anyone know why this works? Is it possible to change
some settings so that I don't have to type ./ every time?

adam_boz · 10-06-2002, 03:16 PM

"./" just means to stay in the current directory when looking for the executable. if you are not in the directory, and it is in, say... /home/adam/programs/ you would type"/home/adam/programs/win10" basically, a "." means current directory, and ".." means one directory up on the filesystem (hence cd ..)
If you don't want to do this, you can put the program somewhere in your $PATH. to see which directories these are, do

"echo $PATH"