From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Alex Williamson <alex.williamson@hp.com>,
Bastian Blank <waldi@debian.org>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] Re: [Xen-staging] [xen-unstable] libxc: Remove duplicate zlib check.
Date: Sun, 27 Jan 2008 17:03:34 +0000 [thread overview]
Message-ID: <C3C269E6.12EFE%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <1201453199.23562.33.camel@bling>
On 27/1/08 16:59, "Alex Williamson" <alex.williamson@hp.com> wrote:
>> Is that correct that the ia64 libxc build needs private headers?
>
> ia64 libxc shares a number of header files with xen for domain
> building. These get linked under libxc/ia64 and are included in the
> libxc build by adding -Iia64 to the include path.
I made an alternative fix in c/s 16916 which preserves the potential
parallelism in building the actual libraries.
-- Keir
prev parent reply other threads:[~2008-01-27 17:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200801271300.m0RD0UPT031200@latara.uk.xensource.com>
2008-01-27 15:11 ` [PATCH] Re: [Xen-staging] [xen-unstable] libxc: Remove duplicate zlib check Alex Williamson
2008-01-27 16:22 ` Bastian Blank
2008-01-27 16:59 ` Alex Williamson
2008-01-27 17:03 ` Keir Fraser [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=C3C269E6.12EFE%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=alex.williamson@hp.com \
--cc=waldi@debian.org \
--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.