public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sjames at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/110462] New: [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: Wed, 28 Jun 2023 17:11:19 +0000 [thread overview]
Message-ID: <bug-110462-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110462
Bug ID: 110462
Summary: [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'?)
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: sjames at gcc dot gnu.org
Target Milestone: ---
See PR109533. Pretty sure this was caused by r14-1569-gd87caacf8e2df5.
```
In file included from
/var/tmp/portage/sys-devel/gcc-14.0.0.9999/work/gcc-14.0.0.9999/libstdc++-v3/src/c++17/fs_ops.cc:63:
/var/tmp/portage/sys-devel/gcc-14.0.0.9999/work/gcc-14.0.0.9999/libstdc++-v3/src/c++17/../filesystem/ops-common.h:
In function 'bool std::filesystem::copy_file_copy_file_range(int, int,
std::size_t)':
/var/tmp/portage/sys-devel/gcc-14.0.0.9999/work/gcc-14.0.0.9999/libstdc++-v3/src/c++17/../filesystem/ops-common.h:377:5:
error: 'off64_t' was not declared in this scope; did you mean 'off_t'?
377 | off64_t off_in = 0, off_out = 0;
| ^~~~~~~
| off_t
/var/tmp/portage/sys-devel/gcc-14.0.0.9999/work/gcc-14.0.0.9999/libstdc++-v3/src/c++17/../filesystem/ops-common.h:381:50:
error: 'off_in' was not declared in this scope; did you mean 'fd_in'?
381 | bytes_copied = ::copy_file_range(fd_in, &off_in, fd_out,
&off_out,
| ^~~~~~
| fd_in
/var/tmp/portage/sys-devel/gcc-14.0.0.9999/work/gcc-14.0.0.9999/libstdc++-v3/src/c++17/../filesystem/ops-common.h:381:67:
error: 'off_out' was not declared in this scope; did you mean 'fd_out'?
381 | bytes_copied = ::copy_file_range(fd_in, &off_in, fd_out,
&off_out,
|
^~~~~~~
|
fd_out
make[6]: *** [Makefile:587: fs_ops.lo] Error 1
```
next reply other threads:[~2023-06-28 17:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-28 17:11 sjames at gcc dot gnu.org [this message]
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
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@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).