Merged
Conversation
Collaborator
Author
|
Before: After: |
Owner
|
Deleting the file so gcc can't find it... this is comedy gold! 🤣 |
megantaite
pushed a commit
to animoto/sharp-libvips
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.
Also, forcefully disable gold as the linker, as Rust still seems to emit a warning:
https://github.com/lovell/sharp-libvips/actions/runs/16145634431/job/45563658436#step:4:13810
(though, I think it's safe in that case, since we are building librsvg statically)
Note that we could use
export CARGO_PROFILE_RELEASE_TRIM_PATHS="all"as a possible follow-up. However, enabling it isn't very straightforward, since-Ztrim-pathscannot be added to theRUSTFLAGSenv variable, see:https://doc.rust-lang.org/cargo/reference/unstable.html#profile-trim-paths-option