From: "Thomas Bonnefille" <thomas.bonnefille@bootlin.com>
To: "Sascha Hauer" <s.hauer@pengutronix.de>,
<barebox@lists.infradead.org>,
"Ahmad Fatoum" <a.fatoum@pengutronix.de>
Cc: "Thomas Bonnefille" <thomas.bonnefille@bootlin.com>,
"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
"Miquèl Raynal" <miquel.raynal@bootlin.com>
Subject: Re: [PATCH] fixup! sandbox: enable keytoc in hosttools_defconfig
Date: Thu, 06 Aug 2026 16:52:10 +0200 [thread overview]
Message-ID: <DKHY283ZF4K3.2VAB9S9SYRY0I@bootlin.com> (raw)
In-Reply-To: <178602149493.2137018.3077110729485180750.b4-ty@pengutronix.de>
[-- Attachment #1: Type: text/plain, Size: 733 bytes --]
Hello, thank you very much for this fix !
On Thu Aug 6, 2026 at 3:04 PM CEST, Sascha Hauer wrote:
>
> On Wed, 05 Aug 2026 16:20:02 +0200, Ahmad Fatoum wrote:
>> ci: musl-tools: disable KEYTOC as it depends on OpenSSL
>>
>> The OpenSSL we ship in the CI container is built against glibc and so
>> compiling keytoc against musl in it is currently not possible.
>>
>> Fix the CI breakage by disable KEYTOC, but only for the Github workflow.
I’ve successfully compiled OpenSSL against musl in a modified version of
the barebox-ci container and can now compile keytoc in it. This approach
would help detect build errors for keytoc + musl earlier.
Would this be acceptable for Barebox?
> [...]
Best regards,
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-08-06 14:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-05 14:20 [PATCH] fixup! sandbox: enable keytoc in hosttools_defconfig Ahmad Fatoum
2026-08-06 13:04 ` Sascha Hauer
2026-08-06 14:52 ` Thomas Bonnefille [this message]
2026-08-06 15:38 ` Ahmad Fatoum
2026-08-06 14:54 ` Thomas Bonnefille
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=DKHY283ZF4K3.2VAB9S9SYRY0I@bootlin.com \
--to=thomas.bonnefille@bootlin.com \
--cc=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=s.hauer@pengutronix.de \
--cc=thomas.petazzoni@bootlin.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 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.