mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Cc: Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: [PATCH] ci: container: downgrade LLVM to v20
Date: Wed, 22 Oct 2025 12:45:08 +0200	[thread overview]
Message-ID: <20251022104509.845994-1-a.fatoum@pengutronix.de> (raw)

It's currently not possible to build LLVM v21 in our Trixie container:

  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   clang-21 : Depends: libstdc++-15-dev but it is not installable
              Depends: libgcc-15-dev but it is not installable
              Depends: libobjc-15-dev but it is not installable
              Recommends: llvm-21-dev but it is not going to be installed
              Recommends: clang-tools-21 but it is not going to be installed
   libllvm21 : Depends: libxml2-16 (>= 2.14.1) but it is not installable
   lldb-21 : Depends: liblldb-21 but it is not going to be installed
             Depends: libxml2-16 (>= 2.14.1) but it is not installable
             Depends: python3-lldb-21 but it is not going to be installed
  E: Unable to correct problems, you have held broken packages.
  E: The following information from --solver 3.0 may provide additional context:
     Unable to satisfy dependencies. Reached two conflicting decisions:
     1. lldb-21:amd64=1:21.1.4~++20251021083224+222fc11f2b8f-1~exp1~20251021083341.56 is selected for install
     2. lldb-21:amd64 Depends libxml2-16 (>= 2.14.1)
        but none of the choices are installable:
        [no choices]

Until resolved, downgrade to LLVM v20. We currently need this only for
libfuzzer.

Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
 test/Containerfile | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/test/Containerfile b/test/Containerfile
index 2c0a20ec59da..6b4a97147c2e 100644
--- a/test/Containerfile
+++ b/test/Containerfile
@@ -62,7 +62,7 @@ RUN apt-get update && apt-get install -y --no-install-recommends \
 	&& rm -rf /var/lib/apt/lists/*
 
 ENV GCC_VERSION=15.2.0
-ENV LLVM_VERSION=21
+ENV LLVM_VERSION=20
 
 RUN apt-get update && apt-get install -y --no-install-recommends lsb-release gnupg \
 	&& wget https://apt.llvm.org/llvm.sh \
-- 
2.47.3




             reply	other threads:[~2025-10-22 10:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-22 10:45 Ahmad Fatoum [this message]
2025-10-22 10:48 ` Sascha Hauer

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=20251022104509.845994-1-a.fatoum@pengutronix.de \
    --to=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.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