gcc is the compiler -- in the second step you compiled an executable
(which would have defaulted to a.out as you didn't specify a "-o
" option). Getting no output was a good thing -- it
means your code was linked into the executable without error. If you
now run the executable with `./a.out
Hio,
Am Freitag 28 Mai 2010 13:15:46 schrieb gottstew:
> I copied that example (saved as test_ode.c) and it compiled properly
> (using "gcc -Wall -c test_ode.c") and I got the test_ode.o file as
> expected.
The file test_ode.o is not the final executable file, but only an intermediate
result. To
Dear Sir or Madam,
I'm pretty new to C/C++ and have a question about the ode example you
provide
(http://www.gnu.org/software/gsl/manual/html_node/ODE-Example-programs.html).
I copied that example (saved as test_ode.c) and it compiled properly
(using "gcc -Wall -c test_ode.c") and I got the test_
