From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org, Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: Hemanth Kumar M D <Hemanth.KumarMD@windriver.com>
Subject: Re: [PATCH master] scripts: fix build failure with glibc 2.43
Date: Fri, 13 Mar 2026 12:12:10 +0100 [thread overview]
Message-ID: <177340033069.206252.6842304138227246713.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20260313102922.1820245-1-a.fatoum@pengutronix.de>
On Fri, 13 Mar 2026 11:29:00 +0100, Ahmad Fatoum wrote:
> glibc 2.43 introduces linux/openat2.h through the fcntl include chain
> (bits/fcntl-linux.h -> linux/openat2.h). This header expects the
> __u64 type to be defined before inclusion.
>
> In barebox scripts/include/linux/types.h the header <fcntl.h> was
> included before the __u64 typedef, causing build failures such as:
>
> [...]
Applied, thanks!
[1/1] scripts: fix build failure with glibc 2.43
https://git.pengutronix.de/cgit/barebox/commit/?id=05af23be1fb9 (link may not be stable)
Best regards,
--
Sascha Hauer <s.hauer@pengutronix.de>
prev parent reply other threads:[~2026-03-13 11:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-13 10:29 Ahmad Fatoum
2026-03-13 11:12 ` Sascha Hauer [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=177340033069.206252.6842304138227246713.b4-ty@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=Hemanth.KumarMD@windriver.com \
--cc=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