Package Base Details: lib32-ffmpeg

Git Clone URL: (read-only, click to copy)
Submitter: lano1106
Maintainer: oxalin
Last Packager: oxalin
Votes: 31
Popularity: 0.94
First Submitted: 2013-05-18 04:43
Last Updated: 2021-04-02 19:58

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 1 2 3 4 5 6 7 8 9 10 ... Next › Last »

QuartzDragon commented on 2019-07-16 14:49

Output is x265 x265 - H.265/HEVC video encoder and 3.0 respectively.

oxalin commented on 2019-07-16 14:45

@QuartzDragon : it seems right. Could you send me what is displayed by the following commands :

pkg-config-32 --list-all | grep x265 pkg-config-32 --modversion x265

QuartzDragon commented on 2019-07-16 00:21

Here we go. I'm using the vanilla x265.pc file


Name: x265
Description: H.265/HEVC video encoder
Version: 3.0
Libs: -L${libdir} -lx265
Libs.private: -lstdc++ -lm -lgcc_s -lgcc -lgcc_s -lgcc -lrt -ldl -lnuma
Cflags: -I${includedir}

oxalin commented on 2019-07-15 17:42

@QuartzDragon : Nothing was changed from previous version (4.1.3) on that matter. However, some changes were made to a previous version.

Is lib32-x265 installed? If so, is it up to date? lib32-x265 was not correctly setting up its .pc file until recently (when I proposed a fix). Could you share your x265.pc file (/usr/lib32/pkgconfig/x265.pc)?

QuartzDragon commented on 2019-07-14 09:57

Anyone else getting this error, even with the latest lib32-x265 installed?

==> Starting build()...
ERROR: x265 not found using pkg-config

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 mailing list or IRC #ffmpeg on
Include the log file "ffbuild/config.log" produced by configure as this will help
solve the problem.
==> ERROR: A failure occurred in build().

oxalin commented on 2019-04-26 18:13

@QuartzDragon: no, I don't have any problem when rebuilding from scratch. Thanks for the cue about lib32-aom. I'm pushing an updated package right now.

QuartzDragon commented on 2019-04-24 07:58

Also, you can enable lib32-aom now, as it exists. :)

QuartzDragon commented on 2019-04-24 02:31

Does anyone else's build just hang forever trying to link:

LD libswresample/

oxalin commented on 2019-04-07 21:41

@mokkurkalve indeed, it still fails. lib32-x264 should be fixed to address the problem: pkgver was not properly updated as it should have.

mokkurkalve commented on 2019-04-03 14:21

The maintainer of lib32-x264 yesterday DID what you asked in your comment over there, he updated to revision 72db437770fd1ce3961f624dd57a8e75ff65ae0b. But by then you had updated lib32-ffmpeg to demand v 157, which he DID NOT update for.... So lib32-ffmpeg can still not be installed, it just throws: ==> Error: Could not find all required packages: lib32-x264>=157 (Wanted by: lib32-ffmpeg)