| Git Clone URL: | https://aur.archlinux.org/compiz.git (read-only, click to copy) |
|---|---|
| Package Base: | compiz |
| Description: | Composite manager for Aiglx and Xgl, with plugins and CCSM |
| Upstream URL: | https://launchpad.net/compiz |
| Keywords: | ccsm |
| Licenses: | MIT, GPL-2.0-or-later, LGPL-2.1-or-later |
| Conflicts: | ccsm, compiz-bcop, compiz-core, compiz-fusion-plugins-experimental, compiz-fusion-plugins-extra, compiz-fusion-plugins-main, compiz-gtk, compizconfig-python, libcompizconfig, simple-ccsm |
| Provides: | ccsm, compiz-bcop, compiz-core, compiz-plugins-extra, compiz-plugins-main, compizconfig-python, libcompizconfig |
| Submitter: | None |
| Maintainer: | xiota |
| Last Packager: | xiota |
| Votes: | 165 |
| Popularity: | 0.46 |
| First Submitted: | 2014-08-04 13:22 (UTC) |
| Last Updated: | 2024-03-24 22:06 (UTC) |
@Chazza I just have a little problem... there's some documentation about what exactly means and how to "rebuild the package"? I've also tried uninstalling, cleaning cache and reinstalling but I get the same error, and even the sim-link doesn't helps because I get exactly the same error and the same "undefined symbol" string of @GaylairdCulbreth.
Thanks in advance and I hope you can help me, I'm a little newbie in the Arch World.
@Sebversive If you run an executable linked against shared libaries in the terminal, and any of those links are broken (i.e. /usr/bin/compiz is linked against libfoo.so.5 but libfoo got updated to libfoo.so.6) then you will get a message in the terminal saying something along the lines of:
shared object libfoo.so.5 could not be found.
And at that point you know you need to rebuild the package that provides that executable (in this case compiz). So this problem only occurs if the version number of a shared object file changes.
Some AUR maintainers will bump the pkgrel of their AUR packages every time there's a shared library that gets its version updated and then people that use AUR helpers like yaourt will have a rebuild triggered when they run their helper. I'm afraid I don't do this for compiz though, mainly because I don't use compiz any more so I don't know when the shared library versions change. I only build compiz and run it when there's an update or when there are issues reported here. I have previously stated - and will state again - that if anyone is unhappy with this, I am more than happy to hand over maintenance of compiz to someone else. Just send me an email.
With all that being said about AUR helpers, I would advise staying away from them anyhow, at least until you're completely familiar with how the AUR and building packages work.
Hope this helps
@Chazza; are you telling me I'm supposed to keep an eye on every single dependency my AUR packages have and notice myself if an AUR package needs rebuilding??
@Sebversive compiz builds fine here. No idea why your build failed on at 34%. And yes, compiz (and all AUR packages in general) need to be rebuilt when dependencies that they're linked against get updated.
Updated my system (last time was 10 days ago) and compiz is broken, doesn't run anymore. Now I tried to reinstall compiz and I get this:
[ 34%] Building CXX object plugins/expo/CMakeFiles/expo.dir/src/expo.cpp.o make[2]: No rule to make target '../plugins/expo/src/glow.cpp', needed by 'plugins/expo/CMakeFiles/expo.dir/src/glow.cpp.o'. Stop. make[1]: [CMakeFiles/Makefile2:9756: plugins/expo/CMakeFiles/expo.dir/all] Error 2 make: *** [Makefile:163: all] Error 2 ==> ERROR: A failure occurred in build(). Aborting...
Any idea?
Edit: replaced compiz with compiz-git -> everything back to normal..
@ector, once I'm in front of my Arch machine I'll update this package to add the fix from upstream.
Edit: done.
Thanks for info @chazza. But can I update or I have to wait for new version compiz? I saw that in ubuntu it was fixed. at the moment I downgraded compiz. Cheers
Great! Thanks alot muktupavels
Pinned Comments
<deleted-account> commented on 2018-09-14 14:00 (UTC)
When library names like libprotobuf.so.XX change you just need to rebuild compiz. It's not a problem with the PKGBUILD. This is normal for AUR packages. Packages in the official repos also get rebuilt when libraries are updated.
Note that you shouldn't symlink new library names to old. This will create problems for you further down the line.