Re: 2.6.0-test11 intio.o build errors

From: Adrian Bunk
Date: Mon Dec 15 2003 - 06:40:27 EST


On Thu, Dec 11, 2003 at 08:24:40PM -0500, RunNHide wrote:
> okay - I'm not a n00b but I'm no C programmer or driver developer,
> either - figured I'd post this - understand there's not a lot of this
> hardware out there so maybe this will be helpful:
>
> CC [M] drivers/scsi/ini9100u.o
> drivers/scsi/ini9100u.c:111:2: #error Please convert me to
> Documentation/DMA-mapping.txt
> drivers/scsi/ini9100u.c:146: warning: initialization from incompatible
> pointer type
> drivers/scsi/ini9100u.c:151: warning: initialization from incompatible
> pointer type
> drivers/scsi/ini9100u.c:152: warning: initialization from incompatible
> pointer type
> drivers/scsi/ini9100u.c: In function `i91uAppendSRBToQueue':
> drivers/scsi/ini9100u.c:241: error: structure has no member named `next'
> drivers/scsi/ini9100u.c:246: error: structure has no member named `next'
> drivers/scsi/ini9100u.c: In function `i91uPopSRBFromQueue':
> drivers/scsi/ini9100u.c:268: error: structure has no member named `next'
> drivers/scsi/ini9100u.c:269: error: structure has no member named `next'
> drivers/scsi/ini9100u.c: In function `i91uBuildSCB':
> drivers/scsi/ini9100u.c:507: error: structure has no member named `address'
> drivers/scsi/ini9100u.c:516: error: structure has no member named `address'
> make[2]: *** [drivers/scsi/ini9100u.o] Error 1
> make[1]: *** [drivers/scsi] Error 2
> make: *** [drivers] Error 2

This is a known problem.

The driver is marked BROKEN in the Kconfig file, and you were only able
to choose it since you said "no" to
Select only drivers expected to compile cleanly
.

Unless someone fixes this driver it will not be available in kernel 2.6.

> Thanks,
> RunNHide

cu
Adrian

--

"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/