Workaround to make FFmpeg buildable with binutil>=2.41#29
Closed
Conversation
0ce6364 to
9acc8c4
Compare
9acc8c4 to
9051bf3
Compare
Mionsz
requested changes
Mar 3, 2025
Collaborator
Mionsz
left a comment
There was a problem hiding this comment.
We will move it to another PR and introduce as a patch - so that it is clear for any client what is happening here.
Collaborator
|
Just to make things move a little faster - I've made another PR for this so that we can close this one and no depend on time zone |
Contributor
Author
|
@Mionsz, Sorry I made one mistake in this PR: The command to cherry-pick or patch should be in FFmpeg's directory. And it also misled PR#33. I submitted PR#36 to fix. |
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.
Chrry-pick the commit to provide this workaround to make FFmpeg n6.1 buildable with binutil >= 2.41.