public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tg at mirbsd dot de" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/23960] [2.28 Regression]: New getdents{64} implementation breaks qemu-user
Date: Thu, 17 Sep 2020 21:42:40 +0000 [thread overview]
Message-ID: <bug-23960-131-nRhpWM2PLD@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-23960-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=23960
Thorsten Glaser <tg at mirbsd dot de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tg at mirbsd dot de
--- Comment #57 from Thorsten Glaser <tg at mirbsd dot de> ---
Jessica,
>Easiest thing would be to patch gcc/config/whatever.h to include:
>
> builtin_define ("_LARGEFILE_SOURCE=1"); \
> builtin_define ("_LARGEFILE64_SOURCE=1"); \
> builtin_define ("_FILE_OFFSET_BITS=64"); \
this will not work, unfortunately: glibc’s <fts.h> refuses to work with LFS.
But why are *new* ports supporting nōn-LFS at all anyway? Just define off_t as
long long int on *all* new architectures, similar how it’s done with 64-bit
time_t for new ILP32 arches… and similar to how the BSDs all operate as well
(off_t is a quad there, period; this with my MirBSD developer hat).
Sorry for being late to this discussion, just found this from
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916276 via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970460 and having seen this
impact Debian. (Current hat: Debian Developer)
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-09-17 21:42 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-23960-131@http.sourceware.org/bugzilla/>
2019-05-01 20:33 ` chewi at gentoo dot org
2020-09-17 21:42 ` tg at mirbsd dot de [this message]
2020-10-02 8:54 ` danny.milo at gmail dot com
2020-10-02 9:36 ` danny.milo at gmail dot com
2020-10-02 9:46 ` fweimer at redhat dot com
2020-10-02 10:41 ` danny.milo at gmail dot com
2020-10-02 11:03 ` danny.milo at gmail dot com
2020-10-02 13:17 ` jrtc27 at jrtc27 dot com
2020-10-02 14:22 ` adhemerval.zanella at linaro dot org
2020-10-02 23:06 ` tg at mirbsd dot de
2020-10-03 13:54 ` fweimer at redhat dot com
2020-10-03 13:55 ` fweimer at redhat dot com
2021-08-24 11:48 ` glaubitz at physik dot fu-berlin.de
2022-05-15 20:53 ` glaubitz at physik dot fu-berlin.de
2022-05-16 12:06 ` adhemerval.zanella at linaro dot org
2022-05-16 20:11 ` glaubitz at physik dot fu-berlin.de
2022-05-16 20:15 ` adhemerval.zanella at linaro dot org
2022-05-17 4:39 ` sam at gentoo dot org
2022-12-06 15:50 ` glaubitz at physik dot fu-berlin.de
2023-01-13 4:52 ` deller at gmx dot de
2023-12-29 23:52 ` sam at gentoo dot org
2024-01-05 8:33 ` sam at gentoo dot org
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=bug-23960-131-nRhpWM2PLD@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).