From: David F Barrera <dfbp@us.ibm.com>
To: Khoa Huynh <khoa@us.ibm.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Compile error with set of NMI patches
Date: Thu, 12 Jan 2006 09:24:25 -0600 [thread overview]
Message-ID: <43C674A9.9060403@us.ibm.com> (raw)
In-Reply-To: <OF55A13A23.6D6A13A9-ON852570F3.0079A5A5-862570F3.007A1E72@us.ibm.com>
I am getting the same error on my x86_64 builds. (changeset 8567)
Khoa Huynh wrote:
>Many of us are getting compilation errors when we compile
>xen-unstable.hg tree with the latest set of patches
>for enabling Xen to pass NMI's to NMI callback in dom0:
>
>arch/xen/x86_64/kernel/built-in.o(.text+0x285d): In function
> `do_nmi_callback':
>: undefined reference to `do_nmi'
>make[4]: *** [.tmp_vmlinux1] Error 1
>make[4]: Leaving directory `/root/xen-unstable.hg/linux-2.6.12-xenU'
>make[3]: *** [build] Error 2
>make[3]: Leaving directory `/root/xen-unstable.hg'
>make[2]: *** [linux-2.6-xenU-install] Error 2
>make[2]: Leaving directory `/root/xen-unstable.hg'
>make[1]: *** [install-kernels] Error 1
>make[1]: Leaving directory `/root/xen-unstable.hg'
>make: *** [world] Error 2
>
>Hope Ian Campbell can fix it (looks like a simple fix). If it has already
> been fixed,
>please ignore this note. This is just FYI. Thanks.
>
>Regards,
>Khoa
>
>
>_______________________________________________
>Xen-devel mailing list
>Xen-devel@lists.xensource.com
>http://lists.xensource.com/xen-devel
>
>
>
--
Regards,
David F Barrera
Linux Technology Center
Systems and Technology Group, IBM
"The wisest men follow their own direction. "
Euripides
next prev parent reply other threads:[~2006-01-12 15:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-11 22:14 Compile error with set of NMI patches Khoa Huynh
2006-01-12 15:24 ` David F Barrera [this message]
2006-01-12 15:39 ` Ian Campbell
2006-01-12 15:53 ` David F Barrera
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=43C674A9.9060403@us.ibm.com \
--to=dfbp@us.ibm.com \
--cc=khoa@us.ibm.com \
--cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.