From: Bill Burns <bburns@redhat.com>
To: xen-devel@lists.xensource.com
Subject: Problem building 3.1.1 HV for ia64
Date: Tue, 16 Oct 2007 08:43:58 -0400 [thread overview]
Message-ID: <4714B20E.6060906@redhat.com> (raw)
I have run into an issue with the Xen 3.1.1 HV where it fails
to build for ia64. I have worked up a patch that fixes the issue, but
I wonder if maybe I am doing something wrong. It seems hard to believe that
they 3.1.1 won't build ia64.
Anyway here is the issue. Building for common/domctl.c get an undefined
reference error on guest_physmap_max_mem_pages. It is declared in arch
dependent shadow.h files. Not sure why only the ia64 does not get the
definition. But the following changeset removed the include of asm/shadow.h
from common/domctl.c:
changeset: 15456:74b05c391535
user: Keir Fraser <keir@xensource.com>
date: Wed Oct 03 14:37:38 2007 +0100
summary: [XEN] replace shadow_* with paging_* in common code
Restoring the include fixes the build for ia64. Do others see this issue?
Thanks,
Bill
next reply other threads:[~2007-10-16 12:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-16 12:43 Bill Burns [this message]
2007-10-16 13:34 ` Problem building 3.1.1 HV for ia64 Alex Williamson
2007-10-16 17:16 ` Alex Williamson
2007-10-17 6:58 ` Keir Fraser
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=4714B20E.6060906@redhat.com \
--to=bburns@redhat.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.