[bug] i2o_lan modules fails to build in 2.5.47

Anthony Murray (murrant@bvu.edu)
Wed, 13 Nov 2002 15:12:10 -0600


Hi, I am hvaing trouble building the i2o_lan module for 2.5.47. I have a 3com 905 net card and built support for it into the kernel. Here is the errors:

[...snip...]
make -f scripts/Makefile.build obj=drivers/message/i2o
gcc -Wp,-MD,drivers/message/i2o/.i2o_lan.o.d -D__KERNEL__ -Iinclude -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=pentium3 -Iarch/i386/mach-generic -nostdinc -iwithprefix include -DMODULE -include include/linux/modversions.h -DKBUILD_BASENAME=i2o_lan -c -o drivers/message/i2o/i2o_lan.o drivers/message/i2o/i2o_lan.c
drivers/message/i2o/i2o_lan.c:28:2: #error Please convert me to Documentation/DMA-mapping.txt
drivers/message/i2o/i2o_lan.c:120: parse error before "struct"
drivers/message/i2o/i2o_lan.c: In function `i2o_lan_receive_post_reply':
drivers/message/i2o/i2o_lan.c:385: `run_i2o_post_buckets_task' undeclared (first use in this function)
drivers/message/i2o/i2o_lan.c:385: (Each undeclared identifier is reported only once
drivers/message/i2o/i2o_lan.c:385: for each function it appears in.)
drivers/message/i2o/i2o_lan.c: In function `i2o_lan_register_device':
drivers/message/i2o/i2o_lan.c:1406: structure has no member named `list'
drivers/message/i2o/i2o_lan.c:1406: structure has no member named `list'
drivers/message/i2o/i2o_lan.c:1406: structure has no member named `list'
drivers/message/i2o/i2o_lan.c:1406: structure has no member named `list'
drivers/message/i2o/i2o_lan.c:1407: structure has no member named `sync'
make[3]: *** [drivers/message/i2o/i2o_lan.o] Error 1
make[2]: *** [drivers/message/i2o] Error 2
make[1]: *** [drivers/message] Error 2
make: *** [drivers] Error 2

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