Running openbox on slack 12.1
Has anyone compiled and ran openbox one 12.1?
I just installed 12.1, with xfce and fluxbox, and wanted to go to my old favorite, openbox. I downloaded openbox 3.4.7.2, untared, configured, made, and make installed. Running openbox gives me the error openbox: error while loading shared libraries: libobrender.so.21: cannot open shared object file: No such file or directory Any help? I'm on a fresh, clean installation, so I haven't changed anything yet about the slackware installation. I remember running openbox on 12.0 last year, but I have been away from my dear linux for a while. Thanks! |
One of the two main points there is impossible.
Either 1) you didn't compile openbox on your system, or 2) it's not a fresh clean installation. |
Hahaha. Can't trick you, rworkman. You're right. It's fresh EXCEPT for my compilation and installation of openbox. That must be my problem right there! =P
|
There is an openbox slackbuild at SlackBuilds.org BTW. Obconf is there as well. I can confirm both work as expected on 12.1.
|
I may end up resorting to that, but I would rather fix this problem. It feels like my system is in some way broken if I can not compile openbox and use it myself. Nothing against packages, and I probably would have gotten the package had I thought of it first, but now that I know there is a problem I have a need to fix it rather than work around it. And if a new version comes out with features that I would like, I would like to be able to compile that myself.
Any ideas? |
Well, there is no openbox package at SlackBuilds.org, of course. SlackBuilds.org contains slackbuild scripts that you use to compile your own package for your own system that you can easily upgrade later on with upgradepkg. It's just like compiling only better. :-) It's the same way PV makes official Slackware packages. And since I'm the maintainer of the openbox and obconf SlackBuilds at SlackBuilds.org, they are updated with each new upstream release. Check out the HOWTO and the FAQ at SlackBuilds.org. I know this still doesn't answer your question, but I just wanted to touch on that.
Did you do a _full_ Slackware fresh install before compiling Openbox? |
Oh, okay. I thought slackbuilds was a slackware package site. Did you have to do anything special to get openbox to build when creating your slackbuild?
I went through all the menus, but the only things that I excluded were a few kde applications like koffice and such, games, and the other windowmanagers besides xfce and fluxbox. |
If I build using the slackbuild I get this error when running openbox:
Openbox-Message: Failed to open the display from the DISPLAY environment variable. |
Quote:
openbox: http://slackbuilds.org/slackbuilds/1...box.SlackBuild obconf: http://slackbuilds.org/slackbuilds/1...onf.SlackBuild To actually build the package using the SlackBuilds, you'll need the other files included with the SlackBuild -- they're all in the .tar.gz package linked to at the page for each SlackBuild (search slackbuilds.org for openbox and obconf). Quote:
Quote:
If that IS what you are doing, make sure no other X sessions are running. Are you using runlevel 3 or 4? You can *try* launching it with `startx -- :0` but I can almost guarantee that won't work. |
Alright...
If I build with the slackbuild and use the xinitrc included, it now runs. Thank you. If I build from source myself and use the same xinitrc, it has the error I posted in the first post of this thread. So my original problem is not solved, but I do have a working openbox. I don't think that the lack of a couple of optional kde packages broke some sort of openbox dependency, though. |
Quote:
Code:
chown -R root:root . Code:
CFLAGS="$SLKCFLAGS" \ Code:
make Code:
( cd $PKG Code:
( cd $PKG/usr/man Code:
install -D -m 0755 $CWD/xinitrc.openbox $PKG/etc/X11/xinit/xinitrc.openbox Code:
# Optionally install xinitrc scripts for running Openbox in KDE or GNOME If you perform the necessary steps outlined above (note that binary-stripping and compressing the man pages are probably not *required*, but are good form), you should create a functional openbox build. If you didn't specify a DESTDIR variable, it will be difficult to upgrade/remove openbox, but it should still work. I would still encourage creating packages. For more information about writing SlackBuilds (my favourite compilation method, but even if you don't write SlackBuilds and want to type the commands manually without creating a package it'll still help to read the following) see here: http://slackwiki.org/Writing_A_SlackBuild_Script The bottom line is that if you could create a working openbox package using the SlackBuild, your system isn't broken. There is no "magic" in this SlackBuild (some SlackBuilds for other apps need to have strange configuration options or odd commands to get stuff to work), so I can't see why a manual build wouldn't work properly if done right. |
I was not supplying any options to ./configure. Why is it necessary to change those directories? Why are the defaults not the correct ones for slackware 12.1?
|
Quote:
Sometimes it doesn't matter so much, but sometimes other programs/libraries are expected to be in a certain place, so it can matter a lot. It's best to be consistent. |
So in slackware is it best to always define the prefix as /usr?
|
Quote:
|
All times are GMT -5. The time now is 10:59 AM. |