-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
check failed: build of ffmpeg failed #27
Comments
Xcode 15 strikes again, it looks like Apple have decided that duplicate symbols should fail their linker, and I can't see a flag to work around it, and reverting to classic behaviour is doing the same. No real fixes, so the only what I can see to fix this ATM is remove the --enable-libsvtav1 and --enable-libbluray options from build-ffmpeg.sh I can try raising errors with the STV-AV1 team as they also work with the libaom and I've already had work with them to get rid of duplicate symbols before. The one has in libbluray and ffmpeg may be trickier as the vlc team seem to ignore administrator emails for their mailing list so don't allow new people so it may be the ffmpeg team that need to sort it and they are quite slow to respond to issues sometimes. |
Thanks. That's actually what I ended up doing. The tests fail, but oh well. Thank you for your work! |
The svt-av1 issue raised as Someone else has raised the libbluray issue, which is a good job as is seems joining the VLC gitlab is as gated as there mailing lists. The ffmpeg team threw it over the fence to libbluray. |
SVT-AV1 should be back working again (as in it works for me :-) ) |
No action from the vlc team with regard to libbluray, so I hacked itv tp compile and created a patch. |
Hi @Vargol, thanks for all your work. I receive the same (or a similar?) error, i.e.
Is there anything I can do about this right now? If this requires a separate issue, please let me know! M1 Mac Mini on Sonoma 14.4.1. |
Did you download the release ? |
@Vargol I cloned the most recent version of this repository using the Git CLI. That should give me the most recent version, right? |
Yes that should work, assuming you didn't clone a branch. Check build/build-libbluray.sh has the following line
I'm running a fresh build from a clone to check. |
@Vargol yes,
on line 46. |
and thats the version thats not working for you, as that is the latest version that has just successfully built for me.
|
Yes, the latest version has not been working for me. I double checked that I indeed had the latest version, and tried to build twice as well. Could I help by providing additional information? |
Sure, first I need your build-libbluray.log from for build directory. |
Also can you check in the build directory and try running the following command
which should return somethin like
if the 'lbr_' on the front of dec_init is missing thats more proof the patch is not applying. |
@Vargol indeed, the patch doesn't apply:
I'm certain I have the latest version of your repository; I even deleted the repo folder and cloned it again. Do you have any clue on what might be going wrong? Perhaps caching-related issues? |
Can you send me the build log build-libbluray.log It strange as there been no changes to the libbluray source for a year, there's only been one version of the patch, so its
alternatively you can try applying the patch using the patch command. To do that change the command
to
in build/build-libbluray.sh |
Older / incompatible Git version sounds plausible. I had not installed Git myself, I used the version that Apple includes in macOS. I have just installed Git (version 2.44.0) using Homebrew, and I'll try again. Will report back ASAP. EDIT (1): no luck using a different Git version. There are no spaces or unusual characters in my paths, thus I will try again after adapting build/libbluray.sh (i.e. EDIT (2): adapting build/libbluray.sh worked! All tests ran successfully. Thanks @Vargol for the extensive support. |
BTW, latest checkout (30-May-24) and it was failing the same way for me (Apple M1-Max) — I did this change, and it's built ok 👌 |
It looks like Xcode had an update two weeks ago- did it break everything again? Snippet from build-ffmpeg.log
|
Not sure, this one is looking like a ffmpeg issue, as the error says
but that flag is or was part of HEVCSPS see the ffmpeg docs. I'm guessing the flag has been changed in the git repo, but no one has changed the video toolbox interface. Just got to do some digging to verify that, like find the HEVCSPS definition in the repo |
Yep, this commit broke it. |
Issue raised on the ffmpeg tracker. |
And it appears to be fixed now. |
Thank you for your quick response! |
Everything seemed to work until the ffmpeg build. The end of my build-ffmpeg.log file:
The text was updated successfully, but these errors were encountered: