On 05/19/2009 01:33 AM, Lori Nagel wrote:
I've been using gcc in Linux and cc in Unix.
I have not been using an IDE, only the terminal shell and a text
editing program for the C files. On both computers c programs compile
and run, however, the compilers are different and have different options,
On 05/19/2009 01:33 AM, Lori Nagel wrote:
I've been using gcc in Linux and cc in Unix.
I have not been using an IDE, only the terminal shell and a text
editing program for the C files. On both computers c programs compile
and run, however, the compilers are different and have different options,
Lori Nagel writes:
I've been using gcc in Linux and cc in Unix. I have not been using
an IDE, only the terminal shell and a text editing program for the C
files. On both computers c programs compile and run, however, the
compilers are different and have different options, and some code
gnhlug-discuss-boun...@mail.gnhlug.org wrote on 05/19/2009 08:48:44 AM:
I strongly recommend that when you compile all of your C code with gcc
that you add the arguments -Werror -Wall -Wcast-qual.
You can either do this or spend your time chasing crazy problems.
Your choice.
What
There are several ways to get GCC to supply the info in question along
with a blizzard of other stuff:
- Ask it to be generally verbose by adding the '-v' flag to the command line.
Maybe not enough info for your purposes but often useful
nevertheless.
- Ask it to mention each
On 05/19/2009 08:48 AM, Kevin D. Clark wrote:
Lori Nagel writes:
I've been using gcc in Linux and cc in Unix. I have not been using
an IDE, only the terminal shell and a text editing program for the C
files. On both computers c programs compile and run, however, the
compilers are different
I've been using gcc in Linux and cc in Unix.
I have not been using an IDE, only the terminal shell and a text
editing program for the C files. On both computers c programs compile
and run, however, the compilers are different and have different options,
and some code that compiles and runs on
