error after make all for host bus adapter driver
 

I'm trying to install QLogic host bus adapter drivers on a IBM server with RHEL V3.
I've installed the Kernel Deveploment package as required but when i execute the
#make all
i get a list of warnings, invalid suffic and an error.

Can someone tell me if a log file is recorded and where? Also am I missing something and have to install some other package?

Thank you.

Teo

If you post some of the warning/error outputs you got, someone might know what they mean...

Yeah you're right. This is from the last part


qla_fo.c:2530: called object is not a function
In file included from qla2x00.c:18979,
from qla2200.c:43:
qla_fo.c: In function `qla2x00_fo_missing_port_summary':
qla_fo.c:2663: invalid suffix on integer constant
qla_fo.c:2663: warning: null format string
qla_fo.c:2663: warning: null format string
qla_fo.c:2663: called object is not a function
qla_fo.c: In function `qla2x00_add_to_portname_list':
qla_fo.c:2875: invalid suffix on integer constant
qla_fo.c:2875: warning: null format string
qla_fo.c:2875: warning: null format string
qla_fo.c:2875: called object is not a function
qla_fo.c: In function `qla2x00_free_portname_list':
qla_fo.c:2902: invalid suffix on integer constant
qla_fo.c:2902: called object is not a function
In file included from qla2200.c:43:
qla2x00.c: In function `apidev_cleanup':
qla2x00.c:19082: `c192d491' undeclared (first use in this function)
qla2x00.c:19082: called object is not a function
make: *** [qla2200.o] Error 1

Hope this helps.

Teo

I think it's likely to be some problem at the beginning of the compile, rather than the end. Usually these kinds of massive failures are triggered by a missing header file. Might be worth posting the *beginning* of your compile errors.

Incidentally, why not use the rpms? According to the readme, this is "the easiest way to install and build" and supports RHEL3.0.

Good luck,
Jeff

Could you tell it this report is logged to some file and where is this located?

The listing that I posted was a copy from the screen.

Thank you.

Teo

It's unlikely to be logged to a file, but you can make it be that way:

make all > /tmp/logfile 2>&1

all the output will go into /tmp/logfile instead of to the screen.

btw if this problem is not a simple one you are better off talking to people who have installed this driver themselves, I'm afraid.