public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/110462] [14 regression] Build failure with musl-1.2.4 (filesystem/ops-common.h:377:5: error: 'off64_t' was not declared in this scope; did you mean 'off_t'?)
Date: Thu, 29 Jun 2023 15:19:15 +0000 [thread overview]
Message-ID: <bug-110462-4-Ql5ELh8Aez@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110462-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110462
--- Comment #11 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jonathan Wakely <redi@gcc.gnu.org>:
https://gcc.gnu.org/g:ff29ee6af88f709e08ee467869d8c1b13889a724
commit r14-2191-gff29ee6af88f709e08ee467869d8c1b13889a724
Author: Jonathan Wakely <jwakely@redhat.com>
Date: Wed Jun 28 19:10:29 2023 +0100
libstdc++: Do not use off64_t in calls to copy_file_range [PR110462]
Although the copy_file_range(2) man page shows the arguments as off64_t*
that is not portable. For musl there is no off64_t type, as off_t is
always 64-bit. Use the loff_t type which is always 64-bit even if off_t
isn't. We could just use off_t because the filesystem library is
compiled with _FILE_OFFSET_BITS=64, but loff_t is the more correct type
for this interface.
libstdc++-v3/ChangeLog:
PR libstdc++/110462
* acinclude.m4 (GLIBCXX_CHECK_FILESYSTEM_DEPS): Check that
copy_file_range can be called with loff_t* arguments.
* configure: Regenerate.
* src/filesystem/ops-common.h (copy_file_copy_file_range):
Use loff_t for offsets.
next prev parent reply other threads:[~2023-06-29 15:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-28 17:11 [Bug libstdc++/110462] New: " sjames at gcc dot gnu.org
2023-06-28 17:12 ` [Bug libstdc++/110462] " sjames at gcc dot gnu.org
2023-06-28 17:13 ` redi at gcc dot gnu.org
2023-06-28 17:14 ` sjames at gcc dot gnu.org
2023-06-28 17:15 ` sjames at gcc dot gnu.org
2023-06-28 17:15 ` redi at gcc dot gnu.org
2023-06-28 17:16 ` redi at gcc dot gnu.org
2023-06-28 17:18 ` sjames at gcc dot gnu.org
2023-06-28 17:23 ` redi at gcc dot gnu.org
2023-06-28 18:03 ` redi at gcc dot gnu.org
2023-06-28 18:44 ` sjames at gcc dot gnu.org
2023-06-29 15:19 ` cvs-commit at gcc dot gnu.org [this message]
2023-06-29 15:22 ` redi at gcc dot gnu.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-110462-4-Ql5ELh8Aez@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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).