From: Anthony PERARD <anthony.perard@citrix.com>
To: <xen-devel@lists.xenproject.org>
Cc: Anthony PERARD <anthony.perard@citrix.com>,
Doug Goldstein <cardoe@cardoe.com>
Subject: [XEN PATCH 0/2] automation: Fix build with new qemu-xen version
Date: Wed, 7 Jul 2021 17:39:59 +0100 [thread overview]
Message-ID: <20210707164001.894805-1-anthony.perard@citrix.com> (raw)
Patch series available in this git branch:
https://xenbits.xen.org/git-http/people/aperard/xen-unstable.git br.automation-add-ninja-v1
Adding ninja-build pkg when possible.
I'll push new containers soon.
Anthony PERARD (2):
automation: Adding ninja-build to some docker images
automation: Check if ninja is available before building QEMU
automation/build/alpine/3.12.dockerfile | 1 +
automation/build/fedora/29.dockerfile | 9 ++++++---
automation/build/suse/opensuse-leap.dockerfile | 2 ++
automation/build/ubuntu/bionic.dockerfile | 2 ++
automation/build/ubuntu/focal.dockerfile | 2 ++
automation/scripts/build | 4 +++-
6 files changed, 16 insertions(+), 4 deletions(-)
--
Anthony PERARD
next reply other threads:[~2021-07-07 16:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-07 16:39 Anthony PERARD [this message]
2021-07-07 16:40 ` [XEN PATCH 1/2] automation: Adding ninja-build to some docker images Anthony PERARD
2021-07-07 16:40 ` [XEN PATCH 2/2] automation: Check if ninja is available before building QEMU Anthony PERARD
2021-07-07 17:46 ` Andrew Cooper
2021-07-07 19:52 ` Olaf Hering
2021-07-07 22:44 ` Andrew Cooper
2021-07-08 0:29 ` Olaf Hering
2021-07-07 20:35 ` Olaf Hering
2021-07-07 22:47 ` Andrew Cooper
2021-07-08 0:32 ` Olaf Hering
2021-07-08 12:23 ` Olaf Hering
2021-07-08 12:51 ` Andrew Cooper
2021-07-08 14:20 ` Olaf Hering
2021-07-08 10:52 ` Anthony PERARD
2021-07-08 11:23 ` Andrew Cooper
2021-07-08 11:30 ` Anthony PERARD
2021-07-07 17:23 ` [XEN PATCH 0/2] automation: Fix build with new qemu-xen version Anthony PERARD
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=20210707164001.894805-1-anthony.perard@citrix.com \
--to=anthony.perard@citrix.com \
--cc=cardoe@cardoe.com \
--cc=xen-devel@lists.xenproject.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.