Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#54026 - [kodi] Self-compiled package links against non-mentioned dependencies (ffmpeg?)

Attached to Project: Community Packages
Opened by Manuel Reimer (M-Reimer) - Saturday, 13 May 2017, 10:43 GMT
Last edited by Doug Newgard (Scimmia) - Saturday, 13 May 2017, 15:40 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Ike Devolder (BlackEagle)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
I tried to recompile Kodi to add a patch to make wakeup for recordings working again:
https://github.com/xbmc/xbmc/pull/11917/commits
This will be in Kodi 17.2 but I don't want to wait for it.

If I create the package on my desktop, then Kodi doesn't start on my HTPC. It gives me the following error:

error while loading shared libraries labavcodec.so.57

Is it possible to configure Kodi to not link to this library even if it exists on the system, so self-created packages don't have the dependency to this library?
This task depends upon

Closed by  Doug Newgard (Scimmia)
Saturday, 13 May 2017, 15:40 GMT
Reason for closing:  Not a bug
Comment by Alexander Schnaidt (Namarrgon) - Saturday, 13 May 2017, 10:52 GMT
This is hardly a bug; if you build a package in an unclean environment you will get all sorts of side effects. Build the package in a chroot: https://wiki.archlinux.org/index.php/DeveloperWiki:Building_in_a_Clean_Chroot
Comment by Manuel Reimer (M-Reimer) - Saturday, 13 May 2017, 10:56 GMT
I think most people just run "makepkg" to get a package. At least this is the case with all PKGBUILDs on AUR.
I didn't have a look at the kodi configuration, but as far as I see, Kodi brings its own ffmpeg which is used if none on the system is found. There has to be some configuration option to force this.
If no fix is wanted for this, it would be wasted time to search for a fix, but if a patch would be accepted, I could have a look at the Kodi documentation to find out how to force the builtin ffmpeg.
Comment by Alexander Schnaidt (Namarrgon) - Saturday, 13 May 2017, 11:07 GMT
Most people who "just run makepkg" don't have the requirement of moving the packages to different systems, with different sets of packages, but install them locally only.
Comment by Antonio Rojas (arojas) - Saturday, 13 May 2017, 11:11 GMT
Assigning for the maintainer to clear up whether building the internal ffmpeg is intentional or not. If it is, then this is indeed not a bug as Namarrgon explained.
Comment by Ike Devolder (BlackEagle) - Saturday, 13 May 2017, 11:52 GMT
Building with internal ffmpeg is intentional for kodi, although they can link against system ffmpeg, there are usually little changes that make things work specifically well for kodi but those libs should be available in your package, when you build them in chroot or with makepkg should yield the same result.
Comment by Ike Devolder (BlackEagle) - Saturday, 13 May 2017, 11:53 GMT
For a portable result I suggest you just build this package in a chroot, install devtools and all should be fine

Loading...