Linux From ScratchThis Forum is for the discussion of LFS.
LFS is a project that provides you with the steps necessary to build your own custom Linux system.
Notices
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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Some time ago I investigated compiz and upon discovering that it required gtk3, despite what I had been told by several people, I abandoned the project.
While looking through the www.x.org website, I discovered that, at some point around 2008, compiz had been absorbed into the xorg project. Oh, wow.
Based on the fact that just about everything I'd compiled from that site compiled easily, I grabbed their version of compiz.
Not having kde nor gnome decided some of the options I used in the above.
So far, this was going better than any previous attempts. Had it required gtk3, the configure would have balked, right?
Naturally there was going to be a problem. I saw that coming. In the past, I could not get compiz to work on Debian, slackware, nor gentoo. Naturally it was going to fail here. This time around, for this version, the problem was in the make phase. Here are the last few lines of the make phase:
Distribution: Void, Linux From Scratch, Slackware64
Posts: 3,157
Rep:
Have come across this problem a few times when packages have been transitioning, you just have to manually add the lib to link in the configure flags ( LDFLAGS or possibly CPPFLAGS ) eg:
Code:
LDFLAGS="-lXext" ./configure ...
The problem is caused by the linker not automaticly adding need libs to the link stage like it used to.
Last edited by Keith Hedger; 07-31-2018 at 10:12 AM.
Reason: wish i culd tpye
The LDFLAGS parameter, as you had it, worked fine. Compiz compiled all the way without further problems. Thank you very much.
Now I realize that -l is used to link in libraries. For example, some of my programs require a "-lm" to link in some floating point math subroutines. but how did you know that "Xext" was what was needed?
Now that Compiz is installed, it doesn't seem to do anything. The usual technique of putting "compiz" in the .xinitrc, instead of my regular window manager, doesn't seem to work. All I get is a pointer. Clicking does nothing.
And the package didn't put in a man page. My suspicions are raised. Maybe this is the wrong compiz. I remember there is one version adds nothing but a compositing manager. Or maybe xorg has got the core and not the plugins? This is a 0.7 version and a quick check on slackbuilds.org has them using a 0.8 version that is more than one package.
Did some trial and error with compiz. While in my regular window manager (blackbox if it makes a difference) I ran compiz from a terminal. The error message said:
Code:
compiz (core) - Error: Another window manager is already running on screen: 0
compiz (core) - Fatal: No manageable screens found on display :1.0
Good in that this version of the compiz package *is* supposed to be a window manager, not a simple compositing plugin.
After exiting back to the console, I then modified .xinitrc to call compiz. This time I had two ideas. One, guess the names of some plugins and pass that as parameters. Two, put a redirection in the compiz call in .xinitrc
Code:
compiz cube wobbly emerald
the result as that, upon "startx" I once again had a mouse pointer whose clicking did nothing, and I had to do some keyboard mashing to eventually, as before, get xorg to crash back to the console. The logged output of the compiz was:
The term ran and did accept keyboard input. It had no titlebar and could not be moved nor resized.
Theory one: compiz needs to be told to call a plugin to manage window decorations.
Theory two: the xorg version of compiz is horribly broken and I am wasting my time.
Related to theory two, the x.org version is 0.7, the slackbuild.org version is 0.8, and there is apparently a 0.9.
p.s. I've actually been failing to get compiz to run across multiple distros over ten years. I begin to wonder if every compiz screenshot I see is actually a photoshop.
Last edited by jr_bob_dobbs; 08-01-2018 at 07:23 PM.
uninstalled compiz. Doing everything through a package manager makes that clean and easy.
Grabbed the 0.8 version of compiz, using slackbuilds.org for links and for order of compilation. Installed the parts that will compile without gtk3. Ran it. Exact same behavior as before.
My reading indicated that a program called ccsm should be run on first run of compiz. I guess to specify settings. Maybe that would help. Since I'd set up my .xinitrc to start a term up as it starts compiz, I at least had a command line to enter commands.
Code:
Traceback (most recent call last):
File "/usr/bin/ccsm", line 23, in <module>
import gi
ImportError: No module named gi
The official compiz site says that when one has windows with no borders, one can kludge by alt-dragging. Nope.
The official compiz site says there there is a forum where one can help. The last post on said forum was 2011.
There are, depending on how one wants to apply various criteria, up to five "current" versions of compiz.
The Emerald window decorator plugin for compiz, despite itself predating gtk3 (and also gtk2?) by several years, requires gtk3.
*gold clap*.
At this point, this thread serves no purpose, aside from warning others to not even bother with compiz, and can be locked, or at least left to drift to obscurity.
Last edited by jr_bob_dobbs; 08-04-2018 at 11:36 AM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.