Ok it compiled good but the out file, which is new to me used to exe, won't even start.
Ok it compiled good but the out file, which is new to me used to exe, won't even start.
Try running it asCode:./a.out
Also, you can name the executable anything you want by using the -o option:
Code:gcc -o myprog.exe myprog.c
But it is highly uncustomary for Linux executables to have an extension.
Of course, this can be done easier:Code:gcc -o myprog myprog.c
Code:make myprog
All the buzzt!
CornedBee
"There is not now, nor has there ever been, nor will there ever be, any programming language in which it is the least bit difficult to write bad code."
- Flon's Law
You should also check out the GNU docs:
www.delorie.com/gnu/docs/glibc/libc_toc.html
GNU make glibc and gcc (which all linux systems and distros use). These are quite readable and informative. I think they also address some of your question re: how POSIX relates to "C", etc.
Good luck.
C programming resources:
GNU C Function and Macro Index -- glibc reference manual
The C Book -- nice online learner guide
Current ISO draft standard
CCAN -- new CPAN like open source library repository
3 (different) GNU debugger tutorials: #1 -- #2 -- #3
cpwiki -- our wiki on sourceforge
True enough! Just thought it might shield him from the "horrors" of LinuxOriginally Posted by CornedBee
You know, I've been developing various *nix flavors for 13 years, and I did not know that. And a Google shows that if I set the CFLAGS environment variable, I can default to use -g -Wall. Thanks
