Package Details: lib32-ffmpeg 1:4.2.1-1

Git Clone URL: (read-only)
Package Base: lib32-ffmpeg
Description: Complete solution to record, convert and stream audio and video (32 bit)
Upstream URL:
Licenses: GPL3
Submitter: lano1106
Maintainer: oxalin
Last Packager: oxalin
Votes: 29
Popularity: 0.727462
First Submitted: 2013-05-18 04:43
Last Updated: 2019-09-18 06:37

Required by (78)

Sources (1)

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 --keyserver x-hkp:// --recv-keys B4322F04D67658D8

Latest Comments

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

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.

Enverex commented on 2018-04-16 10:57

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

Enverex commented on 2018-04-10 13:51

Not sure if something's changed my side or whether another package has broken compatibility, but this suddenly won't build. Fails with "ERROR: gnutls not found using pkg-config". Both gnutls and lib32-gnutls are already installed. The actual error appears to be...

gcc -m32 -Wl,-O1,--sort-common,--as-needed,-z,relro -Wl,--as-needed -Wl,-z,noexecstack -I/usr/include/p11-kit-1 -L/usr/lib32 -o /tmp/ffconf.fgfxB5vm/test /tmp/ffconf.fgfxB5vm/test.o -lgnutls -framework AppKit

gcc: error: AppKit: No such file or directory

gcc: error: unrecognized command line option '-framework'

ERROR: gnutls not found using pkg-config

oxalin commented on 2018-03-06 06:04

Thanks for your test. I was about to ask to the lib32-libx264 (and also possibly the libx264) maintainer to have a look on his side. You give me a valid argument.

DarkPhoenixFF4 commented on 2018-03-05 00:12

Just to let you know, the problem seems to be with lib32-libx264, not this package. I removed the dependency on lib32-ffmpeg it had and built it manually with no problems.

oxalin commented on 2018-02-25 09:10

@TemplarGR and @SteelTitanium: well, there was a circular dependency that I read about, but it was from 2014. From your comments, I've been digging again and I found out yesterday that there is a new problem about a circular dependency. I'll investigate it further.