[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'?)

[cvs-commit at gcc dot gnu.org via Gcc-bugs]

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 <r...@gcc.gnu.org>:

https://gcc.gnu.org/g:ff29ee6af88f709e08ee467869d8c1b13889a724

commit r14-2191-gff29ee6af88f709e08ee467869d8c1b13889a724
Author: Jonathan Wakely <jwak...@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.