Merged
Conversation
Owner
|
Dankjewel Kleis! |
lovell
added a commit
that referenced
this pull request
Aug 14, 2023
bpatrik
added a commit
to bpatrik/pigallery2
that referenced
this pull request
Jul 30, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
musl 1.2.4 has removed the legacy LFS64 glibc-ABI-compat symbols, which would cause an error during
npm install sharpwhen compiled from source (either with the--build-from-sourceflag or when a globally installed libvips is detected).The fix is to replace the OS-specific
#ifdef's with a single one that checks whether_LARGEFILE64_SOURCEis defined. Other libc implementations that provide nondegenerate LFS64 interfaces are expected to define this macro as well.Reproducer