From: Wei Liu <wei.liu2@citrix.com>
To: Doug Goldstein <cardoe@cardoe.com>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
Wei Liu <wei.liu2@citrix.com>,
George Dunlap <George.Dunlap@eu.citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>, Tim Deegan <tim@xen.org>,
xen-devel@lists.xen.org, Jan Beulich <jbeulich@suse.com>,
Andrew Cooper <andrew.cooper3@citrix.com>
Subject: Re: [PATCH] travis: enable building of the tools
Date: Tue, 26 Apr 2016 14:11:52 +0100 [thread overview]
Message-ID: <20160426131152.GI20763@citrix.com> (raw)
In-Reply-To: <20a98382-c467-f4cb-c3bf-895061d9a2f8@cardoe.com>
On Tue, Apr 26, 2016 at 08:06:54AM -0500, Doug Goldstein wrote:
> On 4/25/16 9:46 AM, Doug Goldstein wrote:
> > For native (non-cross compiles) we now only require bcc, ld86, as86 for
> > building rombios, we can build the toolstack sans rombios and using the
> > system SeaBIOS due to known build issues. At the same time capture the
> > output of the configure scripts to help with tracking down future build
> > issues. This does not enable building of the toolstack with clang for
> > now due to multiple failures.
> >
> > Signed-off-by: Doug Goldstein <cardoe@cardoe.com>
> > ---
>
> So good to push? Just want to see this land for 4.7 because I think it
> will help catch issues for backports and I can continue to build on this
> to get more distros building.
>
I will push this in my next sweep.
Wei.
> --
> Doug Goldstein
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
prev parent reply other threads:[~2016-04-26 13:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-25 14:46 [PATCH] travis: enable building of the tools Doug Goldstein
2016-04-25 14:53 ` Wei Liu
2016-04-25 15:02 ` Doug Goldstein
2016-04-25 15:20 ` Wei Liu
2016-04-25 15:17 ` Andrew Cooper
2016-04-26 13:06 ` Doug Goldstein
2016-04-26 13:11 ` Wei Liu [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=20160426131152.GI20763@citrix.com \
--to=wei.liu2@citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=cardoe@cardoe.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=sstabellini@kernel.org \
--cc=tim@xen.org \
--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.