Talkback for article: 229, March2002

GCC - the root of all

Back to:

From: Sworder <jhe(at)> [ date: 2002-03-15 ]
A good guide for every persion who want to have the basic knowlodge of gcc.
From: tom2jerry <mouse_pc(at)> [ date: 2002-03-17 ]
merci ,,,
From: ron [ date: 2002-04-25 ]
Unless the executable file is in a subdirectory which is in PATH you will need to use "./game" not just "game" to run the program. "./" specifies the current subdirectory. I remember that it took me several days to find this out when I first started using Linux. In MSDOS, the logged disk drive and the current subdirectory are searched as well as those subdirectories on the PATH. Not so on Unix systems.

Otherwise, looks very good and thank you.
From: Gerald [ date: 2002-04-25 ]
A good article on gcc.
From: Thomas <Thomas.Huld(at)> [ date: 2002-04-25 ]
Actually, if you ARE paranoid you would realize that you would be almost as vulnerable to the trojan horse described by Ken Thompson when using an open-source compiler as using a closed-source one. He described a trojan horse that you had to have in the source code only the first time you compiled the C compiler. Then you could remove it from the source code, and if you compiled the compiler again with itself it would not show up in the source code but it would still be in the executable.

If you really want to avoid this you should use the compiler you had at the start to compile a different compiler and then compile the first compiler using the second.

It is a bit theoretical however (I hope).
From: TomM [ date: 2002-04-30 ]
Nice article.

For further reference, there is a nice <i>linux GCC howto</i> that
covers some bells and whistles to play with when doing serious compiling.

Happy reading! :-)
From: aaron <oljbear(at)> [ date: 2002-05-19 ]
a very short yet useful article on gcc, gdb.
thank you very much for putting it up.
the only thing missing is as mentioned by ron[2002-04-25] the "./" which took me quite a while to figure why it is used...
From: Sam [ date: 2002-05-24 ]
Nice article. I went through it and worked it. The code was clean -- rather amazing for an article on How To Do. I was lucky enough to have remembered after a run attempt that "./" would find the file for me. Ron and Aaron noted the same.
In general, when reading things on the Net, I am inclined to think that an old English teacher of mine had it right when he said that contractions should be avoided, e.g., "can't" looks rather like "can" when certain tight fonts are used. Cannot is much easier to notice, thus not having to backtrack on the "code" and find the error.

From: byron <byronsuen(at)> [ date: 2002-06-21 ]
simple but usefull fo new commer!
From: Jonas Hughes [ date: 2002-09-06 ]
Excellent article for beginners for gcc. I needed something brief and applicable. Thank u I got it.
From: dan <coolbody(at)> [ date: 2002-11-01 ]
thanks !!


From: nilsson <sniper(at)> [ date: 2003-04-09 ]
thanks a lot
From: Tony Bradley <tonybradley(at)> [ date: 2003-10-30 ]
VERY good howto! However, I'm wondering how to specify which directories GCC should use to place different output files...

Any help would be very much appreciated

From: liuxinbao <liuxinbao2k(at)> [ date: 2003-11-14 ]

From: iris <irissin(at)> [ date: 2004-07-03 ]
thanks,I will go through it .
From: andy <futurestar(at)> [ date: 2004-08-18 ]
very good!
thank a lot!
From: gloria [ date: 2006-05-17 ]
The guide is very useful to a person like me who is studying to compile a c program at the first time. Thank you very much.

17 talkbacks in English
Other talkbacks:   Castellano

Due to the increased amount of web spam we have deciced to removed the talkback posting possibility. You can read old talkbacks but you can no longer post new ones.

Back to

Please contact webmaster(at) if you have any questions with regards to this talkback

lftalkback version 3.10