When asking for help about particular errors, you need to quote the
**complete** line that contains the error message. My **guess** is that it
reads:
"bash: gcc: command not found"
If this **guess** is right, it means that you either don't have the C
compiler gcc on your system or it is not in your command path. The fix is
either to install it or add its location to your PATH environment variable.
If I am **guessing** wrong, then you need to tell us the complete error
message. If it comes after some other output, the preceding couple of lines
might also be informative. But in any case, you need to be telling us what
program is giving the error, and what command the error message refers to.
At 07:35 PM 12/5/99 +0000, John Marr wrote:
> I am having trouble compiling the tulip.c module. I downloaded the
>latest edition of it and ran the exact command line at the bottom of the
>file but I get a return that "command not found." I really don't
>understand why this is the case. I have compiled the older module (but
>I recieved errors that there was an open ended if ... then statement) so
>why wouldn't gcc compile this?
>
> Yes, I made sure I typed the exact command line... I even went into
>GNOME and copy/pasted the line into the terminal. I really have no idea
>what to do now.
>
> The command I used is: "gcc -DMODULE -D__KERNEL__ -Wall
>-Wstrict-prototypes -O6 -c tulip.c `[ -f
>/usr/include/linux/modversions.h ] && echo -DMODVERSIONS`"
------------------------------------"Never tell me the odds!"---
Ray Olszewski -- Han Solo
Palo Alto, CA [EMAIL PROTECTED]
----------------------------------------------------------------
