From: Alex Williamson <alex.williamson@hp.com>
To: Gerd Hoffmann <kraxel@suse.de>
Cc: Xen devel list <xen-devel@lists.xensource.com>
Subject: Re: ia64 build broken due to oprofile?
Date: Thu, 07 Dec 2006 08:29:56 -0700 [thread overview]
Message-ID: <1165505396.5622.2.camel@lappy> (raw)
In-Reply-To: <45782B75.8000305@suse.de>
On Thu, 2006-12-07 at 15:55 +0100, Gerd Hoffmann wrote:
> Hi,
>
> I can't cross-build ia64 xen kernels any more for quite some time due to
> missing asm/xenoprof.h (which really isn't in xen/include/asm-ia64). Is
> this really broken upstream? Or did I miss something else? Somehow I
> can't imagine it stays unfixed *that* long ...
Hi Gerd,
Yes, xen-unstable.hg is broken on ia64. We've been having a rough
time keeping up with all the breakages, but we're almost there.
http://xenbits.xensource.com/ext/xen-ia64-unstable.hg is merged up to
nearly the latest xen-unstable.hg changeset, and I plan to request a
pull within the next day or so. Please use the xen-ia64-unstable.hg
tree until then. Thanks,
Alex
--
Alex Williamson HP Open Source & Linux Org.
prev parent reply other threads:[~2006-12-07 15:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-07 14:55 ia64 build broken due to oprofile? Gerd Hoffmann
2006-12-07 15:29 ` Alex Williamson [this message]
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=1165505396.5622.2.camel@lappy \
--to=alex.williamson@hp.com \
--cc=kraxel@suse.de \
--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.