-   Linux - Software (
-   -   Attempting to install xcb 1.4 and other AwesomeWM deps on Slack64 13 (

conartist6 11-09-2009 01:21 AM

Attempting to install xcb 1.4 and other AwesomeWM deps on Slack64 13
I am attempting to install libxcb 1.4 and xcb-utils 0.3.6 on slackware64 13.0. I have been stymied in pretty much every direction I turn so far. No packages exist for these tarballs for slackware at all, much less for slack64. Furthermore there are no slackbuilds scripts for libxcb. At any rate I can at least remove the default libxcb package and compile a replacement, however this creates several problems. Firstly, when I set the prefix flag in the libxcb configure script attempting to make the program results in the message "cannot install `[any file]' to a directory not ending in /usr/local/lib." being shown for every file which should have been copied. Secondly, even in /usr/local/, the program installs libraries to lib instead of lib64. D'oh. Finally this process does not generate a package, and from what I can tell all the other dependencies are checking for the existence of a package instead of just raw library files. I'm not yet sure what problems I'll run into when I try to install xcb-utils, but at least I have a SlackBuild script for that.
So, the question is - what should I do? Do I make install libxcb to a temporary directory and then move all the files around by hand and make a package out of it and install that? Do I symlink files to their appropriate locations from their inappropriate ones and then try to force xcb-utils to acknowledge the files that are there? Is there another way to go about this? I guess I'll try the first, as there's no harm in it, but this is all an immense pain. Any insight appreciated.


Edit: Started playing with building package, however files still made to lib directory instead of lib64 -- are these 64 bit libraries which are just named incorrectly? Will I be destroying the program's linking by moving its files around relative to one another? What a mess.

Edit: The poster is incredibly surprised to find that everything is working... So far. configure is satisfied, but who knows if the actual files are even vaguely what they should be... I don't.

Edit: Close to knowing whether my inital hackery did any more than fool the computer into thinking that deps were satisfied. In the mean time Awesome's make still wants
-- package 'libstartup-notification-1.0>=0.10' not found
-- package 'libxdg-basedir>=1.0.0' not found
Both of which should be installed that this point... :/
What to do? (note: the libstartup-notification is now simply known as startup-notification, however the library name is the same. Maybe this is where I symlink in a new name in /etc/packages/?) (note2: I can probably figure out what is happening with libxdg-basedir) (note3: I really need to go to bed and stop messing with this)

brianL 11-09-2009 04:24 AM

Why not try the Awesome SlackBuild?

conartist6 11-09-2009 01:35 PM


Originally Posted by brianL (Post 3750043)

Sorry, I should have specified, I'd like to install the newest revision of Awesome. That SlackBuild is a major revision old, and doesn't reflect the current structure of Awesome's installer. In any case it doesn't handle deps. There IS a slackbuild for Awesome 3 that works, but with the make script not finding the proper deps it isn't very helpful... Any other answers to the basic questions I asked above?

conartist6 11-09-2009 05:00 PM

Libxdg-basedir problem solved by moving /usr/lib files to /usr/lib64 before makepkg was run. Libstartupnotification problem found to be user error. .10 is the most recent version, but I was reading that as .010. Packaged and installed most recent to fill dep. Now installing ev (unlisted dep)

Elv13 11-09-2009 05:49 PM

Welcome to the awesome world of awesome, the software with API chaging every 3 millisecond and always requiring to compile the latest SVN build of x11proto and libxkb, but the result is so awesome ;)

conartist6 11-09-2009 06:32 PM

Awesome is installed! Now on to configuration... and learning lua! Ran across one last problem - awesome complained about missing fbdev module on installation, quickly fixed with installation of NVIDIA drivers which I had been too lazy to do as of yet. I posted a tarball with all the required packages to my website. (Only missing file is rc.lua, which should be placed in $HOME/.config/awesome (or there are a few other dirs that work as well))Get it here (If you trust me with you system's well being, that is...) That will be all for now. Good luck to any others trying to do this.

Elv13 11-09-2009 10:25 PM

If you have question, remember to ask in #awesome at or send me a personal message, I have used most modules and know them well.

I suggest to switch to shifty module early in your configuration if you want dynamic tagging and "easy" apps management, it is much harder to add it later on.

All times are GMT -5. The time now is 01:21 AM.