From: Andrej Shadura <andrew.shadura@collabora.co.uk>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] pseudo FTBFS with recent glibc
Date: Mon, 3 Jan 2022 20:04:25 +0100 [thread overview]
Message-ID: <4e46a5df-1abd-2a3c-d8b7-ec98f08be08c@collabora.co.uk> (raw)
In-Reply-To: <e77792acdad02f36f436ccd7fe979c5c56f37361.camel@linuxfoundation.org>
Hi,
On 03/01/2022 14:47, Richard Purdie wrote:
> On Fri, 2021-12-31 at 21:40 +0100, Andrew Shadura wrote:
>> pseudo started failing to build from the source apparently after a glibc
>> update [1] we had in Debian:
>>
>>>> In file included from pseudo_wrappers.c:46:
>>>> ports/unix/guts/symlinkat.c: In function ‘wrap_symlinkat’:
>>>> pseudo_client.h:14:65: error: ‘_STAT_VER’ undeclared (first use in this function)
>>>> 14 | #define base_fstatat(dirfd, path, buf, flags) real___fxstatat64(_STAT_VER, dirfd, path, buf, flags)
>>>> | ^~~~~~~~~
>>>> ports/unix/guts/symlinkat.c:37:14: note: in expansion of macro ‘base_fstatat’
>>>> 37 | rc = base_fstatat(dirfd, newpath, &buf, AT_SYMLINK_NOFOLLOW);
>>>> | ^~~~~~~~~~~~
>>
>> A similar issue has been reported against fakeroot [2]. I guess,
>> something similar is required for pseudo as well.
>>
>> [0]: https://bugs.debian.org/1002136
>> [1]: https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=8ed005daf0
>> [2]: https://salsa.debian.org/clint/fakeroot/-/merge_requests/10/diffs
>>
>
> That looks to be a fairly old version of pseudo. This was fixed here:
>
> https://git.yoctoproject.org/pseudo/commit/?h=oe-core&id=f332f5633b5dd73fa2b6e5d605eb33e4a446d7ad
I see. I didn’t realise the development moved to a different branch. How
about deleting the master branch and making oe-core the default one if
master is no longer in use? I think many more people may be missing out
on updates if they only fetch the master branch.
--
Cheers,
Andrej
next prev parent reply other threads:[~2022-01-03 19:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-31 20:40 pseudo FTBFS with recent glibc Andrej Shadura
2022-01-03 13:47 ` [OE-core] " Richard Purdie
2022-01-03 19:04 ` Andrej Shadura [this message]
2022-01-03 19:09 ` Andrej Shadura
2022-01-03 22:08 ` Richard Purdie
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=4e46a5df-1abd-2a3c-d8b7-ec98f08be08c@collabora.co.uk \
--to=andrew.shadura@collabora.co.uk \
--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 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.