| Git Clone URL: | https://aur.archlinux.org/lib32-ffmpeg.git (read-only, click to copy) |
|---|---|
| Package Base: | lib32-ffmpeg |
| Description: | Complete solution to record, convert and stream audio and video (32 bit) |
| Upstream URL: | http://ffmpeg.org |
| Licenses: | GPL-3.0-only |
| Conflicts: | lib32-libffmpeg |
| Provides: | libavcodec.so, libavdevice.so, libavfilter.so, libavformat.so, libavutil.so, libpostproc.so, libswresample.so, libswscale.so |
| Replaces: | lib32-libffmpeg |
| Submitter: | lano1106 |
| Maintainer: | oxalin |
| Last Packager: | oxalin |
| Votes: | 37 |
| Popularity: | 0.006711 |
| First Submitted: | 2013-05-18 04:43 (UTC) |
| Last Updated: | 2024-09-27 17:48 (UTC) |
@unknown78: you should have lib32-v4l-utils (and v4l-utils) installed. It is a dependency which should be automatically detected if missing and added if needed.
Can you make sure you have usr/lib32/libv4l2.so and usr/lib/libv4l2.so installed? Also, do you have usr/lib32/pkgconfig/libv4l2.pc and usr/lib/pkgconfig/libv4l2.pc installed which should be used by pkg-config?
I get the following error. Can someone help?
ERROR: libv4l2 not found using pkg-config
GordonGR: Thank you, I'll be updating lib32-ffmpeg package in a few minutes.
Just letting you know I created the package lib32-x264 as the equivalent to the renewed extra/x264 that replaced the extra/libx264* packages.
Zaplo, could you post the error please? I'm not having any problem on my side.
Build fails in my system, due to libavcodec/x86/vp9lpf_16bpp.asm. It finished succesfully after I compiled this file manually:
yasm vp9lpf_16bpp.asm -I ../../ -mx86 -felf32 -DARCH_X86_64=0 -DARCH_X86_32=1 -DHAVE_CPUNOP=1 -DHAVE_ALIGNED_STACK=1
@ZIPS: I've asked GordonGR, maintainer of lib32-libx264, to remove the make-dependency against lib32-ffmpeg on his side. This should properly fix the circular dependency encountered recently.
Appear to have a bit of a loop going on as of the last update:
:: Package lib32-ffmpeg not found in repositories, trying AUR...
:: resolving dependencies...
tsort: -: input contains a loop:
tsort: lib32-ffmpeg
tsort: lib32-libx264
@Enverex: There is no reason why you would need to specify the target OS unless the tools are unable to identify it by themselves. From the error reported in your 2018-04-10 comment, it seems you were encountering an error with AppKit, which you now specifically disable with the proposed modification. AppKit should be needed only under macOS, so the build tools are really identifying your system as such...
Using --pkgconfigdir option is pretty much the same as using PKG_CONFIG_PATH. However, "PKG_CONFIG_PATH is a environment variable that specifies additional paths in which pkg-config will search for its .pc files." Thus, it's a small differentiation between the environmental variable and the use of the option that should have no impact on the result.
When you say that you are now unable to build this package, which versions are you comparing: 3.4.2 against 3.4.1? Nothing special changed, we are mimicking pretty much exactly what is done under the x64/native package.
Could you delete lib32-ffmpeg folder under pacaur's cache (~/.cache/pacaur/lib32-ffmpeg) then reinstall lib32-ffmpeg? This will force to start from scratch and eliminate any problem that could have been related to a corrupted cache folder.
Found the issue, you need to specify that this is being built for Linux. Something's causing it to build as MacOS now which obviously doesn't work. Adding the following to configure fixes it and also negates the need to export the PKG related variable too:
--target-os=linux --pkgconfigdir=/usr/lib32/pkgconfig --disable-appkit
Pinned Comments
oxalin commented on 2024-04-09 22:05 (UTC)
For those wondering: I intentionally keep this package as close to the native package as possible, to the extent of the available dependencies. FFMPEG package sees a lot of modifications through time and I prefer to follow the changes applied to the native PKGBUILD as much as possible. The more it goes, the more flags are added and the more often we need to cherrypick commits (until a new release comes in).
This means I'll keep the dependencies around even if there is no obvious usecase for them.
Also, since openjpeg2 is still used with the native package, I'll also keep it around. Last thing I read about the JPEG2000 internal decoder was that it was faster, but that it was still introducing errors in the rendering. This probably explains why it is still enable in the native package. I look at it once in a while and things may have evolved since, but a quick checkup didn't bring up any tangible answer.
Now, if someone would like to take the ownership of this package, I would be more than pleased to hand it over. The same goes for any related packages that I maintain mostly for FFMPEG. lib32-libffmpeg and lib32-ffmpeg could be merged back together to simplify its maintenance.
Let me know if this is something you're interested in.
oxalin commented on 2018-02-25 07:37 (UTC) (edited on 2020-05-25 15:55 (UTC) by oxalin)
About GPG, it is up to you to import the missing public key. If you receive an error about it, this is ffmpeg's project public key. Something like the following should do the trick: gpg --recv-keys B4322F04D67658D8