Package Details: lib32-ffmpeg 2:7.0.2-3

Git Clone URL: https://aur.archlinux.org/lib32-ffmpeg.git (read-only, click to copy)
Package Base: lib32-ffmpeg
Description: Complete solution to record, convert and stream audio and video (32 bit)
Upstream URL: http://ffmpeg.org
Licenses: GPL-3.0-only
Conflicts: lib32-libffmpeg
Provides: libavcodec.so, libavdevice.so, libavfilter.so, libavformat.so, libavutil.so, libpostproc.so, libswresample.so, libswscale.so
Replaces: lib32-libffmpeg
Submitter: lano1106
Maintainer: oxalin
Last Packager: oxalin
Votes: 37
Popularity: 0.006711
First Submitted: 2013-05-18 04:43 (UTC)
Last Updated: 2024-09-27 17:48 (UTC)

Required by (291)

Sources (2)

Pinned Comments

oxalin commented on 2024-04-09 22:05 (UTC)

For those wondering: I intentionally keep this package as close to the native package as possible, to the extent of the available dependencies. FFMPEG package sees a lot of modifications through time and I prefer to follow the changes applied to the native PKGBUILD as much as possible. The more it goes, the more flags are added and the more often we need to cherrypick commits (until a new release comes in).

This means I'll keep the dependencies around even if there is no obvious usecase for them.

Also, since openjpeg2 is still used with the native package, I'll also keep it around. Last thing I read about the JPEG2000 internal decoder was that it was faster, but that it was still introducing errors in the rendering. This probably explains why it is still enable in the native package. I look at it once in a while and things may have evolved since, but a quick checkup didn't bring up any tangible answer.

Now, if someone would like to take the ownership of this package, I would be more than pleased to hand it over. The same goes for any related packages that I maintain mostly for FFMPEG. lib32-libffmpeg and lib32-ffmpeg could be merged back together to simplify its maintenance.

Let me know if this is something you're interested in.

oxalin commented on 2018-02-25 07:37 (UTC) (edited on 2020-05-25 15:55 (UTC) by oxalin)

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

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

unit73e commented on 2024-10-25 13:30 (UTC)

@oxalin I've adopted the lib32-x265 package which was outdated (3.5 and should be 3.6) and ends up fixing your package. If you want to maintain both that's okay by me.

oxalin commented on 2024-08-03 19:57 (UTC)

@RJ-2906: pl_log_create comes from pl_log, which is related to libplacebo. Libplacebo was updated recently. I maintain the lib32-libplacebo package. Following the native package's update, I updated it in the last few days to version 7.349.0, thus the "349" at the end of pl_log_create_349.

Updating lib32_libplacebo should fix your issue.

RJ-2906 commented on 2024-07-21 09:32 (UTC) (edited on 2024-07-21 09:39 (UTC) by RJ-2906)

Even after working around the x265 error by updating the package manually, lib32-ffmpeg won't build. Any ideas?

/usr/bin/ld: libavcodec/x86/aacencdsp.o: warning: relocation in read-only section           `.text'
/usr/bin/ld: warning: creating DT_TEXTREL in a shared object
LD  libavformat/libavformat.so.61
LD  libavfilter/libavfilter.so.10
/usr/bin/ld: libavfilter/x86/af_volume.o: warning: relocation in read-only section     `.text'
/usr/bin/ld: warning: creating DT_TEXTREL in a shared object
LD  libavdevice/libavdevice.so.61
LD  ffmpeg_g
LD  ffplay_g
/usr/bin/ld: /tmp/ccmu0c4C.ltrans0.ltrans.o: in function `create.lto_priv.0':
<artificial>:(.text+0xa6a): undefined reference to `pl_log_create_349'
collect2: error: ld returned 1 exit status
make: *** [Makefile:136: ffplay_g] Error 1
make: *** Waiting for unfinished jobs....
/usr/bin/ld: libavfilter/libavfilter.so: undefined reference to `pl_log_create_349'
collect2: error: ld returned 1 exit status
make: *** [Makefile:136: ffmpeg_g] Error 1
==> ERROR: A failure occurred in build().
    Aborting...
 -> error making: lib32-ffmpeg-exit status 4
 -> Failed to install the following packages. Manual intervention is required:
lib32-ffmpeg - exit status 4

oxalin commented on 2024-07-01 04:19 (UTC)

The x265 error is caused by a mismatch between the native package, which contains the header files, and the lib32 package which doesn't and is outdated. Once the lib32 package will be updated (or if you do it manually), things will get in line and work.

HisDudeness commented on 2024-06-25 07:28 (UTC)

@jaska Yes, also installing the package manually allows you to change the version. You must download the snapshot in the AUR page, extract the package, edit the PKGBUILD with the editor of your choice and then, in the extracted package's folder, do makepkg -s to download sources and build them and, if the process ends succesfully, do sudo pacman -U on the resulting pkg.tar.zst package. Current version seems to be 3.6-1.

Jaska commented on 2024-06-24 18:28 (UTC) (edited on 2024-06-24 22:04 (UTC) by Jaska)

@zepar How did you manually upgrade the version? The current version in the AUR is 3.5-2.

EDIT: It turns out that with aur sync you can just edit version number in PKGBUILD-file and it works

Jaska commented on 2024-06-24 01:31 (UTC)

I also get the ERROR: x265 not found using pkg-config -error

NeWolf commented on 2024-06-23 19:52 (UTC)

I get the same error when trying to build.

zepar commented on 2024-06-23 08:15 (UTC) (edited on 2024-06-24 03:46 (UTC) by zepar)

Fails to build


==> 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
ffmpeg-user@ffmpeg.org mailing list or IRC #ffmpeg on irc.libera.chat.
Include the log file "ffbuild/config.log" produced by configure as this will help
solve the problem.
==> ERROR: A failure occurred in build().
    Aborting...
 -> error making: lib32-ffmpeg-exit status 4

Edit: fixed by updating lib32-x265 to version 3.6

thaewrapt commented on 2024-05-26 23:38 (UTC) (edited on 2024-05-26 23:44 (UTC) by thaewrapt)

Those -git packages also use a versioning scheme from upstream not Arch packaging (without epoch 2:), so it probably fails the check because of that.

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