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-21-2011, 11:15 PM   #1
manzdagratiano
LQ Newbie
 
Registered: Mar 2011
Location: NJ, USA
Distribution: Ubuntu, Arch Linux, Debian Sid, Slackware64-current, Gentoo
Posts: 26

Rep: Reputation: 12
Why does Conky depend on Audacious?!!!


Hi All!

I noticed I had audacious installed on my system, and having been a fan of setting up a minimal Slackware system, I purged it immediately. But, subsequently, conky refused to start with the error message:

conky: error while loading shared libraries: libaudcore.so.1: cannot open shared object file: No such file or directory


Reinstalling audacious and audacious-plugins fixed the issue. Now I have nothing against audacious - that was the first audio player I had ever used in GNU/Linux, on a Knoppix CD (well, xmms actually). But why on earth does conky depend on a shared library that is part of audacious? I do not have audacious on my other distros, so I am flabbergasted!
 
Old 06-21-2011, 11:22 PM   #2
andrewthomas
Senior Member
 
Registered: May 2010
Location: Chicago Metro
Distribution: Arch, Gentoo, Slackware
Posts: 1,690

Rep: Reputation: 307Reputation: 307Reputation: 307Reputation: 307
When you built conky, you had audacious on your system and it must of linked to it.

If you would have rebuilt conky after removing audacious, it would work just fine.
 
Old 06-21-2011, 11:40 PM   #3
thegato
Member
 
Registered: Nov 2006
Posts: 42

Rep: Reputation: 4
Audacious should be disabled by default. However if you're using the script from slackbuilds.org it has --enable-audacious set.

Just remove it or switch it to --disable-audacious
 
Old 06-22-2011, 12:50 AM   #4
manzdagratiano
LQ Newbie
 
Registered: Mar 2011
Location: NJ, USA
Distribution: Ubuntu, Arch Linux, Debian Sid, Slackware64-current, Gentoo
Posts: 26

Original Poster
Rep: Reputation: 12
Quote:
Originally Posted by thegato View Post
Audacious should be disabled by default. However if you're using the script from slackbuilds.org it has --enable-audacious set.

Just remove it or switch it to --disable-audacious
Aha! Herein lies the culprit - I indeed did build from Slackbuilds.org! Thanks! I would expect that the default behavior would be to disable audacious support.
 
Old 06-22-2011, 11:20 AM   #5
andrewthomas
Senior Member
 
Registered: May 2010
Location: Chicago Metro
Distribution: Arch, Gentoo, Slackware
Posts: 1,690

Rep: Reputation: 307Reputation: 307Reputation: 307Reputation: 307
Quote:
Originally Posted by manzdagratiano View Post
Aha! Herein lies the culprit - I indeed did build from Slackbuilds.org! Thanks! I would expect that the default behavior would be to disable audacious support.
Yet, if you don't have audacious on your system, the --enable-audacious flag is harmless.

The only reason you encountered a problem was because you removed the program.
 
Old 06-23-2011, 09:54 AM   #6
manzdagratiano
LQ Newbie
 
Registered: Mar 2011
Location: NJ, USA
Distribution: Ubuntu, Arch Linux, Debian Sid, Slackware64-current, Gentoo
Posts: 26

Original Poster
Rep: Reputation: 12
Quote:
Originally Posted by andrewthomas View Post
Yet, if you don't have audacious on your system, the --enable-audacious flag is harmless.

The only reason you encountered a problem was because you removed the program.
The flag would be harmless by itself, but the Slackbuilds.org script lists audacious as a mandatory dependency - it won't compile without it! - I tried building without audacious and it screamed; why on Earth they would do that is beyond me, and maybe I should submit a new script. For the meantime, I just chose to leave audacious installed as opposed to manually downloading and editing the Slackbuild, so that the package could be cleanly managed by sbopkg
 
Old 06-23-2011, 10:36 AM   #7
Daedra
Senior Member
 
Registered: Dec 2005
Location: Springfield, MO
Distribution: Slackware64-14.1
Posts: 1,226

Rep: Reputation: 187Reputation: 187
I maintain the conky script and it may beyond you, but like were saying audacious is standard in the stock Slackware full install, which most people here seem use. Why would I gut a useful feature out of the build script when its easy enough for people who don't need it to just edit the script themselves. It takes maybe an extra two minutes to build it by hand vs. sbopkg. Is it really that inconvenient for you?

Last edited by Daedra; 06-23-2011 at 11:05 AM.
 
Old 06-23-2011, 11:28 AM   #8
abrouwers
Member
 
Registered: May 2005
Location: Michigan
Distribution: Slackware -current
Posts: 98

Rep: Reputation: 37
Quote:
Originally Posted by manzdagratiano View Post
The flag would be harmless by itself, but the Slackbuilds.org script lists audacious as a mandatory dependency - it won't compile without it! - I tried building without audacious and it screamed; why on Earth they would do that is beyond me, and maybe I should submit a new script. For the meantime, I just chose to leave audacious installed as opposed to manually downloading and editing the Slackbuild, so that the package could be cleanly managed by sbopkg
Actually, the problem is that YOU built it against audacious, and then removed the audacious package. Otherwise, your package would not have linked against audacious in the first place. Don't blame the tools :-)
 
Old 06-24-2011, 11:18 AM   #9
manzdagratiano
LQ Newbie
 
Registered: Mar 2011
Location: NJ, USA
Distribution: Ubuntu, Arch Linux, Debian Sid, Slackware64-current, Gentoo
Posts: 26

Original Poster
Rep: Reputation: 12
Quote:
Originally Posted by Daedra View Post
I maintain the conky script and it may beyond you, but like were saying audacious is standard in the stock Slackware full install, which most people here seem use. Why would I gut a useful feature out of the build script when its easy enough for people who don't need it to just edit the script themselves. It takes maybe an extra two minutes to build it by hand vs. sbopkg. Is it really that inconvenient for you?
I apologize if my comment seemed like the `flamewar' type - such was not my intention. I would first commend you for maintaining the script in the first place. What I was trying to elucidate was that I find it unusual that audacious is a mandatory dependency of conky, since it is not necessary for conky to function (why I say `mandatory' is revealed later in the post - please see below). I concede that it is included in the regular Slackware stock build, but whether a person actually chooses to have it on their system is a matter of personal choice. Just to corroborate my point, if you take a look at this thread over in the Arch Linux forums representing a poll of media players, most people use mpd as opposed to audacious, whereas mpd is not a mandatory dependency of conky, though the flag is indeed enabled by default in your script, which detects mpd if it is there and not otherwise. Agreed that mpd is not part of the standard install, but there are tons of packages in Slackbuilds.org that have external dependencies not in the Slackware default install. I am not making this a case to make mpd a dependency - I would just like to ask: why not the same for audacious? Leave the flag enabled, and if the user has it, include the support, else not. Listing it as a mandatory dependency requires modifying the script itself, which though not really inconvenient because it entails editing a few lines of code, is an extra step. If one were to argue that Slackers are 'advanced' enough to deal with that, then one could also say that they are advanced enough to just download the source themselves, and './configure + make + make install' themselves, thereby eliminating the need for the entire Slackbuilds.org repository, which would be a ludicrous statement! But, as I acknowledged, the choice is indeed yours.

Quote:
Originally Posted by abrouwers View Post
Actually, the problem is that YOU built it against audacious, and then removed the audacious package. Otherwise, your package would not have linked against audacious in the first place. Don't blame the tools :-)
To that I can only reply - you did not read my last post carefully. I am not here blaming the tools. I also tried after I purged audacious, and when I purge conky and try reinstalling it via sbopkg, this is what I get:
Code:
checking for Audacious... configure: error: Package requirements (audacious >= 1.4.0 audclient dbus-glib-1 glib-2.0 gobject-2.0) were not met:

No package 'audacious' found
No package 'audclient' found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables Audacious_CFLAGS
and Audacious_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.


conky:
Would you like to continue processing the rest of the
build 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?:
This therefore implies that audacious is listed as a mandatory dependency, and not merely as a flag which is harmless even if enabled in the absence of audacious. Like I said, it doesn't really bother me to either leave audacious installed or build with it explicitly disabled. I was merely pointing out that turning on a package as a mandatory dependency which is not really needed for the functioning of the package being installed is an anomalous choice.
 
Old 06-24-2011, 11:38 AM   #10
Daedra
Senior Member
 
Registered: Dec 2005
Location: Springfield, MO
Distribution: Slackware64-14.1
Posts: 1,226

Rep: Reputation: 187Reputation: 187
I understand what you are saying, I do. But when I submit packages to SBo I submit them with the mindset that the person did a full install, since that is what is generally recommended. If you notice the conky build does have a flag for lua, the reason is because lua does not come with the stock Slackware so enabling it by default would make no sense, but as you know audacious does. Yes it sucks that if you don't have audacious the build will fail, but the vast majority of people will never run into this problem. And the ones who do can just remove the --enable-audacious flag and build it themselves.
 
Old 06-24-2011, 01:23 PM   #11
manzdagratiano
LQ Newbie
 
Registered: Mar 2011
Location: NJ, USA
Distribution: Ubuntu, Arch Linux, Debian Sid, Slackware64-current, Gentoo
Posts: 26

Original Poster
Rep: Reputation: 12
Quote:
Originally Posted by Daedra View Post
I understand what you are saying, I do. But when I submit packages to SBo I submit them with the mindset that the person did a full install, since that is what is generally recommended. If you notice the conky build does have a flag for lua, the reason is because lua does not come with the stock Slackware so enabling it by default would make no sense, but as you know audacious does. Yes it sucks that if you don't have audacious the build will fail, but the vast majority of people will never run into this problem. And the ones who do can just remove the --enable-audacious flag and build it themselves.
Agreed and conceded by all means Good Sir!

Cheers!
 
1 members found this post helpful.
  


Reply

Tags
audacious, conky, library


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
conky question: passing conky-variable to shell-script zlin50 Linux - Software 2 12-29-2012 07:47 PM
Alternative to Audacious for eac cuesheets, midi playback (hardware)? Fix audacious? Holering Linux - Software 0 10-03-2010 12:19 AM
LXer: Conky Colors Makes Your Conky Beautiful In Seconds (Version 3.20 Released) LXer Syndicated Linux News 0 08-01-2010 12:21 PM
LXer: Conky Ubuntu Lucid Theme - Among The Easiest to Install Conky Theme in Ubuntu LXer Syndicated Linux News 0 07-05-2010 05:11 PM
Conky on Suse 10.0 - *** buffer overflow detected *** conky terminated Slidex Linux - Software 1 03-17-2006 12:50 PM


All times are GMT -5. The time now is 06:11 PM.

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
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration