SlackwareThis Forum is for the discussion of Slackware Linux.
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.
I was so taken with the purty "basic black" screenshots of CrunchBang Linux I decided "well, I'll get the SlackBuilds of both openbox and conky and make my own." Openbox set up fine, and it was my first experience running sbopkg, which is a great program.
However, conky failed to build. For some reason the right edge of the error messages was cut off in the sbopkg window, but there was enough to guess the drift: something having to do with audacious and libmcs was not present, or not present in a recent enough version.
I tried building the package from the CL later, and got the same errors, only here more readable:
"checking for Audacious... configure: error: Package requirements (audacious >= 1.4.0 dbus-glib-1 glib-2.0 gobject-2.0) were not met:
Package 'Audacious' requires 'libmcs >= 0.7' but version of libmcs is 0.4.1
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."
For what it is worth, I am also getting a segfault when I try to launch audacious from the command line.
I'm guessing audacious or just the library needs upgradin', but I don't know why slackpkg wouldn't have alerted me to that. If anyone has any ideas, I would appreciate any pointers. I am going to try removing and reinstalling audacious.
Hi -- if you have KEEPLOG=yes in your /etc/sbopkg/sbopkg.conf file, then the build process will be retained in a permanent log. See the sbopkg.conf(5) man page for details. The next release of sbopkg will allow you to set the actual log file name and location.