Ben Bucksch wrote:
Reason is, as said, that the build assumes that
/usr/include/linux/ioctl.h exists, i.e. it just #include linux/ioctl.h
Oh, that's not nice. Certainly for me /usr/include/linux will never point to the kernel I'm building against so that's just a
problem waiting to happen.
Avi Kivity wrote:
Ben Bucksch wrote:
configure accepts the kernel source dir as input param, or
automatically finds /lib/modules/2.6.27-rc5/build/ or similar. But the
build only uses the dir to copy the latest kvm*.h into the local dir.
The directory is not passed to gcc via -I . This
Ben Bucksch wrote:
configure accepts the kernel source dir as input param, or
automatically finds /lib/modules/2.6.27-rc5/build/ or similar. But the
build only uses the dir to copy the latest kvm*.h into the local dir.
The directory is not passed to gcc via -I . This results in a
configure accepts the kernel source dir as input param, or automatically
finds /lib/modules/2.6.27-rc5/build/ or similar. But the build only uses
the dir to copy the latest kvm*.h into the local dir. The directory is
not passed to gcc via -I . This results in a linux/ioctl.h not found
and
