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

1 2 3 4 5 6 ... Next › Last »

oxalin commented on 2019-08-30 19:00

@sl1pkn07 please, how did you come to that conclusion? I asked the same question in another package. Many lib32 packages, even officials, use the provide option without any problem with their native x64 counterparts. On my side, I don't have any drawback causes by the provides option.

sl1pkn07 commented on 2019-08-30 14:47

please remove,,,,,,, in provides. break ffmpeg package

Strunkenbold commented on 2019-07-20 08:16


Thx for finding the issue. Unfortunately lib32-x265 is still at 3.0...

QuartzDragon commented on 2019-07-17 07:11

Turns out to have been caused by a version mismatch between the 64-bit and 32-bit x265 libraries. I use the testing repos, which supplies x265 3.1. lib32-x265 is 3.0. Upgrading lib32-x265 to 3.1 allowed lib32-ffmpeg to find the library.

lib32-ffmpeg is then seemingly using pkg-config to find the 64-bit x265 version, and derive the 32-bit version from that, so it's no wonder that lib32-ffmpeg couldn't find it...

oxalin commented on 2019-07-16 15:39

Well, everything seems fine. On my side, I removed lib32-x265 and lib32-ffmpeg before reinstalling them and everything went just fine. Could you delete your lib32-ffmpeg build folder in case it is keeping something wrong from a previous installation? It could be under ~/.cache/<yourselectedAURtool>/

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().