public inbox for buildroot@busybox.net
 help / color / mirror / Atom feed
From: Julien Olivain 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/2] package/libtpms: fix build with host gcc >= 15.x
Date: Fri, 06 Mar 2026 13:59:35 +0100	[thread overview]
Message-ID: <8bf2fda2bd88ca7932c3140e7954a512@free.fr> (raw)
In-Reply-To: <20260306074106.124068-1-bernd@kuhls.net>

On 06/03/2026 08:41, Bernd Kuhls wrote:
> Fixes:
> https://autobuild.buildroot.net/results/7a6/7a6ea7c513e8f1dcc32d868108bfb2a907d6fe85/
> 
> The previous change to src/tpm_library.c dates back to 2024:
> https://github.com/stefanberger/libtpms/commits/master/src/tpm_library.c
> so a backport to buildroot LTS branches should be considered.
> 
> Signed-off-by: Bernd Kuhls <bernd@kuhls.net>

Series applied to master, thanks.
For info, this issue happens only on hosts with glibc-2.43, so I added
that comment in the title. See:
https://gitlab.com/buildroot.org/buildroot/-/commit/f773fd6787491af3c98ae30f5683b8d7a431b0e5

Best regards,

Julien.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  parent reply	other threads:[~2026-03-06 12:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-06  7:41 [Buildroot] [PATCH 1/2] package/libtpms: fix build with host gcc >= 15.x Bernd Kuhls
2026-03-06  7:41 ` [Buildroot] [PATCH 2/2] package/libtpms: security bump version to 0.10.2 Bernd Kuhls
2026-03-14  7:53   ` Thomas Perale via buildroot
2026-03-06 12:59 ` Julien Olivain via buildroot [this message]
2026-03-14  7:53 ` [Buildroot] [PATCH 1/2] package/libtpms: fix build with host gcc >= 15.x Thomas Perale via buildroot

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=8bf2fda2bd88ca7932c3140e7954a512@free.fr \
    --to=buildroot@buildroot.org \
    --cc=bernd@kuhls.net \
    --cc=jarkko@kernel.org \
    --cc=ju.o@free.fr \
    /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