I'm wondering what the general wisdom is here to deal with the fact that given a kernel-ib-devel installation, /usr/src/ofa_kernel/include/linux has an autoconf.h in it with just the OFED kernel definitions in it.
Given that when I build my kernel module I do:
. /usr/src/ofa_kernel/config.mk
gcc ... $BACKPORT_INCLUDES -I/usr/src/ofa_kernel/include -I<kernel
includes> ...
and my kernel module does a:
#include <linux/autoconf.h>
my module obviously ends up getting the very abbreviated OFED autoconf.h
rather than the kernel's own, much bigger and more complete version.
Should I be jiggering my gcc options to somehow include the kernel one
(i.e. -include $kernel_path/include/linux/autoconf.h)? I dislike that
solution somewhat as it includes hte autoconf.h in source files that
don't specifically need it. Or is there some other solution?
Should, perhaps, the autoconf.h that's
in /usr/src/ofa_kernel/include/linux perhaps employ an "#include_next
<linux/autoconf>" to get the kernel's own version of that file merged
with the OFED one?
Thanx,
b.
signature.asc
Description: This is a digitally signed message part
_______________________________________________ ewg mailing list [email protected] http://lists.openfabrics.org/cgi-bin/mailman/listinfo/ewg
