public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Randy MacLeod <randy.macleod@windriver.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>,
	Hemanth.KumarMD@windriver.com
Cc: openembedded-core@lists.openembedded.org, Sundeep.Kokkonda@windriver.com
Subject: Re: [OE-core] [PATCH v3 5/6] barebox-tools: fix build failure with glibc 2.43
Date: Thu, 12 Mar 2026 15:07:50 -0400	[thread overview]
Message-ID: <0d193cac-0f0e-4eb3-a462-ba5c459bce73@windriver.com> (raw)
In-Reply-To: <CANNYZj_JtZZ7Ftskf+W46LuradpnFv1CvyYt2G_HPJovyCq09Q@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1387 bytes --]

On 2026-03-10 2:06 p.m., Alexander Kanavin wrote:
> On Tue, 10 Mar 2026 at 18:45, Hemanth Kumar M D via
> lists.openembedded.org
> <Hemanth.KumarMD=windriver.com@lists.openembedded.org> wrote:
>> +barebox-tools: fix build failure with glibc 2.43
>> +
>> +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:
>> +
>> +  linux/openat2.h:20:9: error: unknown type name '__u64'
>> +
>> +Move the inclusion of <fcntl.h> after the typedef definitions so that
>> +__u64 and related types are defined before linux/openat2.h is parsed.
>> +
>> +Upstream-Status: Pending
> This should be submitted upstream, we should try to avoid adding
> Pending patches without a clear reason given.
>
> Alex

Hemanth meant to reply saying:

Hi Alex,

Sure, I'll do that but since we're in a hurry to get the glibc-2.43 merged,
I'll keep the existing status and follow-up with a status change next week,
once I've had time to submit a patch to upstream barebox:
https://github.com/barebox/barebox?tab=readme-ov-file#contributing

Right Hemanth ?   :-)

-- 
# Randy MacLeod
# Wind River Linux

[-- Attachment #2: Type: text/html, Size: 2240 bytes --]

  reply	other threads:[~2026-03-12 19:08 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-10 17:43 [PATCH v3 1/6] glibc: Upgrade to 2.43 release Hemanth.KumarMD
2026-03-10 17:43 ` [PATCH v3 2/6] gettext: upgrade 0.26 -> 1.0 Hemanth.KumarMD
2026-03-10 17:44 ` [PATCH v3 3/6] gcc-runtime: avoid discarded-qualifiers build failure with glibc 2.43 Hemanth.KumarMD
2026-03-10 17:44 ` [PATCH v3 4/6] libxcrypt: " Hemanth.KumarMD
2026-03-10 17:44 ` [PATCH v3 5/6] barebox-tools: fix " Hemanth.KumarMD
2026-03-10 18:06   ` [OE-core] " Alexander Kanavin
2026-03-12 19:07     ` Randy MacLeod [this message]
2026-03-12 19:17       ` Alexander Kanavin
2026-03-13 17:15         ` Ahmad Fatoum
2026-03-17 10:14           ` Hemanth Kumar M D
2026-03-17 12:14             ` Alexander Kanavin
2026-03-10 17:44 ` [PATCH v3 6/6] ltp: workaround openat2 " Hemanth.KumarMD
2026-03-10 18:05   ` [OE-core] " Alexander Kanavin
2026-03-11 13:43 ` [OE-core] [PATCH v3 1/6] glibc: Upgrade to 2.43 release Mathieu Dubois-Briand
2026-03-11 17:43   ` Mathieu Dubois-Briand

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=0d193cac-0f0e-4eb3-a462-ba5c459bce73@windriver.com \
    --to=randy.macleod@windriver.com \
    --cc=Hemanth.KumarMD@windriver.com \
    --cc=Sundeep.Kokkonda@windriver.com \
    --cc=alex.kanavin@gmail.com \
    --cc=openembedded-core@lists.openembedded.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