From: "Yoann Congal" <yoann.congal@smile.fr>
To: "Javier Viguera" <javier.viguera@digi.com>,
<openembedded-core@lists.openembedded.org>
Cc: <richard.purdie@linuxfoundation.org>
Subject: Re: [scarthgap 00/28] Pull request (cover letter only)
Date: Tue, 17 Feb 2026 12:09:13 +0100 [thread overview]
Message-ID: <DGH6UWVR18RO.2LU166X88G2RC@smile.fr> (raw)
In-Reply-To: <b18d950d-4a43-4797-8c9d-0a7b350d04fc@digi.com>
On Tue Feb 17, 2026 at 11:18 AM CET, Javier Viguera wrote:
> Hi Yoann,
>
> On 2/13/26 19:47, Yoann Congal via lists.openembedded.org wrote:
>>
>> Richard Purdie (2):
>> pseudo: Update to 1.9.3 release
>> pseudo: Update to include an openat2 fix
>>
>
> The backport of the pseudo patches to Scarthgap broke the build on
> Ubuntu 20, as it still uses glibc 2.31, so the pseudo-native build fails
> with:
>
> | In file included from pseudo_ports.h:5,
> | from pseudo.h:164,
> | from pseudo_wrappers.c:30:
> | ports/linux/pseudo_wrappers.c: In function ‘syscall’:
> | ports/linux/portdefs.h:59:21: error: ‘__NR_openat2’ undeclared (first
> use in this function); did you mean ‘real_openat2’?
> | 59 | #define SYS_openat2 __NR_openat2
> | | ^~~~~~~~~~~~
>
> According to poky.conf, ubuntu-20 is still a supported distro to build
> Scarthgap, so I guess this needs to be somehow fixed.
Thanks for the report, I'm working on a fix.
In this case, __NR_openat2 is not present in the kernel headers.
(Ubuntu 20.04 is on Linux 5.4, the openat2 syscall was added in 5.6)
> --
> Regards,
> Javier Viguera
> Digi International Inc.
--
Yoann Congal
Smile ECS
next prev parent reply other threads:[~2026-02-17 11:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-13 18:47 [OE-core][scarthgap 00/28] Pull request (cover letter only) Yoann Congal
2026-02-16 8:48 ` Paul Barker
2026-02-17 10:18 ` [scarthgap " Javier Viguera
2026-02-17 11:09 ` Yoann Congal [this message]
2026-02-17 12:59 ` [OE-core] " Paul Barker
2026-02-17 15:55 ` Yoann Congal
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=DGH6UWVR18RO.2LU166X88G2RC@smile.fr \
--to=yoann.congal@smile.fr \
--cc=javier.viguera@digi.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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