Package Details: ffmpeg-compat-57 3.4.11-1

Git Clone URL: https://aur.archlinux.org/ffmpeg-compat-57.git (read-only, click to copy)
Package Base: ffmpeg-compat-57
Description: Compatibility package for ffmpeg to provide versions 57 of libavcodec, libavdevice and libavformat, not anymore provided by the ffmpeg package
Upstream URL: http://ffmpeg.org/
Keywords: libavcodec.so-57 libavdevice.so-57 libavformat.so-57 libavutil-55 libavutils-55
Licenses: GPL
Provides: libavcodec.so, libavdevice.so, libavfilter.so, libavformat.so, libavresample.so, libavutil.so, libpostproc.so, libswresample.so, libswscale.so
Submitter: SonnyX
Maintainer: HurricanePootis
Last Packager: HurricanePootis
Votes: 27
Popularity: 0.35
First Submitted: 2018-03-16 22:34 (UTC)
Last Updated: 2022-05-18 03:44 (UTC)

Required by (163)

Sources (3)

Latest Comments

xuanruiqi commented on 2021-10-22 08:33 (UTC)

Hi! LTO breaks the building of this package, so I think options=(!lto) is required.

HurricanePootis commented on 2021-10-22 04:03 (UTC)

If you have having trouble updating because of issues with libvpx, I was able to solve my issues by uninstall ffmpeg-compat-57, updating ffmpeg, then rebuilding ffmpeg-compat-57.

bar777 commented on 2021-06-28 09:58 (UTC)

@KohGeek Thank You Man!

tobil commented on 2021-05-09 09:20 (UTC)

Hello !

ffmpeg-compat-58 is needed ... Please !

KohGeek commented on 2021-04-14 02:42 (UTC)

If you have PGP errors, do the following:

curl -sS http://ffmpeg.org/ffmpeg-devel.asc | gpg --import -

HurricanePootis commented on 2021-03-23 13:08 (UTC) (edited on 2021-03-25 21:36 (UTC) by HurricanePootis)

I get some LD errors whenever compiling this with the latest versions of x265 and x264

/usr/bin/ld: /tmp/libavcodec.so.57.bh4Qv6.ltrans114.ltrans.o: warning: relocation against `pd_1' in read-only section `.text'
/usr/bin/ld: /tmp/libavcodec.so.57.bh4Qv6.ltrans28.ltrans.o: relocation R_X86_64_PC32 against undefined symbol `ff_h264_cabac_tables' can not be used when making a shared object; recompile with -fPIC
/usr/bin/ld: final link failed: bad value
collect2: error: ld returned 1 exit status
make: *** [ffbuild/library.mak:103: libavcodec/libavcodec.so.57] Error 1
/usr/bin/ld: /tmp/libpostproc.so.54.Plrt45.ltrans0.ltrans.o: warning: relocation against `w04' in read-only section `.text'
/usr/bin/ld: /tmp/libpostproc.so.54.Plrt45.ltrans0.ltrans.o: relocation R_X86_64_PC32 against undefined symbol `w05' can not be used when making a shared object; recompile with -fPIC
/usr/bin/ld: final link failed: bad value
collect2: error: ld returned 1 exit status
make: *** [ffbuild/library.mak:103: libpostproc/libpostproc.so.54] Error 1
make: *** Waiting for unfinished jobs....
/usr/bin/ld: /tmp/libswscale.so.4.tx4G1h.ltrans9.ltrans.o: warning: relocation against `pb_03' in read-only section `.text'
/usr/bin/ld: /tmp/libswscale.so.4.tx4G1h.ltrans8.ltrans.o: relocation R_X86_64_PC32 against undefined symbol `mask24l' can not be used when making a shared object; recompile with -fPIC
/usr/bin/ld: final link failed: bad value
collect2: error: ld returned 1 exit status
make: *** [ffbuild/library.mak:103: libswscale/libswscale.so.4] Error 1

Edit: This may have been because I have had -flto in my mamekpkg.conf, going to retry without it.

Edit 2: It was >:[

rharish commented on 2021-03-23 10:25 (UTC)

@D3SOX Thanks for the info, it worked!

D3SOX commented on 2021-03-23 10:03 (UTC)

@rharish It works fine. Just uninstall this, upgrade x265 and reinstall it. You can force uninstall it for the time being with sudo pacman -Rdd ffmpeg-compat-57

rharish commented on 2021-03-23 10:02 (UTC)

I got this error when updating packages:

:: installing x265 (3.5-1) breaks dependency 'libx265.so=192-64' required by ffmpeg-compat-57

@sgtxd Could you check if the latest version of x265 will work with this package? If not, could you create a package for the older version, say x265-compat?

sonuishaq67 commented on 2021-02-25 12:45 (UTC)

I get this error while building

==> Removing existing $pkgdir/ directory... ==> Starting build()... ERROR: gmp 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.freenode.net. Include the log file "ffbuild/config.log" produced by configure as this will help solve the problem. ==> ERROR: A failure occurred in build(). Aborting...

sgtxd commented on 2021-02-13 19:41 (UTC)

Alright, i took the task of maintaining this package. I'll try my best. I fixed the issue with openjpeg2 being listed as dependency instead of openjpeg.

vcekron commented on 2021-01-09 20:12 (UTC)

Same here, @sgtxd. Could this be added to the dependencies, please?

sgtxd commented on 2020-12-31 22:45 (UTC)

It seems you actually also need openjpeg (not openjpeg2) to actually build ffmpeg-compat-57.

Volker_Weissmann commented on 2020-10-19 23:59 (UTC) (edited on 2020-10-19 23:59 (UTC) by Volker_Weissmann)

I ran pacman-key --populate archlinux , but I'm still getting the "unknown public key B4322F04D67658D8 error message".

D3SOX commented on 2020-08-26 20:44 (UTC)

I don't know the reason why pacmac didn't work but I'm glad I could help

matt17br commented on 2020-08-26 20:41 (UTC)

Thank you, yay gets it done. I was trying to build it with pamac all this time, so dumb of me not to even try any other AUR package manager.

D3SOX commented on 2020-08-26 20:37 (UTC) (edited on 2020-08-26 20:38 (UTC) by D3SOX)

What are you trying to build the package with? I just successfully built it with yay -S ffmpeg-compat-57 (on Arch Linux but that shouldn't make a difference regarding this problem)
If it's still not working, you could add --skipinteg to makepkg.
This is not recommended but it will work.
With yay, you can use it like this: yay -S --mflags --skipinteg ffmpeg-compat-57

matt17br commented on 2020-08-26 20:29 (UTC)

The command does seem to work, and the output it yields tells me that the key has been imported, but when clean building the package I still get the exact same error as below.

D3SOX commented on 2020-08-26 08:52 (UTC)

@matt17br Try gpg --keyserver pool.sks-keyservers.net --recv-keys B4322F04D67658D8

matt17br commented on 2020-08-25 20:56 (UTC)

I can't seem to get this to build on Manjaro. I get

ffmpeg-3.4.2.tar.xz ... FAILED (unknown public key B4322F04D67658D8)

When running

gpg --search-keys B4322F04D67658D8

I get:

gpg: error searching keyserver: General error

yurikaka commented on 2020-04-06 00:28 (UTC)

So after makepkg, the generated package will be marked as depending on a specific version of libx265.so, this will break future upgrade process of x265. When you want to upgrade x265 in the future, you need to rebuild this package, is there any way to trigger the rebuilding automatically? (Just like what dkms do when kernel get upgraded.)

D3SOX commented on 2020-04-05 23:26 (UTC) (edited on 2020-04-05 23:33 (UTC) by D3SOX)

Clean building it did the trick. Thanks @jshap and sorry for my unawareness (I should have just read the other comments)

jshap commented on 2020-04-05 22:41 (UTC)

that this package is not out of date, you just need to remove and then clean build it.

gardotd426 commented on 2020-04-05 20:47 (UTC)

@D3SOX is correct, this package is broken and prevents updating the system due to this error:


error: failed to prepare transaction (could not satisfy dependencies)
:: installing x265 (3.3-1) breaks dependency 'libx265.so=179-64' required by ffmpeg-compat-57

D3SOX commented on 2020-04-05 19:50 (UTC) (edited on 2020-04-05 22:05 (UTC) by D3SOX)

Doesn't work with the latest version of x265

error: failed to prepare transaction (could not satisfy dependencies)
:: installing x265 (3.3-1) breaks dependency 'libx265.so=179-64' required by ffmpeg-compat-57

bunnybooboo commented on 2020-02-11 15:26 (UTC) (edited on 2020-02-11 15:27 (UTC) by bunnybooboo)

@anon54163 To closer inspect (thus avoiding the described "importing random keys" trust of the terminal print) you can inspect the PKGBUILD. By doing so you will observe that the B4322F04D67658D8 key is in fact listed as the "validpgpkeys" and has been at least since the initial commit in 2018. Therefor they match.

For the current commit: https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=ffmpeg-compat-57

and the initital commit from 2018 https://aur.archlinux.org/cgit/aur.git/commit/?h=ffmpeg-compat-57&id=8e7873f50cd9658457e67f5e0df79e5f7b0b4158

Read more on this makepkg oddity here: https://wiki.archlinux.org/index.php/makepkg#Signature_checking

anon54163 commented on 2020-01-04 19:44 (UTC) (edited on 2020-02-13 14:47 (UTC) by anon54163)

There is an error when validating ffmpeg-3.4.2.tar.xz. The PGP signature cannot be verified. I know I can import the key myself, but I'm not too comfortable importing random keys. This should ultimately not be necessary, like with other AUR packages.

JoelSanchez commented on 2019-11-14 10:10 (UTC)

I got the error regarding the x265 package, but I noticed I was trying to install ffmpeg-compat-57 from a different repo (chaotic-aur) instead of installing it from the AUR. Hope this helps someone.

WSDMatty commented on 2019-10-31 13:41 (UTC)

@E3LDDfrK I'm not sure exactly why that error pops up, but rebuilding ffmpeg-compat-57 solves the problem. looking at the pkgbuild and deps, ffmpeg- doesn't explicitly require libx265.so=176-64, I think that's some leftover fluff from a previous release of this package.

@fabiocorbo Added an upstream patch to fix the compiler errors you mentioned.

E3LDDfrK commented on 2019-10-30 23:58 (UTC) (edited on 2019-10-30 23:59 (UTC) by E3LDDfrK)

ALso got this error:

installing x265 (3.2-1) breaks dependency 'libx265.so=176-64' required by ffmpeg-compat-57

The solution was just uninstall ffmpeg-compat-57 and reinstall it.

But any idea what I did wrong originally? I almost always installed packages with an AUR helper called pikaur. Never had the error before.

WSDMatty commented on 2019-09-30 13:08 (UTC)

@fabiocorbo

Those are not errors. Those are warnings. If you had to interrupt the progress, that means it is building just fine, those are just warnings to let you know about things that could-and-should be addressed, but are not detrimental to the build/run of the package.

If the message says "warning:" You can ignore it unless it causes problems with the program running.

If the message says "error:" and the build process stops, You need to fix a problem before the program will build.

fabiocorbo commented on 2019-08-31 16:32 (UTC) (edited on 2019-08-31 17:28 (UTC) by fabiocorbo)

Hi, I'm trying to compile ffmpeg-compat57 both from pamac and from terminal, but I get errors like theese: CC libavdevice/alldevices.o In file included from ./libavutil/common.h:464, from ./libavutil/avutil.h:296, from ./libavutil/log.h:25, from libavdevice/avdevice.h:48, from libavdevice/alldevices.c:23: ./libavutil/mem.h:341:1: warning: ‘alloc_size’ attribute ignored on a function returning ‘int’ [-Wattributes] 341 | av_alloc_size(2, 3) int av_reallocp_array(void ptr, size_t nmemb, size_t size); | ^~~~~~~~~~~~~ CC libavdevice/alsa.o In file included from ./libavutil/common.h:464, from ./libavutil/avutil.h:296, from ./libavutil/log.h:25, from libavdevice/avdevice.h:48, from libavdevice/alsa.c:32: ./libavutil/mem.h:341:1: warning: ‘alloc_size’ attribute ignored on a function returning ‘int’ [-Wattributes] 341 | av_alloc_size(2, 3) int av_reallocp_array(void ptr, size_t nmemb, size_t size); | ^~~~~~~~~~~~~ CC libavdevice/alsa_dec.o In file included from ./libavutil/common.h:464, from ./libavutil/avutil.h:296, from ./libavutil/log.h:25, from ./libavutil/timer.h:49, from ./libavutil/internal.h:42, from libavdevice/alsa_dec.c:50: ./libavutil/mem.h:341:1: warning: ‘alloc_size’ attribute ignored on a function returning ‘int’ [-Wattributes] 341 | av_alloc_size(2, 3) int av_reallocp_array(void ptr, size_t nmemb, size_t size); | ^~~~~~~~~~~~~ CC libavdevice/alsa_enc.o In file included from ./libavutil/common.h:464, from ./libavutil/avutil.h:296, from ./libavutil/log.h:25, from ./libavutil/timer.h:49, from ./libavutil/internal.h:42, from libavdevice/alsa_enc.c:42: ./libavutil/mem.h:341:1: warning: ‘alloc_size’ attribute ignored on a function returning ‘int’ [-Wattributes] 341 | av_alloc_size(2, 3) int av_reallocp_array(void ptr, size_t nmemb, size_t size); | ^~~~~~~~~~~~~ CC libavdevice/avdevice.o In file included from ./libavutil/common.h:464, from ./libavutil/avutil.h:296, from ./libavutil/avassert.h:31, from libavdevice/avdevice.c:19: ./libavutil/mem.h:341:1: warning: ‘alloc_size’ attribute ignored on a function returning ‘int’ [-Wattributes] 341 | av_alloc_size(2, 3) int av_reallocp_array(void *ptr, size_t nmemb, size_t size); | ^~~~~~~~~~~~~ I had to interrumpt the process because it keeps going on like this. Please, can someone help me? I'm using manjaro xfce18

jerz4evr commented on 2019-03-07 20:35 (UTC) (edited on 2019-03-07 20:36 (UTC) by jerz4evr)

@Ketchup901: First, you need to remove the old package by running sudo pacman -R ffmpeg-compat-57, run an update (sudo pacman -Syu) and go back to the directory which you cloned this repository (assuming you used git) and run makepkg -fsi. This should rebuild the package properly.

Ketchup901 commented on 2019-03-06 08:12 (UTC) (edited on 2019-03-06 08:12 (UTC) by Ketchup901)

Prevents update of libvpx:

:: installing libvpx (1.8.0-1) breaks dependency 'libvpx.so=5-64' required by ffmpeg-compat-57

jshap commented on 2019-02-06 00:41 (UTC)

@Plailect do a clean build (makepkg -f)

commented on 2019-02-05 18:47 (UTC)

I am currently getting the following trying to install this:

:: unable to satisfy dependency 'libx265.so=165-64' required by ffmpeg-compat-57

This seems to be caused by the recent update to libx265.

SonnyX commented on 2018-11-12 15:56 (UTC) (edited on 2018-11-12 15:57 (UTC) by SonnyX)

@applebloom Yes it is for programs that require these libraries during runtime. I originally set it up for Atom if I remember correctly, I used the git version of ffmpeg which provided newer version libraries than the program looked for. Therefor I created this package as I figured other people would probably run into the same issue as me. I already stopped using the program and thus this package, but it is here for whoever still requires it.

applebloom commented on 2018-11-12 15:08 (UTC)

@SonnyX Thanks for explaining. So this package is for programs that are already built and just need the so files to link with?

SonnyX commented on 2018-11-11 20:31 (UTC) (edited on 2018-11-11 20:39 (UTC) by SonnyX)

@applebloom You are right, ffmpeg3.4 can also be installed next to other ffmpeg packages since it renames the ffmpeg binary, he should probably update his provides to include ffmpeg3.4. In that case you can see this package as the minimal version compared to a full install of ffmpeg. The pkgconfig folder provided by ffmpeg and the includes are unnecessary to the targeted programs. I see that your use case was for the mplayer2, the package ffmpeg3.4 fits your needs better in the case of mplayer2 which uses ffmpeg as a build dependency.

SonnyX commented on 2018-11-11 18:53 (UTC)

@applebloom This package differs from ffmpeg3.4 in the way that it does not provide ffmpeg. It provides a specific version of ffmpeg libraries (version 57) required by specific programs. This can be installed along with ffmpeg version 4.0.3 as an example.

applebloom commented on 2018-11-11 18:47 (UTC)

How does this package differ from ffmpeg3.4, also on AUR?

7314776 commented on 2018-08-18 15:35 (UTC)

.SRCINFO ... pkgver = 3.4.2 pkgrel = 2 ...

But in PKGBUILD here ... pkgver=3.4.2 pkgrel=1 ...

So forming package name after building gives 3.4.2-1 instead of 3.4.2-2, pacman thinks its not an update, but a reinstall of the same package version.

SonnyX commented on 2018-08-17 20:34 (UTC) (edited on 2018-08-17 20:48 (UTC) by SonnyX)

@brittyazel I see, the dependency seems to have been renamed from libx264.so (and libx264-all.so) to libx264.so=somepackage-version, however both new and old seemed to support libx264, so gonna rename it to libx264 and gonna test if it builds and will update the package then.

brittyazel commented on 2018-08-17 20:24 (UTC)

You're right, it seems to build and install correctly once the new x264 libs are installed, but it hits a dependency cycle with the default repositories preventing pacman from updating until this package is removed first.

SonnyX commented on 2018-08-17 07:15 (UTC)

@brittyazel Package builds just fine with latest x264.so

Tested using the following commands:

mkdir ~/git
cd ~/git
git clone https://aur.archlinux.org/ffmpeg-compat-57.git ffmpeg-compat-57
cd ffmpeg-compat-57
mkdir ./chroot
CHROOT=~/git/ffmpeg-compat-57/chroot
sudo pacman -S devtools
mkarchroot $CHROOT/root base-devel
arch-nspawn $CHROOT/root pacman -Syu
makechrootpkg -c -r $CHROOT

jhernberg commented on 2018-06-24 11:37 (UTC)

@klemens: Right you are. For some reason I can't explain I was starting from the older 3.3.4 buildscript. Sorry for the noise and please ignore! :)

klemens commented on 2018-06-23 22:55 (UTC)

This package already provides libswscale.so.4 (4.8.100). Are you sure that you are using the newest version?

jhernberg commented on 2018-06-23 16:31 (UTC)

This script adds it: https://gist.github.com/jhernberg/c0e380a4ac9c985e0206919874d21558

jhernberg commented on 2018-06-23 16:13 (UTC)

Could you please add libswscale.so.4 too, as I need it for reaper.

SonnyX commented on 2018-05-29 16:47 (UTC)

@pavlushka the dependency is now only openjpeg2

SonnyX commented on 2018-05-29 16:46 (UTC)

Updated the package with changes klemens (and thus redg3ar) mentioned and verified the package.

klemens commented on 2018-05-23 01:03 (UTC)

I have updated the package to ffmpeg 3.4.2, which provides the same library versions as the 3.3 series. The patch includes the modifications from @redg3ar. I also cleaned up the dependencies and configure switches based on the ffmpeg package in extra before the update to 4.0. It now builds without problems in a clean chroot.

pavlushka commented on 2018-05-19 22:06 (UTC)

@Sonnyx but your PKGBUILD mentioned openjpeg as dependency and openjpeg2 and openjpeg are not in conflict and had to install openjpeg also to make the compiling happen.

f1u77y commented on 2018-05-15 05:34 (UTC)

It complains: ERROR: libopenjpeg not found. The patch is for libopenjpeg 2.2 but there is already openjpeg 2.3. Substituting 2.2 with 2.3 everywhere in the patch helps. Please update the package.

bepvte commented on 2018-05-11 14:25 (UTC)

https://pastebin.com/fKy5jBgJ this patch enables swrescale 57 and other libraries that arent provided by the new version of ffmpeg, I have tested it and it works. This is the first time I have used the 'provides' field so there might be a problem there.

SonnyX commented on 2018-04-22 11:46 (UTC)

@Saren I already include openjpeg2 in the dependency list, which is version two of openjpeg afaik?

Saren commented on 2018-04-21 13:36 (UTC)

please add openjpeg into dependency list