Package Base Details: lib32-ffmpeg

Git Clone URL: https://aur.archlinux.org/lib32-ffmpeg.git (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 ... 3 4 5 6 7 8 9 10 11 12 13 Next › Last »

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.

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

TemplarGR commented on 2018-02-24 12:30

There is an error when trying to build this package, it depends on lib32-libx264, yet lib32-libx264 depends on lib32-ffmpeg. I suppose someone who is just updating any of those 2 shouldn't face any issue, but anyone doing a fresh install will encounter this cyclical dependency. The fun part is that lib32-libx264 no longer shows up when searhing for it here (so i couldn't find its maintainer to ask), yet yaourt and packer find the pkgbuild...

oxalin commented on 2018-02-23 18:52

@SteelTitanium: you "can't". In fact, from what I have read on x264 forum, libx264 (the library itself) doesn't depend on ffmpeg. However, x264 have an optional dependency at build time against ffmpeg. Now, that being said, are you getting an error while trying to install the current package?

SteelTitanium commented on 2018-02-19 23:56

How do you break the dependency cycle, lib32-ffmpeg depends on lib32-libx264 and lib32-libx264 depends on lib32-ffmpeg.

oxalin commented on 2017-12-17 21:22

@unknown78: nothing changed since last version except version number and sha256sum.

The first step executed in the build() step is configure, which can take a moment to process. However, it should move to the next step, which is "make".

Could you restart your system and see if that helps if you didn't try it yet?