Review your favorite Linux distribution.
Go Back > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Slackware This Forum is for the discussion of Slackware Linux.


  Search this Thread
Old 04-23-2018, 07:38 PM   #16
Registered: Oct 2005
Location: Connecticut USA
Distribution: SalixOS
Posts: 185

Rep: Reputation: 92

Originally Posted by orbea View Post
Whether it "works" or not, its an incredibly terrible hack that is liable to break something somewhere down the line. Probably when you no longer remember doing it...
I understand the potential issues that hacks like this can result in, but in this case is it really a potential problem for anything besides Spotify?

Last edited by laprjns; 04-23-2018 at 07:51 PM.
Old 04-23-2018, 08:37 PM   #17
Senior Member
Registered: Feb 2015
Distribution: Slackware64-current
Posts: 1,474

Rep: Reputation: Disabled
Its hard to say, I'm not sure how many programs will try to link against that debian specific library if present. If any do and that symlink then breaks at a later point it could lead to an interesting and possibly non-obvious build or run-time error.
Old 04-23-2018, 08:38 PM   #18
Registered: Mar 2006
Distribution: Slackware64 -current
Posts: 268
Blog Entries: 1

Rep: Reputation: 78
Initially, I would have argued that on Slackware it's unlikely that you'd be compiling anything against that link. But there's a difference between doing something like this on my own machine vs posting it on the forum as a potential solution. At a minimum, it was an ill-advised post.

Anyway, the hack relies on "similar" implementations of the same protocol. It's ugly from the very beginning.
1 members found this post helpful.
Old 04-26-2018, 06:58 PM   #19
Registered: Aug 2010
Posts: 325

Rep: Reputation: 140Reputation: 140
What I have done for the latest version of spotify is to compile curl-7.59.0 against gnutls. This requires more intervention than it may seem: compiling with the

--with-ca-bundle=/usr/share/curl/ca-bundle.crt --without-ssl --with-gnutls
options was not enough. It was also necessary temporarily to uninstall the openssl and openssl-solibs packages while configuring and compiling curl in order to obtain a openssl free shared library file. The only thing you then need from this compilation is the resulting shared library file at curl-7.59.0/lib/.libs/ You can rename this as and place it under that name in /usr/lib[64] in your spotify package. The rest of the resulting curl compile should be ignored - you don't want to interfere with the standard slackware curl installation.

So far that has been working fine for me.
1 members found this post helpful.


error message, slackbuild, slackware64, spotify

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
OpenSSL and GNUTLS are insecure by default on Slackware64 14.2 Matt Owen Slackware 8 01-18-2018 05:30 AM
Spotify segmentation fault on Slackware64 14.0 stahlkrantz Slackware 8 06-11-2013 03:10 AM
required rpm teabagindia Linux - Mobile 8 09-15-2010 05:52 AM
PyQt4 module error in SlackBuild for Slackware 12.2 under Slackware64 13... Alexvader Slackware 3 12-28-2009 05:02 PM
Kmymoney2 Slackware64 Sbo Slackbuild Error AlleyTrotter Slackware 4 07-05-2009 11:10 PM > Forums > Linux Forums > Linux - Distributions > Slackware

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

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