From: "Daniel P. Berrangé" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Thomas Huth" <thuth@redhat.com>,
"Beraldo Leal" <bleal@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Daniel P. Berrangé" <berrange@redhat.com>
Subject: [PATCH 0/2] Fix CI build on Free BSD 13
Date: Mon, 4 Mar 2024 14:44:54 +0000 [thread overview]
Message-ID: <20240304144456.3825935-1-berrange@redhat.com> (raw)
FreeBSD seems to have prematurely purged the 13.2 images from gcloud,
despite 13.3 not being announced until tomorrow. Historically the old
images were left available for quite some time, until we noticed ports
failing due to missing symbols. Either way we need to update to 13.3
This exposed a clang bug so needs a workaround adding too.
Daniel P. Berrangé (2):
meson: detect broken clang 17 with -fzero-call-used-regs
gitlab: update FreeBSD Cirrus CI image to 13.3
.gitlab-ci.d/cirrus.yml | 2 +-
meson.build | 17 ++++++++++++-----
2 files changed, 13 insertions(+), 6 deletions(-)
--
2.43.0
next reply other threads:[~2024-03-04 14:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-04 14:44 Daniel P. Berrangé [this message]
2024-03-04 14:44 ` [PATCH 1/2] meson: detect broken clang 17 with -fzero-call-used-regs Daniel P. Berrangé
2024-03-04 14:48 ` Peter Maydell
2024-03-04 14:44 ` [PATCH 2/2] gitlab: update FreeBSD Cirrus CI image to 13.3 Daniel P. Berrangé
2024-03-04 14:49 ` Peter Maydell
2024-03-04 14:53 ` Daniel P. Berrangé
2024-03-04 17:05 ` [PATCH 0/2] Fix CI build on Free BSD 13 Richard Henderson
2024-03-04 21:16 ` Alex Bennée
2024-03-05 9:44 ` Peter Maydell
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=20240304144456.3825935-1-berrange@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=bleal@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--cc=wainersm@redhat.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 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).