Repository navigation
Conversation
Correct toolchain metadata and import-library generation, add missing dependency targets, and disable unsupported SIMD and NVIDIA paths. Preserve glibc compatibility archives and handle static libgomp symbol versions when linking shared FFmpeg libraries.
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
1 participant
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.
Building
linuxriscv64fails in several dependency recipes, and shared FFmpeg builds encounter unresolved OpenMP symbol versions from staticlibgomp.libdl/librtcompatibility archives.libgompsymbol versions when linking shared FFmpeg librariesI encountered these failures after adding RISC-V64 to releases in my abrar71/FFmpeg-Builds repository. Several dependencies failed to compile, and shared FFmpeg builds failed when linking static libgomp. This PR contributes the fixes developed and validated there.