From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Olaf Hering <olaf@aepfle.de>
Cc: Anthony PERARD <anthony.perard@citrix.com>,
<xen-devel@lists.xenproject.org>,
Doug Goldstein <cardoe@cardoe.com>
Subject: Re: [XEN PATCH 2/2] automation: Check if ninja is available before building QEMU
Date: Wed, 7 Jul 2021 23:47:02 +0100 [thread overview]
Message-ID: <375823a3-8b49-7aab-ca2a-af219234b5e4@citrix.com> (raw)
In-Reply-To: <20210707223551.5462c74e.olaf@aepfle.de>
On 07/07/2021 21:35, Olaf Hering wrote:
> Am Wed, 7 Jul 2021 18:46:03 +0100
> schrieb Andrew Cooper <andrew.cooper3@citrix.com>:
>
>> Tumbleweed is generally broken and fails at ./configure due to missing
>> compression libraries.
> Something requests zlib-devel to be installed.
Yeah - it shouldn't be hard to fix.
> I suggest to provide all config.logs, not just the one from the top directory.
>
> Also a "test -f /etc/os-release && cat /etc/os-release" should be added after "$CC --version", just to know how stale the container is.
We ought to yes, although I think at the moment we probably don't want
to realise how stale all the containers are.
~Andrew
next prev parent reply other threads:[~2021-07-07 22:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-07 16:39 [XEN PATCH 0/2] automation: Fix build with new qemu-xen version Anthony PERARD
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 [this message]
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=375823a3-8b49-7aab-ca2a-af219234b5e4@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=anthony.perard@citrix.com \
--cc=cardoe@cardoe.com \
--cc=olaf@aepfle.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).