Obviously I didn’t mention this issue enough yet since google didn’t return my blog for this issue as well as I’d like.
Today’s task with a problem: upgrading to Deluge 1.3.0-rc2 from rc1. Just for reference, I ran into this problem before. Since we’re upgrading Deluge, I’m upgrading the torrent library first. The latest version seems to be libtorrent-rasterbar version 0.15.2.
# Some configure junk and then:
Checking for boost libraries:
checking for boostlib >= 1.36... yes
checking whether the Boost::System library is available... yes
configure: error: Boost.System library not found. Try using --with-boost-system=lib
… don’t you just hate it when your computer hints you to try something trivial? (continue reading…)
Yeah, I bet you didn’t know that. You’re so stupid. (continue reading…)
Yesterday I found a release notice in the pulseaudio mailinglist announcing version 0.9.16.
Today, I found another release note in the mailinglist that announced pulseaudio version 0.9.17. Gee, another fuckup? (but that’s part of the release process I guess ;))
Anyway, I decided to upgrade my 0.9.15 installation since it still glitches every now and then. (continue reading…)
After toying around a bit on the news sites I decided it would be interesting to see if qBitTorrent would run on slackware 64.
So we go to the download site, copy the url, and see if Slackbuild likes it. Slackbuild leeches, untars, gives the configure options (which are a bit buggy, I know, will be fixed next release), runs configure. Configure crashes out with “blabla boost blabla”. (continue reading…)
Of course you’re already thrilled by my slackbuild.pl script, but this one thing keeps popping up.
“How do I get configure to get my system paths right without giving it a line that’s 2389472389 arguments long?”
Simple, install a site config.
It’s a tiny little shell script that takes the configure options and barfs out some prefixes and stuff based on the options presented to it.
So when I tell it
prefix=/usr, it will decide that
sysconfdir=/etc instead of
You can get my my version here:
config.site (687 downloads)
Now the important tidbit. In order for configure to automagically use this script, you wil need to set the environment variable CONFIG_SITE.
Personally I do this through a profile file. Download the config.site script, put it in /etc and put the profile file in /etc/profile.d. Logout/login, done.
Oh, here’s the profile file:
config_site.sh (570 downloads)
Now if everything worked out allright, running configure should start with something like this:
configure: loading site script /etc/config.site
Wonderful isn’t it? 🙂