From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: buildroot@buildroot.org, Jarkko Sakkinen <jarkko@kernel.org>
Subject: Re: [Buildroot] [PATCH 1/1] package/swtpm: needs gmp
Date: Sun, 14 Dec 2025 18:06:59 +0100 [thread overview]
Message-ID: <20251214180659.666b3d0a@windsurf> (raw)
In-Reply-To: <20251208174427.3459324-1-bernd@kuhls.net>
On Mon, 8 Dec 2025 18:44:27 +0100
Bernd Kuhls <bernd@kuhls.net> wrote:
> Buildroot commit 2b449935c2e8e19a03a8962f49493a76ccca11f9 bumped swtpm
> from version 0.8.2 to 0.10.1.
>
> Upstream added gmp as dependency in version 0.9.0:
> https://github.com/stefanberger/swtpm/commit/605e0ce8800201fca2a9a37dea5e99be7bdb2233
>
> This causes build errors which are fixed by adding host-gmp as
> dependency.
>
> Fixes:
> https://autobuild.buildroot.net/results/d14/d14b2953e04b488b2f357386870d557d50190d34/
>
> Signed-off-by: Bernd Kuhls <bernd@kuhls.net>
Thanks for this *good* commit log, which has all the information
needed! If you could make sure all your commit logs fixing build issues
have the same level of information, it would be A-M-A-Z-I-N-G.
Jarkko: since you maintain this package, it would be good to report
upstream the issue that <gmp.h> is being included without a proper
check for gmp's availability in configure.ac. This should be fixed
upstream.
Thanks a lot!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2025-12-14 17:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-08 17:44 [Buildroot] [PATCH 1/1] package/swtpm: needs gmp Bernd Kuhls
2025-12-08 18:54 ` Jarkko Sakkinen via buildroot
2025-12-14 17:06 ` Thomas Petazzoni via buildroot [this message]
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=20251214180659.666b3d0a@windsurf \
--to=buildroot@buildroot.org \
--cc=bernd@kuhls.net \
--cc=jarkko@kernel.org \
--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.