On Sep 16, 2008, at 12:01 PM, Zhang, Xiantao wrote:
Alexander Graf wrote:
KVM as is assumes that the kernel obj dir and the kernel source dir
are at the same location. This is true for most self-built vanilla
kernels, but some distributions split these up (e.g. SUSE).
To keep compatible and have users have a good experience on building
KVM on any distribution, this patch attempts to rebuild the logic
from the kernel Makefile as closely as possible. With it I
successfully built KVM on a current SUSE system.
Signed-off-by: Alexander Graf <[EMAIL PROTECTED]>
Please check and see if it breaks the build process for anyone else.
Building with IA64 on SUSE-kernels is still broken due to similar but
separate problems.
Hi, Graf
I am confused by this patch. Why not use ./configure --kerneldir=
your_kernel_source_directory ? It should be also workable for you.
In the Makefile, KERNELDIR means the kernel source directory of
target
machine, and is set to /lib/modules/$(uname -r)/build of build machine
by default. But you can change it at your will through configure or
modifying config.mak.
On SUSE kernels, there are two directories that are completely
separate. One is linked to from /lib/modules/$(uname -r)/build (that's
the object dir), while the other one is linked to from /lib/modules/$
(uname -r)/source (that's the source dir).
The build dir contains files that were built during a kernel build.
The source dir is the one the kernel was built from. Almost all of the
code in KVM assumes, that these are at one location. This is true for
self-built kernels, as they generate the obj files in your source dir.
It is not true for SUSE kernels you install from RPMs though.
Alex
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
