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

« First ‹ Previous 1 .. 3 4 5 6 7 8 9 10 11 12 13 .. 21 Next › Last »

oxalin commented on 2022-02-19 19:09 (UTC)

@sgt-hartman : I can't seem to reproduce the build error, but I don't have an NVidia gpu. Could you apply the suggested patch and let me know if this helps you? https://git.ffmpeg.org/gitweb/ffmpeg.git/commit/52cc323735ced6e8095cfd3acea0e36e35c76eb2

oxalin commented on 2022-02-19 18:57 (UTC) (edited on 2022-03-29 18:26 (UTC) by oxalin)

@MarsSeed : it seems ffmpeg 4.4 will be temporary, since it is being used by only a few packages that were not updated to use ffmpeg 5.0.

@sgt-hartman : makedependencies and dependencies are (should unless I missed one) be the same as the native package. cuda_llvm should be handled by Clang to the best of my knowledge. I have no personal use of CUDA, but googling the error brought a recent commit that could/should fix it: https://git.ffmpeg.org/gitweb/ffmpeg.git/commit/52cc323735ced6e8095cfd3acea0e36e35c76eb2

I'll install the needed optional dependencies to try to trigger the build error and then apply the patch.

sgt-hartman commented on 2022-02-19 10:49 (UTC)

I've the following error trying to install lib32-ffmpeg 2:5.0-2: "ERROR: cuda_llvm requested but not found"

Full log: 

==> Retrieving sources...
  -> Cloning ffmpeg git repo...
Cloning into bare repository '/home/ben/.cache/yay/lib32-ffmpeg/ffmpeg'...
100   131  100   131    0     0    478      0 --:--:-- --:--:-- --:--:--   479
100 1886k    0 1886k    0     0  2469k      0 --:--:-- --:--:-- --:--:-- 4824k
==> Validating source files with sha256sums...
    1.3.2.tar.gz ... Passed
remote: Enumerating objects: 26685, done.
remote: Counting objects: 100% (26685/26685), done.
remote: Compressing objects: 100% (12726/12726), done.
remote: Total 653169 (delta 21371), reused 16926 (delta 13942)
Receiving objects: 100% (653169/653169), 161.77 MiB | 23.75 MiB/s, done.
Resolving deltas: 100% (525264/525264), done.
  -> Found ffmpeg-vmaf2.x.patch
  -> Found add-av_stream_get_first_dts-for-chromium.patch
==> Validating source files with b2sums...
    ffmpeg ... Skipped
    ffmpeg-vmaf2.x.patch ... Passed
    add-av_stream_get_first_dts-for-chromium.patch ... Passed
 -> amf-headers not satisfied, flushing install queue
==> Making package: lib32-ffmpeg 2:5.0-2 (Sat 19 Feb 2022 11:45:12 AM CET)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Updating ffmpeg git repo...
Fetching origin
  -> Found ffmpeg-vmaf2.x.patch
  -> Found add-av_stream_get_first_dts-for-chromium.patch
==> Validating source files with b2sums...
    ffmpeg ... Skipped
    ffmpeg-vmaf2.x.patch ... Passed
    add-av_stream_get_first_dts-for-chromium.patch ... Passed
==> Removing existing $srcdir/ directory...
==> Extracting sources...
  -> Creating working copy of ffmpeg git repo...
Cloning into 'ffmpeg'...
done.
Switched to a new branch 'makepkg'
==> Starting prepare()...
Auto-merging libavcodec/nvenc.c
Auto-merging libavcodec/nvenc.h
patching file configure
Hunk #1 succeeded at 3747 (offset -4 lines).
Hunk #2 succeeded at 6615 (offset -11 lines).
patching file doc/filters.texi
patching file libavfilter/vf_libvmaf.c
patching file libavformat/avformat.h
Hunk #1 succeeded at 1115 (offset 105 lines).
patching file libavformat/utils.c
Hunk #1 succeeded at 92 with fuzz 1 (offset -29 lines).
==> Starting pkgver()...
==> Sources are ready.
==> Making package: lib32-ffmpeg 2:5.0-2 (Sat 19 Feb 2022 11:45:16 AM CET)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> WARNING: Using existing $srcdir/ tree
==> Starting pkgver()...
==> Starting build()...
ERROR: cuda_llvm requested but not found

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

MarsSeed commented on 2022-02-01 04:12 (UTC) (edited on 2022-02-01 04:13 (UTC) by MarsSeed)

It seems even upstream Arch is going to keep ffmpeg 4.4 as a separate package alongside ffmpeg 5.0.

oxalin commented on 2022-01-27 21:55 (UTC)

I'll be updating the package to 5.0 directly once the native package will be available.

misharash commented on 2022-01-05 10:22 (UTC) (edited on 2022-01-05 11:00 (UTC) by misharash)

While building another package (lib32-chromaprint), I was getting the following critical issues:

/usr/bin/ld: warning: libvpx.so.6, needed by /usr/lib/gcc/x86_64-pc-linux-gnu/11.1.0/../../../../lib32/libavcodec.so, not found (try using -rpath or -rpath-link)
/usr/bin/ld: warning: libx264.so.161, needed by /usr/lib/gcc/x86_64-pc-linux-gnu/11.1.0/../../../../lib32/libavcodec.so, not found (try using -rpath or -rpath-link)
/usr/bin/ld: /usr/lib/gcc/x86_64-pc-linux-gnu/11.1.0/../../../../lib32/libavcodec.so: undefined reference to `vpx_codec_decode'

Solved by reinstalling lib32-libffmpeg. I wonder if there is any way to rebuild package automatically after its dependency libs are updated?

Rojikku commented on 2021-06-02 21:12 (UTC)

@oxalin

So, looked into it, that is decidedly not the issue. My problem I presume ended up being that I built lib32-x265 using aurto, which should chroot. And something must be wrong with their build process, because my PKG_CONFIG_DIR didn't contain x265.pc, which was needed for this process.

The logs did not indicate this, I just discovered it when I went looking for it after it was mentioned. Logs indicated it was found. (I got help in the IRC)

I will complain on lib32-x265, but the issue was solved by just doing a makepkg -sri of that package manually.

oxalin commented on 2021-06-02 04:53 (UTC) (edited on 2021-06-02 04:56 (UTC) by oxalin)

@Rojikku : could it be that your lib32-x265 and your x265 packages are of different versions? The error is usually misleading and pretty useless, but I've seen it before with x265 where the header files (part of x265 package) are from a different version than lib32-x265.

You'll find a trace in one of the log file from the build. Look at MarsSeed's comment from 2021-03-28 about build log src/ffmpeg/ffbuild/config.log

Rojikku commented on 2021-06-02 01:19 (UTC) 

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

For the love of god, why. I've been trying to compile lib32-gst-plugins-bad for like four hours.

I just want to sleep.

I can fix this by hacking the PKGBUILD with some random comments and making the configure script immutable after commenting out the part that allows it to error.

But then I get a very similar error from lib32-gst-plugins-bad so it's moot point. I don't even know if this compiled with x265 support or not.

I tried reading the configure script, and I think it relies on this:

pkg-config --exists --print-errors x265

Which actually seems to return true perfectly fine on my system, which I confirmed about 50 times in a row before doing a list--all | grep x265 and confirming it's there too.

What do you want from me, ./configure? I even guaranteed I'm not doing it wrong by trying x266 and x267, both of which obviously error.

Please, if anyone knows, tell me. I'm going to crash in bed. This is driving me mad.

oxalin commented on 2021-04-11 04:24 (UTC)

@MarsSeed: yes, I've discovered that around the same time you were commenting here. I was relying on an example from ArchLinux' wiki, but without any mention about the epoch. Thanks for notifying me.

I know ffmpeg 4.4 is now available, but I have to wait until ffmpeg package is updated before pushing the appropriate commit. Stay tuned.

« First ‹ Previous 1 .. 3 4 5 6 7 8 9 10 11 12 13 .. 21 Next › Last »