All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrej Shadura <andrew.shadura@collabora.co.uk>
To: openembedded-core@lists.openembedded.org
Subject: pseudo FTBFS with recent glibc
Date: Fri, 31 Dec 2021 21:40:28 +0100	[thread overview]
Message-ID: <e9d8abaa-20e9-4ee6-0cfc-2705d858c432@collabora.co.uk> (raw)

Hi,

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

-- 
Cheers,
   Andrej


             reply	other threads:[~2021-12-31 20:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-31 20:40 Andrej Shadura [this message]
2022-01-03 13:47 ` [OE-core] pseudo FTBFS with recent glibc Richard Purdie
2022-01-03 19:04   ` Andrej Shadura
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=e9d8abaa-20e9-4ee6-0cfc-2705d858c432@collabora.co.uk \
    --to=andrew.shadura@collabora.co.uk \
    --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 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.