-current with 4.14.3 can't build kodi from ponce sbo repo
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: Slackware64-current on Thinkpad Carbon X1
Posts: 264
Rep:
-current with 4.14.3 can't build kodi from ponce sbo repo
Ok.. I hate to ask this because I know it is probably an obvious answer. I tried and tried but can't figure it out. So here we go.
I am completely up to date with -current *including the testing kernel*
I have sbo set up to sync with ponce git repo for current.
However, when trying to install I get the following error
Code:
chmod: cannot operate on dangling symlink './tools/depends/target/ffmpeg/ffmpeg-3.1.9-Krypton-17.4.tar.gz'
patching file xbmc/filesystem/FTPParse.cpp
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
3 out of 3 hunks ignored -- saving rejects to file xbmc/filesystem/FTPParse.cpp.rej
kodi:
Would you like to continue processing the rest of the
queue or would you like to abort? If this failed
package is a dependency of another package in the queue
then it may not make sense to continue.
(Y)es to continue, (N)o to abort, (R)etry the build?:
Distribution: Slackware64-current on Thinkpad Carbon X1
Posts: 264
Original Poster
Rep:
Quote:
Originally Posted by ponce
try using the script for 14.2 from SBo: does that work?
I suppose the patch I added in july isn't necessary anymore.
Thanks for the reply. I changed the repo to 14.2 and it still fails but much later in the process. This time complaining about -lva and -lva-x11
Code:
CPP xbmc/platform/posix/main.o
AR xbmc/platform/posix/posix.a
LD kodi.bin
/usr/lib64/gcc/x86_64-slackware-linux/7.2.0/../../../../x86_64-slackware-linux/bin/ld: cannot find -lva-x11
/usr/lib64/gcc/x86_64-slackware-linux/7.2.0/../../../../x86_64-slackware-linux/bin/ld: cannot find -lva
collect2: error: ld returned 1 exit status
make: *** [Makefile:453: kodi.bin] Error 1
kodi:
Would you like to continue processing the rest of the
queue or would you like to abort? If this failed
package is a dependency of another package in the queue
then it may not make sense to continue.
(Y)es to continue, (N)o to abort, (R)etry the build?:
I've just tried on a full and clean installation of slackware64-current and compilation went fine with the kodi script on SBo.
judging from the output that you got when linking the kodi binary I suppose you have still some dependency (mandatory or optional, or dependency of some dependency, and so on...) built against the old libva and that gives you that error when linking: you should rebuild whatever uses the old libva to use the new one.
Distribution: Slackware64-current on Thinkpad Carbon X1
Posts: 264
Original Poster
Rep:
Quote:
Originally Posted by ponce
I've just tried on a full and clean installation of slackware64-current and compilation went fine with the kodi script on SBo.
judging from the output that you got when linking the kodi binary I suppose you have still some dependency (mandatory or optional, or dependency of some dependency, and so on...) built against the old libva and that gives you that error when linking: you should rebuild whatever uses the old libva to use the new one.
Thanks. That is helpful. Is there an easy way to find out what packages are build using the old libva?
Going to do a little searching to see if there is a script to figure it out...
Distribution: Slackware64-current on Thinkpad Carbon X1
Posts: 264
Original Poster
Rep:
I have sbbdep a try but there are so many deps for Kodi that I am not sure it narrowed things down too much. I think the quickest way to solve this might be.
1. slackpkg clean-system
followed by
2. deleting everything I installed from SBO (other than libreoffice most are related to kodi anyway)
3. Rebuild kodi again from the queue file will all deps.
However, since everything is working I might just leave it alone... having 2 versions of lva doesn't seem to be causing any trouble.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.