how to complie 2.6.34 dom0 kernel to bzImage (Nothing to be done for `bzImage)
in [Kernel]
|
Prev: [PATCH 3/5] drivers/rtc: Remove unneeded ifdef CONFIG_PM
Next: EXPORT_SYMBOL set_irq_noprobe, set_irq_chip_and_handler, irq_to_desc ?
From: lei yang on 15 Jul 2010 09:40 On Thu, Jul 15, 2010 at 6:44 PM, Fajar A. Nugraha <fajar(a)fajar.net> wrote: > On Thu, Jul 15, 2010 at 4:34 PM, lei yang <yanglei.fage(a)gmail.com> wrote: >> All, >> >> I patched linux-2.6.34 with xen patches >> >> I find if I don't enable XEN ,use default kernel config >> :i386_defconfig, make bzImage can build well >> >> >> if I enable �XEN:eg: CONFIG_X86_XEN=y >> >> [lyang0(a)ala-lpggp1 linux-2.6.34]$ make ARCH=i386 bzImage >> scripts/kconfig/conf -s arch/x86/Kconfig >> # >> # configuration written to .config >> # >> make: Nothing to be done for `bzImage'. > > Short answer: don't run make bzImage. Simply run "make", and you'll > have vmlinuz (./arch/x86/boot/vmlinuz) which you can use. > >> Actually, I need to use bzImage, becasue I want to use gpxe to boot it which not support vmlinuz >> Note:2.6.33 works well > > Is this 2.6.33 pv_ops from Jeremy's git tree? pv_ops and Novell's xen > patches are somewhat different, so something that works on pv_ops may > or may not work on Novell's xen patches, and vise versa. > > -- Yep, I use Jeremy' s tree. > Fajar > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |