musl-1.2.4 (9999 right now) will remove/removes the LFS compatibility hacks, like fopen64: - https://git.musl-libc.org/cgit/musl/commit/?id=246f1c811448f37a44b41cd8df8d0ef9736d95f4 - https://git.musl-libc.org/cgit/musl/commit/?id=25e6fee27f4a293728dd15b659170e7b9c7db9bc The gist is that bad configure tests (suffering from -Wimplicit-function-declaration) would build and link successfully because musl provided these symbols as aliases, despite not needing them (musl natively supports both LFS & time64). To head this off, these aliases are now gone, but remain in libc.so for binary compatibility. The fix is to just use the regular functions and not anything _LARGEFILE64_SOURCE. As a workaround, we can pass -D_LARGEFILE64_SOURCE in tricky cases *for one release cycle*. musl will drop that compatibility hack entirely in the next release *after* 1.2.4.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=5fff4978abbdd4b55fe85decb9df743786f57c6a commit 5fff4978abbdd4b55fe85decb9df743786f57c6a Author: Sam James <sam@gentoo.org> AuthorDate: 2023-05-02 17:51:06 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2023-05-02 19:11:10 +0000 sys-libs/musl: add 1.2.4 Bug: https://bugs.gentoo.org/903611 Signed-off-by: Sam James <sam@gentoo.org> sys-libs/musl/Manifest | 2 + sys-libs/musl/musl-1.2.4.ebuild | 212 ++++++++++++++++++++++++++++++++++++++++ 2 files changed, 214 insertions(+)
