From: Mark Wielaard <mark@klomp.org>
To: buildbot@sourceware.org
Cc: nickc@redhat.com, Mark Wielaard <mark@klomp.org>
Subject: [COMMITTED] Add clang clang-devel llvm-devel to Containerfile-fedora-{latest,rawhide}
Date: Mon, 4 Mar 2024 23:47:40 +0100 [thread overview]
Message-ID: <20240304224740.2979024-1-mark@klomp.org> (raw)
Those packages are now needed to build annobin.
---
builder/containers/Containerfile-fedora-latest | 1 +
builder/containers/Containerfile-fedora-rawhide | 3 ++-
2 files changed, 3 insertions(+), 1 deletion(-)
diff --git a/builder/containers/Containerfile-fedora-latest b/builder/containers/Containerfile-fedora-latest
index f27fb5111bd6..1d52682394a7 100644
--- a/builder/containers/Containerfile-fedora-latest
+++ b/builder/containers/Containerfile-fedora-latest
@@ -3,6 +3,7 @@ FROM registry.fedoraproject.org/fedora:latest
RUN dnf upgrade -y && \
dnf install -y \
gcc gcc-c++ libubsan libasan libtool ccache valgrind \
+ clang clang-devel llvm-devel \
glibc-gconv-extra \
isl-devel libmpc-devel mpfr-devel gmp-devel autogen \
patch util-linux diffutils iproute bsdtar cpio procps \
diff --git a/builder/containers/Containerfile-fedora-rawhide b/builder/containers/Containerfile-fedora-rawhide
index 7e8f8f03ff16..c37ae55293b3 100644
--- a/builder/containers/Containerfile-fedora-rawhide
+++ b/builder/containers/Containerfile-fedora-rawhide
@@ -2,7 +2,8 @@
FROM registry.fedoraproject.org/fedora:rawhide
RUN dnf upgrade -y && \
dnf install -y \
- gcc gcc-c++ libubsan libasan libtool ccache valgrind clang \
+ gcc gcc-c++ libubsan libasan libtool ccache valgrind \
+ clang clang-devel llvm-devel \
glibc-gconv-extra \
isl-devel libmpc-devel mpfr-devel gmp-devel autogen \
patch util-linux diffutils iproute bsdtar cpio procps \
--
2.39.3
reply other threads:[~2024-03-04 22:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20240304224740.2979024-1-mark@klomp.org \
--to=mark@klomp.org \
--cc=buildbot@sourceware.org \
--cc=nickc@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 read-only IMAP folder(s) and NNTP newsgroup(s).