Package Base Details: lib32-ffmpeg

Git Clone URL: (read-only, click to copy)
Submitter: lano1106
Maintainer: oxalin
Last Packager: oxalin
Votes: 32
Popularity: 1.54
First Submitted: 2013-05-18 04:43
Last Updated: 2021-05-10 12:46

Pinned Comments

oxalin commented on 2018-02-25 07:37

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

Latest Comments

« First ‹ Previous ... 2 3 4 5 6 7 8 9 10 11 12 ... Next › Last »

cloverskull commented on 2018-10-06 19:39

@oxalin I'm running into the same error about libv4l2 not being found.

I've confirmed all files you've asked about do exist on my filesystem.

$ pkg-config --libs /usr/lib32/pkgconfig/libv4l2.pc -L/usr/lib32 -lv4l2

Please advise, thanks!

oxalin commented on 2018-10-03 15:06

@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/ and usr/lib/ installed? Also, do you have usr/lib32/pkgconfig/libv4l2.pc and usr/lib/pkgconfig/libv4l2.pc installed which should be used by pkg-config?

unknown78 commented on 2018-09-22 14:56

I get the following error. Can someone help?

ERROR: libv4l2 not found using pkg-config

oxalin commented on 2018-08-21 03:30

GordonGR: Thank you, I'll be updating lib32-ffmpeg package in a few minutes.

GordonGR commented on 2018-08-18 16:17

Just letting you know I created the package lib32-x264 as the equivalent to the renewed extra/x264 that replaced the extra/libx264* packages.

oxalin commented on 2018-06-16 15:16

Zaplo, could you post the error please? I'm not having any problem on my side.

zaplo commented on 2018-06-16 12:02

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

oxalin commented on 2018-06-12 07:55

@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.

ZIPS commented on 2018-06-03 18:35

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

oxalin commented on 2018-04-17 05:48

@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.