From: "Fajar A. Nugraha" <fajar@fajar.net>
To: lei yang <yanglei.fage@gmail.com>
Cc: xen-devel@lists.xensource.com,
Xen Mailing List <xen-users@lists.xensource.com>
Subject: Re: how to complie 2.6.34 dom0 kernel to bzImage (Nothing to be done for `bzImage)
Date: Thu, 15 Jul 2010 17:44:36 +0700 [thread overview]
Message-ID: <AANLkTilW7OtG9SvQdXmaHhLi4ZVKTrdmTFpVIOPeVSai@mail.gmail.com> (raw)
In-Reply-To: <AANLkTikVDFL1oBg6jAyH3PmJNczOPknskjjkMSJK8Nhp@mail.gmail.com>
On Thu, Jul 15, 2010 at 4:34 PM, lei yang <yanglei.fage@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@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.
>
> 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.
--
Fajar
next prev parent reply other threads:[~2010-07-15 10:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-15 9:34 how to complie 2.6.34 dom0 kernel to bzImage (Nothing to be done for `bzImage) lei yang
2010-07-15 10:44 ` Fajar A. Nugraha [this message]
2010-07-15 13:39 ` [Xen-users] " lei yang
2010-07-15 15:11 ` Fajar A. Nugraha
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AANLkTilW7OtG9SvQdXmaHhLi4ZVKTrdmTFpVIOPeVSai@mail.gmail.com \
--to=fajar@fajar.net \
--cc=xen-devel@lists.xensource.com \
--cc=xen-users@lists.xensource.com \
--cc=yanglei.fage@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).