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