From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Simon Martin <furryfuttock@gmail.com>, xen-devel@lists.xen.org
Subject: Re: stubdom/libxc-x86_64 compile error with valgrind installed
Date: Mon, 21 Jul 2014 11:40:55 +0100 [thread overview]
Message-ID: <53CCEE37.80903@citrix.com> (raw)
In-Reply-To: <1405938788.24518.3.camel@kazak.uk.xensource.com>
On 21/07/14 11:33, Ian Campbell wrote:
> On Mon, 2014-07-21 at 11:19 +0100, Andrew Cooper wrote:
>> I am not sure what is the correct solution here is. Introducing an
>> explicit --{en,dis}able-valgrind to the main ./configure will still
>> break for anyone who chooses to enable it.
> I proposed a bodge which I think would be acceptable (assuming it works)
I saw. It most certainly is a bodge, but is probably the best short
term course of action.
Doesn't it need an extra check for the rump stuff?
>
>> I suspect a fix involves
>> someone draining the swamp which is the stubdom build system.
> I'm hopeful that the rump kernel work will at least reduce it to a
> manageable mire...
>
> Ian.
>
Lets hope!
~Andrew
next prev parent reply other threads:[~2014-07-21 10:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-21 10:00 stubdom/libxc-x86_64 compile error with valgrind installed Simon Martin
2014-07-21 10:06 ` Ian Campbell
2014-07-21 11:17 ` Simon Martin
2014-07-21 10:19 ` Andrew Cooper
2014-07-21 10:33 ` Ian Campbell
2014-07-21 10:40 ` Andrew Cooper [this message]
2014-07-21 10:47 ` Ian Campbell
2014-07-21 10:56 ` Andrew Cooper
2014-07-21 11:06 ` Ian Campbell
2014-07-21 11:10 ` Ian Campbell
2014-07-21 11:14 ` Ian Jackson
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=53CCEE37.80903@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=furryfuttock@gmail.com \
--cc=xen-devel@lists.xen.org \
/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.