Bugs item #2800447, was opened at 2009-06-03 11:17 Message generated for change (Comment added) made by tuxjay You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2800447&group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: James (tuxjay) Assigned to: Nobody/Anonymous (nobody) Summary: kvm fails to build against "out of tree" kernel builds+patch Initial Comment: Hi, The first problem is the ---------------------------------------------------------------------- >Comment By: James (tuxjay) Date: 2009-06-03 12:19 Message: I've prepared the patches and changelog entries, how do I get it signed off? I've been searching the website for the patch procedure and couldn't find it, sorry. Thank you ---------------------------------------------------------------------- Comment By: Jan Kiszka (kiszka) Date: 2009-06-03 11:41 Message: Please post your patches with individual changelogs and signed-off to kvm@xxxxxxxxxxxxxxxx TiA. ---------------------------------------------------------------------- Comment By: James (tuxjay) Date: 2009-06-03 11:19 Message: Hi, The first problem is that kvm fails to detect the kernel source directory correctly.. In "configure" the line kernelsourcedir=${kerneldir%/*}/source Only works if ../source is the build parent (e.g. if the source dir is /lib/modules/<version>/source) The first patch fixes that. The next is a build problem: -Iarch/${ARCH_DIR}/include should be: -I$(KERNELSOURCEDIR)/${ARCH_DIR}/include In the case of out of place builds. The second patch fixes that. Cheers, James ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2800447&group_id=180599 -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
