| Git Clone URL: | https://aur.archlinux.org/ffmpeg-libfdk_aac.git (read-only, click to copy) |
|---|---|
| Package Base: | ffmpeg-libfdk_aac |
| Description: | Complete solution to record, convert and stream audio and video (Same as official package except with libfdk-aac support) |
| Upstream URL: | https://ffmpeg.org |
| Licenses: | custom:libfdk-aac, GPL-3.0-only |
| Conflicts: | ffmpeg |
| Provides: | ffmpeg, libavcodec.so, libavdevice.so, libavfilter.so, libavformat.so, libavutil.so, libswresample.so, libswscale.so |
| Submitter: | korrode |
| Maintainer: | zotan |
| Last Packager: | zotan |
| Votes: | 67 |
| Popularity: | 0.42 |
| First Submitted: | 2013-07-12 10:24 (UTC) |
| Last Updated: | 2025-10-13 11:45 (UTC) |
Replacing the libglslang with libshaderc in PKGBUILD worked for me. I'm not even going to pretend I know why
ffmpeg 8 adds Whisper for subtitle generation:
https://web.archive.org/web/20251002085956/https://ivo.palli.nl/2025/09/18/subtitles-using-ffmpeg/
I couldn't say for sure that this is the reason, but it's plausible. There are also some codecs that make more use of available GPUs for decoding and/or encoding.
Apologies for the delay, updated to 8.0-3, libglslang build errors should be resolved.
@salfter
Replacing the libglslang with libshaderc in PKGBUILD worked for me. I'm not even going to pretend I know why (wild guess would be transient dependencies), so ymmv.
$ git diff PKGBUILD
diff --git a/PKGBUILD b/PKGBUILD
index 7c2b826..30464b8 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -169,7 +169,7 @@ build() {
--enable-libdvdread \
--enable-libfreetype \
--enable-libfribidi \
- --enable-libglslang \
+ --enable-libshaderc \
--enable-libgsm \
--enable-libharfbuzz \
--enable-libiec61883 \
The current version is throwing this error when I try to build:
==> Starting prepare()...
Applied patch to 'libavformat/avformat.h' cleanly.
Applied patch to 'libavformat/mux_utils.c' cleanly.
==> Starting pkgver()...
==> Starting build()...
ERROR: spirv_compiler not found
If you think configure made a mistake, make sure you are using the latest
version from Git. If the latest version fails, report the problem to the
ffmpeg-user@ffmpeg.org mailing list or IRC #ffmpeg on irc.libera.chat.
Include the log file "ffbuild/config.log" produced by configure as this will help
solve the problem.
==> ERROR: A failure occurred in build().
Aborting...
==> ERROR: Build failed, check /var/lib/archbuild/extra-x86_64/salfter-1/build
This even occurs in a clean chroot.
spirv-tools is installed. Does it need spirv-tools-git instead?
Update: spirv-tools-git didn't fix the problem.
@zotan
it still doesnt work, stuck at the same place :(
i'll try to find a chance to reboot the whole system, thank you all the same :)
Update:
A system-wide rebooting does not help, and I can't recall any modification has been done since the last update of this package (except system update)
I have omitted the flag "--enable-librsvg", and the rest compiles successfully
@rAYz hm, that's really strange. what happens if you modify the PKGBUILD, replacing /usr/lib/mbedtls2/pkgconfig with /usr/lib/mbedtls2/pkgconfig:/usr/lib/pkgconfig?
@zotan
rm -rf ~/.cache/yay/ffmpeg-libfdk_aac
this removes the entire folder, which contains the src and the pkg dirs, then
$ yay -S ffmpeg-libfdk_aac
AUR Explicit (1): ffmpeg-libfdk_aac-2:8.0-2
:: (1/1) Downloaded PKGBUILD: ffmpeg-libfdk_aac
1 ffmpeg-libfdk_aac (Installed) (Build Files Exist)
==> Packages to cleanBuild?
==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4)
==> A
...
gets the same result log
@rAYz can you try rebuilding the package after clearing the srcdir & pkgdir? your logs show a non-clean build
@rAYz hmm, the PKGBUILD sets the env var to /usr/lib/mbedtls2/pkgconfig (from this extra repo commit). I wonder why that's not causing any issues for anyone else
@zotan Thanks for the quick reply No, I modified nothing. And it is a clean build, as usual
Pinned Comments
BryanLiang commented on 2025-05-26 06:16 (UTC)
If you encounter dependency break when updating the system, you can try building the package in clean chroot and using a local repository to resolve this issue.