LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 06-04-2016, 11:26 AM   #1
ahc_fan
Member
 
Registered: Jan 2009
Location: Seattle, WA
Distribution: Slackware64 14.2
Posts: 258

Rep: Reputation: 9
Trouble building Clementine again


Code:
Either crypto++ must be available or the non-GPL Spotify code must be
  compiled in
I'm trying to build Clementine 1.3.1 using modified SBo slackbuild and I get the error above, even with cryptopp installed. Cryptopp and libspotify are both listed as optional, and I have all the other non-optional dependencies installed.

I recall that libechonest is also required, so I installed that as well. I'm not sure what the problem is here. Maybe I built everything in the wrong order?

Last edited by ahc_fan; 06-04-2016 at 11:27 AM.
 
Old 06-04-2016, 12:17 PM   #2
willysr
Senior Member
 
Registered: Jul 2004
Location: Jogja, Indonesia
Distribution: Slackware-Current
Posts: 3,991

Rep: Reputation: 1237Reputation: 1237Reputation: 1237Reputation: 1237Reputation: 1237Reputation: 1237Reputation: 1237Reputation: 1237Reputation: 1237
where did you get that SlackBuild?
in master branch, cryptopp and libechonest are no longer considered optional dependency
 
Old 06-04-2016, 12:31 PM   #3
ahc_fan
Member
 
Registered: Jan 2009
Location: Seattle, WA
Distribution: Slackware64 14.2
Posts: 258

Original Poster
Rep: Reputation: 9
I got it from slackbuilds.org.

I tried the master branch one. It looks like I have all the requirements(chromaprint, cryptopp, libechonest, protobuf). Still get that error though.

Last edited by ahc_fan; 06-04-2016 at 12:39 PM.
 
Old 06-04-2016, 12:42 PM   #4
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 6,138

Rep: Reputation: 3839Reputation: 3839Reputation: 3839Reputation: 3839Reputation: 3839Reputation: 3839Reputation: 3839Reputation: 3839Reputation: 3839Reputation: 3839Reputation: 3839
Did you get all the dependencies from the master branch? The 14.1 builds are not intended to work on -current, nor necessarily work as dependencies for things built in the master branch. Everything in the master branch is intended to work together, just as everything with the 14.1 branch are intended to work together. Mixing and matching 14.1 packages with -current packages are not supported.
 
1 members found this post helpful.
Old 06-04-2016, 12:49 PM   #5
ahc_fan
Member
 
Registered: Jan 2009
Location: Seattle, WA
Distribution: Slackware64 14.2
Posts: 258

Original Poster
Rep: Reputation: 9
To be honest I didn't even know about the master branch. What I did was get the latest versions of the source for each dependency(instead of the source provided on SBo), and edited the slackbuilds as necessary.

I will try the slackbuilds on the master branch then. Hopefully that will do it.
 
Old 06-04-2016, 01:04 PM   #6
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 6,138

Rep: Reputation: 3839Reputation: 3839Reputation: 3839Reputation: 3839Reputation: 3839Reputation: 3839Reputation: 3839Reputation: 3839Reputation: 3839Reputation: 3839Reputation: 3839
If use sbopkg, it has support for the master branch.

http://slackblogs.blogspot.com/2016/...-upcoming.html
 
1 members found this post helpful.
Old 06-04-2016, 01:55 PM   #7
willysr
Senior Member
 
Registered: Jul 2004
Location: Jogja, Indonesia
Distribution: Slackware-Current
Posts: 3,991

Rep: Reputation: 1237Reputation: 1237Reputation: 1237Reputation: 1237Reputation: 1237Reputation: 1237Reputation: 1237Reputation: 1237Reputation: 1237
At this point, the one displayed in the SBo's website is still based on Slackware 14.1 and it *may* not work when being tested on current due to massive changes happening during development cycle.

Your best option is to try using SBo's GIT master either manually cloning it or use automatic tools such as sbopkg, slpkg, sbotools, etc to help you build packages.
 
1 members found this post helpful.
Old 06-04-2016, 02:17 PM   #8
ahc_fan
Member
 
Registered: Jan 2009
Location: Seattle, WA
Distribution: Slackware64 14.2
Posts: 258

Original Poster
Rep: Reputation: 9
That's all it took. Thanks guys!
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Trouble building mod_gnutls blueh2o Linux - Software 4 01-05-2016 09:04 AM
trouble in building kernel nagabhushan Linux - Server 1 07-19-2012 01:50 PM
trouble building tigervnc mm3000 Slackware 4 09-06-2011 05:37 AM
Trouble building kxdocker 0.20 mauripop Linux - Software 2 04-20-2005 01:59 PM
Trouble building RAZOR froedi Linux - Software 3 02-13-2004 10:34 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 12:41 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration