Progress on Unity under Arch Linux!

chenxiaolong · 2012-04-04 03:44:19

Update notes for the April 3rd round of updates:

1. The following packages are needed from the testing repo (or wait until GNOME 3.4 lands in extra):
* libwacom
* vala
* networkmanager

They can be downloaded from https://packages.archlinux.org. Just select your CPU architecture, select 'testing' for the repository, and search for the three packages. The download link will be on the right sidebar ("Download from mirror"). If you're like me and love to use the command line, the packages can be downloaded with:

wget --content-disposition 'https://www.archlinux.org/packages/testing/CPUARCH/PACKAGE/download/'

2. Unity fails to compile with the new GCC 4.7.0. I've filed a bug report here: https://bugs.launchpad.net/unity/+bug/973016 If anyone knows how to fix it, please post a patch at the Launchpad bug report so it can be included upstream.

naxan · 2012-04-04 22:22:21

Great work, as usual! I am seeing two issues, however, one of which I have a solution for and one I don't.

Firstly, qt-ubuntu won't compile out of the box for me. The problem seems to be in WebKit, which is throwing an error about _GMutex. However, by following the the instruction in comments #1 and #2 at https://bugs.webkit.org/show_bug.cgi?id=72085 and deleting the corresponding lines in kubuntu_01_fix_build_glib_231.diff I was able to get it to compile. (Still need to temporarily remove qtwebkit every time, but such is the price of living on the edge, no?)

Secondly, lightdm-unity-greeter (from Unity-for-Arch-Extra) won't compile for me. I'm trying to upgrade it dead last (so all of the other updates from today have been applied already), but always see the following:

==> Making package: lightdm-unity-greeter 0.2.7.0ubuntu1-100 (Wed Apr  4 16:07:22 MDT 2012)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving Sources...
  -> Found unity-greeter_0.2.7-0ubuntu1.debian.tar.gz
  -> Found unity-greeter_0.2.7.orig.tar.gz
==> Validating source files with sha512sums...
    unity-greeter_0.2.7-0ubuntu1.debian.tar.gz ... Passed
    unity-greeter_0.2.7.orig.tar.gz ... Passed
==> Extracting Sources...
  -> Extracting unity-greeter_0.2.7-0ubuntu1.debian.tar.gz with bsdtar
  -> Extracting unity-greeter_0.2.7.orig.tar.gz with bsdtar
==> Starting build()...
patching file src/unity-greeter.vala
Hunk #1 succeeded at 878 (offset 458 lines).
autoreconf: Entering directory `.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: aclocal --force 
autoreconf: configure.ac: tracing
autoreconf: configure.ac: not using Libtool
autoreconf: running: /usr/bin/autoconf --force
autoreconf: running: /usr/bin/autoheader --force
autoreconf: running: automake --add-missing --copy --force-missing
autoreconf: Leaving directory `.'
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for style of include used by make... GNU
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking dependency style of gcc... gcc3
checking whether gcc and cc understand -c and -o together... yes
checking for valac-0.16... /usr/bin/valac-0.16
checking /usr/bin/valac-0.16 is at least version 0.15.1... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking whether make supports nested variables... yes
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.16... yes
checking whether gcc understands -Wno-sign-compare... yes
checking what warning flags to pass to the C compiler... -Wall -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-sign-compare
checking what language compliance flags to pass to the C compiler... 
checking for UNITY_GREETER... yes
checking whether NLS is requested... yes
checking for intltool >= 0.35.0... 0.50.2 found
checking for intltool-update... /usr/bin/intltool-update
checking for intltool-merge... /usr/bin/intltool-merge
checking for intltool-extract... /usr/bin/intltool-extract
checking for xgettext... /usr/bin/xgettext
checking for msgmerge... /usr/bin/msgmerge
checking for msgfmt... /usr/bin/msgfmt
checking for gmsgfmt... /usr/bin/msgfmt
checking for perl... /usr/bin/perl
checking for perl >= 5.8.1... 5.14.2
checking for XML::Parser... ok
configure: creating ./config.status
config.status: creating Makefile
config.status: creating data/Makefile
config.status: creating po/Makefile.in
config.status: creating src/Makefile
config.status: creating config.h
config.status: executing depfiles commands
config.status: executing po/stamp-it commands
make  all-recursive
make[1]: Entering directory `/tmp/lightdm-unity-greeter/src/unity-greeter-0.2.7'
Making all in data
make[2]: Entering directory `/tmp/lightdm-unity-greeter/src/unity-greeter-0.2.7/data'
  GEN    com.canonical.unity-greeter.gschema.valid
make[2]: Leaving directory `/tmp/lightdm-unity-greeter/src/unity-greeter-0.2.7/data'
Making all in po
make[2]: Entering directory `/tmp/lightdm-unity-greeter/src/unity-greeter-0.2.7/po'
  MSGFMT af.gmo
  MSGFMT am.gmo
  MSGFMT an.gmo
  MSGFMT ar.gmo
  MSGFMT ast.gmo
  MSGFMT az.gmo
  MSGFMT bem.gmo
  MSGFMT be.gmo
  MSGFMT bg.gmo
  MSGFMT bn.gmo
  MSGFMT bo.gmo
  MSGFMT br.gmo
  MSGFMT bs.gmo
  MSGFMT ca.gmo
  MSGFMT ca@valencia.gmo
  MSGFMT cs.gmo
  MSGFMT cy.gmo
  MSGFMT da.gmo
  MSGFMT de.gmo
  MSGFMT el.gmo
  MSGFMT en_AU.gmo
  MSGFMT en_CA.gmo
  MSGFMT en_GB.gmo
  MSGFMT eo.gmo
  MSGFMT es.gmo
  MSGFMT et.gmo
  MSGFMT eu.gmo
  MSGFMT fa.gmo
  MSGFMT fil.gmo
  MSGFMT fi.gmo
  MSGFMT fo.gmo
  MSGFMT fr.gmo
  MSGFMT fy.gmo
  MSGFMT ga.gmo
  MSGFMT gd.gmo
  MSGFMT gl.gmo
  MSGFMT gu.gmo
  MSGFMT he.gmo
  MSGFMT hi.gmo
  MSGFMT hr.gmo
  MSGFMT ht.gmo
  MSGFMT hu.gmo
  MSGFMT id.gmo
  MSGFMT it.gmo
  MSGFMT ja.gmo
  MSGFMT ka.gmo
  MSGFMT kk.gmo
  MSGFMT kl.gmo
  MSGFMT km.gmo
  MSGFMT ko.gmo
  MSGFMT ku.gmo
  MSGFMT ky.gmo
  MSGFMT lb.gmo
  MSGFMT lt.gmo
  MSGFMT lv.gmo
  MSGFMT mg.gmo
  MSGFMT mhr.gmo
  MSGFMT ml.gmo
  MSGFMT ms.gmo
  MSGFMT my.gmo
  MSGFMT nb.gmo
  MSGFMT nl.gmo
  MSGFMT nn.gmo
  MSGFMT oc.gmo
  MSGFMT pa.gmo
  MSGFMT pl.gmo
  MSGFMT ps.gmo
  MSGFMT pt_BR.gmo
  MSGFMT pt.gmo
  MSGFMT ro.gmo
  MSGFMT ru.gmo
  MSGFMT sd.gmo
  MSGFMT shn.gmo
  MSGFMT si.gmo
  MSGFMT sk.gmo
  MSGFMT sl.gmo
  MSGFMT sq.gmo
  MSGFMT sr.gmo
  MSGFMT sv.gmo
  MSGFMT ta.gmo
  MSGFMT te.gmo
  MSGFMT th.gmo
  MSGFMT ti.gmo
  MSGFMT tr.gmo
  MSGFMT ug.gmo
  MSGFMT uk.gmo
  MSGFMT uz.gmo
  MSGFMT vi.gmo
  MSGFMT wae.gmo
  MSGFMT zh_CN.gmo
  MSGFMT zh_HK.gmo
  MSGFMT zh_TW.gmo
make[2]: Leaving directory `/tmp/lightdm-unity-greeter/src/unity-greeter-0.2.7/po'
Making all in src
make[2]: Entering directory `/tmp/lightdm-unity-greeter/src/unity-greeter-0.2.7/src'
  VALAC  unity_greeter_vala.stamp
menubar.vala:23.20-23.28: error: The symbol `Indicator' could not be found
    public unowned Indicator.ObjectEntry entry;
                   ^^^^^^^^^
menubar.vala:26.31-26.39: error: The symbol `Indicator' could not be found
    public IndicatorMenuItem (Indicator.ObjectEntry entry)
                              ^^^^^^^^^
menubar.vala:119.18-119.26: error: The symbol `Indicator' could not be found
    private List<Indicator.Object> indicator_objects;
                 ^^^^^^^^^
menubar.vala:466.39-466.47: error: The symbol `Indicator' could not be found
    private uint get_indicator_index (Indicator.Object object)
                                      ^^^^^^^^^
menubar.vala:480.13-480.21: error: The symbol `Indicator' could not be found
    private Indicator.Object? get_indicator_object_from_entry (Indicator.ObjectEntry entry)
            ^^^^^^^^^
menubar.vala:480.64-480.72: error: The symbol `Indicator' could not be found
    private Indicator.Object? get_indicator_object_from_entry (Indicator.ObjectEntry entry)
                                                               ^^^^^^^^^
menubar.vala:494.38-494.46: error: The symbol `Indicator' could not be found
    private void indicator_added_cb (Indicator.Object object, Indicator.ObjectEntry entry)
                                     ^^^^^^^^^
menubar.vala:494.63-494.71: error: The symbol `Indicator' could not be found
    private void indicator_added_cb (Indicator.Object object, Indicator.ObjectEntry entry)
                                                              ^^^^^^^^^
menubar.vala:517.40-517.48: error: The symbol `Indicator' could not be found
    private void indicator_removed_cb (Indicator.Object object, Indicator.ObjectEntry entry)
                                       ^^^^^^^^^
menubar.vala:517.65-517.73: error: The symbol `Indicator' could not be found
    private void indicator_removed_cb (Indicator.Object object, Indicator.ObjectEntry entry)
                                                                ^^^^^^^^^
Compilation failed: 10 error(s), 0 warning(s)
make[2]: *** [unity_greeter_vala.stamp] Error 1
make[2]: Leaving directory `/tmp/lightdm-unity-greeter/src/unity-greeter-0.2.7/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/tmp/lightdm-unity-greeter/src/unity-greeter-0.2.7'
make: *** [all] Error 2
==> ERROR: A failure occurred in build().
    Aborting...

I have no idea what's going on here. I noticed that the vapi files for all of the packages in Unity-for-Arch are getting installed in /usr/share/vala/vapi, while everything else is finding its way into /usr/share/vala-0.16/vapi, but I'm not even sure if I'm on the right trail, and I've been unable to figure out how to modify the VALAFLAGS used during compilation to test this hypothesis.

chenxiaolong · 2012-04-05 04:44:16

naxan wrote:

Great work, as usual! I am seeing two issues, however, one of which I have a solution for and one I don't.
Firstly, qt-ubuntu won't compile out of the box for me. The problem seems to be in WebKit, which is throwing an error about _GMutex. However, by following the the instruction in comments #1 and #2 at https://bugs.webkit.org/show_bug.cgi?id=72085 and deleting the corresponding lines in kubuntu_01_fix_build_glib_231.diff I was able to get it to compile. (Still need to temporarily remove qtwebkit every time, but such is the price of living on the edge, no?)

Thanks for the info! I'll fix it as soon I as get rid of the burn mark on my desk from compiling so much...just kidding

naxan wrote:

Secondly, lightdm-unity-greeter (from Unity-for-Arch-Extra) won't compile for me. I'm trying to upgrade it dead last (so all of the other updates from today have been applied already), but always see the following:
lightdm-unity-greeter build output
I have no idea what's going on here. I noticed that the vapi files for all of the packages in Unity-for-Arch are getting installed in /usr/share/vala/vapi, while everything else is finding its way into /usr/share/vala-0.16/vapi, but I'm not even sure if I'm on the right trail, and I've been unable to figure out how to modify the VALAFLAGS used during compilation to test this hypothesis.

Actually, I think /usr/share/vala/vapi is the correct directory. If you check which package owns the files in /usr/share/vala-0.16/vapi with:

pacman -Qo /usr/share/vala-0.16/vapi/* | awk '{print $(NF-1)" "$NF}' | sort | uniq

you'll see that vala owns all the files. Anyway, the error looks like libindicate didn't get installed properly. Could you run:

pacman -Qo /usr/share/vala/vapi/Indicate-0.7.vapi

or maybe try recompiling libindicate?

Trym · 2012-04-05 12:49:53

chenxiaolong wrote:

Unfortunately, I don't have a script, like jhbuild, that can compile everything automatically . The What Can I Update?.py script just checks if there are updates after the initial install of all the packages.
As for the VirtualBox issue, you'll probably need to log in to another session first to install the guest additions for 3D acceleration. If it still fails, could you post the ~/.xsession-errors file from the virtual machine while it's at the blue screen?

Ah, now the filename makes sense. I thought it was an automated script that was going to update Arch with the files for Unity. I already have the guest additions installed. The blue screen was the Gnome desktop, just the plain blue colour, not the wallpaper, with the cursor as an X. No login screen. I'll have another go at it but some files were missing when I tried previously such as gt-ubuntu.

Last edited by Trym (2012-04-05 12:50:14)

naxan · 2012-04-05 12:56:03

You're right, everything in /usr/share/vala-0.16/vapi is owned by vala 0.16.0-1. I think libindicate is installed fine though...

pacman -Qo /usr/share/vala/vapi/Indicate-0.7.vapi

returns

/usr/share/vala/vapi/Indicate-0.7.vapi is owned by libindicate 0.6.92-100

which looks right to me. I tried recompiling and reinstalling libindicate just in case, but nothing changes (either on my system, or in the build of lightdm-unity-greater) that I can see. Still get the same error.

BTW, looks like libindicate should have perl-xml-libxml added to its makedepends array.

chenxiaolong · 2012-04-05 17:47:11

Trym wrote:

chenxiaolong wrote:
Unfortunately, I don't have a script, like jhbuild, that can compile everything automatically . The What Can I Update?.py script just checks if there are updates after the initial install of all the packages.
As for the VirtualBox issue, you'll probably need to log in to another session first to install the guest additions for 3D acceleration. If it still fails, could you post the ~/.xsession-errors file from the virtual machine while it's at the blue screen?
Ah, now the filename makes sense. I thought it was an automated script that was going to update Arch with the files for Unity. I already have the guest additions installed. The blue screen was the Gnome desktop, just the plain blue colour, not the wallpaper, with the cursor as an X. No login screen. I'll have another go at it but some files were missing when I tried previously such as gt-ubuntu.

Hmm...are you able to login to a GNOME session then? I thought the background was blue. If there's no background at all, then gnome-settings-daemon is failing somewhere (it handles mouse cursors, background, and other GNOME settings). If there are still missing files or dependencies, please file a bug at https://github.com/chenxiaolong/Unity-for-Arch/issues or https://bugs.launchpad.net/unity-for-arch

chenxiaolong · 2012-04-05 17:58:45

naxan wrote:

You're right, everything in /usr/share/vala-0.16/vapi is owned by vala 0.16.0-1. I think libindicate is installed fine though...
pacman -Qo /usr/share/vala/vapi/Indicate-0.7.vapi
returns
/usr/share/vala/vapi/Indicate-0.7.vapi is owned by libindicate 0.6.92-100
which looks right to me. I tried recompiling and reinstalling libindicate just in case, but nothing changes (either on my system, or in the build of lightdm-unity-greater) that I can see. Still get the same error.
BTW, looks like libindicate should have perl-xml-libxml added to its makedepends array.

Thanks, I've added perl-xml-libxml to the makedepends array Could you try compiling lightdm-unity-greeter again after today's round of updates? If it still fails could you tar your lightdm-unity-greeter build directory and upload it somewhere?

naxan · 2012-04-05 22:09:07

Still seeing the same failure with lightdm-unity-greater. I've tar'd up the directory and uploaded it to http://www.ecopunk.info/f/lightdm-unity … 405.tar.xz.

Another unrelated tweak: The bamf PKGBUILD should have gtk-doc in the makedepends array.

chenxiaolong · 2012-04-06 01:06:25

naxan wrote:

Still seeing the same failure with lightdm-unity-greater. I've tar'd up the directory and uploaded it to http://www.ecopunk.info/f/lightdm-unity … 405.tar.xz.
Another unrelated tweak: The bamf PKGBUILD should have gtk-doc in the makedepends array.

Darn, autotools doesn't like to keep logs like CMake. What is stored in the VALAFLAGS AM_VALAFLAGS variable on your system? Could you try building with the following command?

VALAFLAGS="--vapidir=/usr/share/vala/vapi" makepkg

jgreen1tc · 2012-04-06 18:13:38

Directory of Engineering, Ubuntu does an AMA

An interesting read, although slightly off topic (didn't know if it warranted its own thread. sorry if this is hijacking).

chenxiaolong · 2012-04-06 19:19:18

jgreen1tc wrote:

Directory of Engineering, Ubuntu does an AMA
An interesting read, although slightly off topic (didn't know if it warranted its own thread. sorry if this is hijacking).

Thanks for the link! It was a very interesting read

naxan · 2012-04-06 20:03:53

Unfortunately

VALAFLAGS="--vapidir=/usr/share/vala/vapi" makepkg

doesn't seem to change anything. I've also tried adding the VALAFLAGS line below the CFLAGS line in the PKGBUILD, but that doesn't help either.

Is anyone else having problems building the latest version of lightdm-unity-greeter, or am I the only one? If other folks are also experiencing issues, we should try to figure out if there's any commonalities in our system setups...

naxan · 2012-04-08 08:13:07

Just in case anyone is having the same problems compiling lightdm-unity-greeter as I am, I've managed to identify a solution that involves patching src/Makefile.am. While working on this, I've begun to suspect that the problem is actually with the vala-0.16.0-1 package, and not with any of the packages chenxiaolong has provided... However, my limited knowledge of coding really prevents me from saying for sure. If anyone with more skills than I wants to investigate, there may be a bug here to file with the Arch devs, or perhaps even with the Vala devs directly.

In any event, the patch that allows lightdm-unity-greater to compile is at https://github.com/chenxiaolong/Unity-f … a/issues/2.

I've created a second patch at https://github.com/chenxiaolong/Unity-f … a/issues/3 that modifies the PKGBUILD to apply the first patch, and also bumps the version of lightdm-unity-greeter to 0.2.7.0ubuntu2.

Hopefully chenxiaolong, and anyone who might be experiencing similar issues, will find this info helpful.

chenxiaolong · 2012-04-08 16:17:21

naxan wrote:

Just in case anyone is having the same problems compiling lightdm-unity-greeter as I am, I've managed to identify a solution that involves patching src/Makefile.am. While working on this, I've begun to suspect that the problem is actually with the vala-0.16.0-1 package, and not with any of the packages chenxiaolong has provided... However, my limited knowledge of coding really prevents me from saying for sure. If anyone with more skills than I wants to investigate, there may be a bug here to file with the Arch devs, or perhaps even with the Vala devs directly.
In any event, the patch that allows lightdm-unity-greater to compile is at https://github.com/chenxiaolong/Unity-f … a/issues/2.
I've created a second patch at https://github.com/chenxiaolong/Unity-f … a/issues/3 that modifies the PKGBUILD to apply the first patch, and also bumps the version of lightdm-unity-greeter to 0.2.7.0ubuntu2.
Hopefully chenxiaolong, and anyone who might be experiencing similar issues, will find this info helpful.

Thank you very much for the patch! I've incorporated it into the latest update for lightdm-unity-greeter.

I'm also thinking that vala is the cause of the issue. Back when GNOME 3.0 was released, I tried to compile something (I think pulseaudio). Arch Linux's vala was 0.0.1 versions older than the latest version and the build failed. vala-git was too new and the build failed

Last edited by chenxiaolong (2012-04-08 16:18:13)

\〠/ · 2012-04-09 11:14:28

Is it still fail to compile with gcc 4.7.0?

chenxiaolong · 2012-04-09 17:16:17

\〠/ wrote:

Is it still fail to compile with gcc 4.7.0?

Only Unity fails to compile right now. However, if you compiled Unity when Arch Linux was still using gcc 4.6.0, it will continue to work.

chenxiaolong · 2012-04-20 05:06:16

Sorry everyone, I won't be able to update the Unity packages for a while. My Lenovo W520 somehow screwed up its UEFI EEPROM chip, so I need to get its motherboard replaced

EDIT 2: WARNING: Do not perform the steps below. AGAIN, do NOT perform the steps below. The half-GNOME 3.2 and half-GNOME 3.4 situation will break your machine. Do NOT do the steps below unless you know what you are doing!

EDIT: I was able to update the packages on my old Core 2 Duo machine (slow...), but I can't push the changes to github because my ssh keys are on my dead computer. Here's how to update the packages:

1. Change to a temporary directory, not inside the previous git cloned directories. Then, download the tarballs for the latest updates.

mkdir ~/Unity-Packages-Temp
wget https://github.com/downloads/chenxiaolong/Unity-for-Arch/Unity-for-Arch_00d0abd68920c99842bedc7ab76675fc7f60bb72.tar.xz
wget https://github.com/downloads/chenxiaolong/Unity-for-Arch-Extra/Unity-for-Arch-Extra_d306c5c369a809e66d00865e21f5420e2e6f40c6.tar.xz
tar Jxvf Unity-for-Arch_00d0abd68920c99842bedc7ab76675fc7f60bb72.tar.xz
tar Jxvf Unity-for-Arch-Extra_d306c5c369a809e66d00865e21f5420e2e6f40c6.tar.xz

2. Update the packages as usual. The following packages from testing are now needed (Please move GNOME 3.4 to extra... ):

* pango
* gobject-introspection
* gdk-pixbuf2
* gnome-desktop

Last edited by chenxiaolong (2012-04-21 19:43:19)

fat0troll · 2012-04-25 21:33:22

when I building libcompizconfig, I got some error:

[fat0troll@basket-case libcompizconfig-ubuntu]$ LANG=C makepkg -sif
==> Making package: libcompizconfig-ubuntu 0.9.7.0.bzr428.0ubuntu6-100 (Thu Apr 26 01:28:25 MSK 2012)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving Sources...
  -> Found libcompizconfig_0.9.7.0~bzr428.orig.tar.bz2
  -> Found libcompizconfig_0.9.7.0~bzr428-0ubuntu6.debian.tar.gz
==> Validating source files with sha512sums...
    libcompizconfig_0.9.7.0~bzr428.orig.tar.bz2 ... Passed
    libcompizconfig_0.9.7.0~bzr428-0ubuntu6.debian.tar.gz ... Passed
==> Extracting Sources...
  -> Extracting libcompizconfig_0.9.7.0~bzr428.orig.tar.bz2 with bsdtar
  -> Extracting libcompizconfig_0.9.7.0~bzr428-0ubuntu6.debian.tar.gz with bsdtar
==> Removing existing pkg/ directory...
==> Starting build()...
patching file config/config
patching file src/bindings.c
CMake Error at CMakeLists.txt:9 (include):
  include could not find load file:

    CompizCommon


CMake Error at CMakeLists.txt:10 (include):
  include could not find load file:

    CompizPackage


CMake Error at CMakeLists.txt:125 (compiz_pkg_check_modules):
  Unknown CMake command "compiz_pkg_check_modules".


CMake Warning (dev) in CMakeLists.txt:
  No cmake_minimum_required command is present.  A line of code such as

    cmake_minimum_required(VERSION 2.8)

  should be added at the top of the file.  The version specified may be lower
  if you wish to support older CMake versions for this project.  For more
  information run "cmake --help-policy CMP0000".
This warning is for project developers.  Use -Wno-dev to suppress it.

-- Configuring incomplete, errors occurred!
==> ERROR: A failure occurred in build().
    Aborting...

Does anyone know how to fix it?

triplesquarednine · 2012-04-25 21:48:27

fat0troll wrote:

when I building libcompizconfig, I got some error:

[fat0troll@basket-case libcompizconfig-ubuntu]$ LANG=C makepkg -sif
==> Making package: libcompizconfig-ubuntu 0.9.7.0.bzr428.0ubuntu6-100 (Thu Apr 26 01:28:25 MSK 2012)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving Sources...
  -> Found libcompizconfig_0.9.7.0~bzr428.orig.tar.bz2
  -> Found libcompizconfig_0.9.7.0~bzr428-0ubuntu6.debian.tar.gz
==> Validating source files with sha512sums...
    libcompizconfig_0.9.7.0~bzr428.orig.tar.bz2 ... Passed
    libcompizconfig_0.9.7.0~bzr428-0ubuntu6.debian.tar.gz ... Passed
==> Extracting Sources...
  -> Extracting libcompizconfig_0.9.7.0~bzr428.orig.tar.bz2 with bsdtar
  -> Extracting libcompizconfig_0.9.7.0~bzr428-0ubuntu6.debian.tar.gz with bsdtar
==> Removing existing pkg/ directory...
==> Starting build()...
patching file config/config
patching file src/bindings.c
CMake Error at CMakeLists.txt:9 (include):
  include could not find load file:

    CompizCommon


CMake Error at CMakeLists.txt:10 (include):
  include could not find load file:

    CompizPackage


CMake Error at CMakeLists.txt:125 (compiz_pkg_check_modules):
  Unknown CMake command "compiz_pkg_check_modules".


CMake Warning (dev) in CMakeLists.txt:
  No cmake_minimum_required command is present.  A line of code such as

    cmake_minimum_required(VERSION 2.8)

  should be added at the top of the file.  The version specified may be lower
  if you wish to support older CMake versions for this project.  For more
  information run "cmake --help-policy CMP0000".
This warning is for project developers.  Use -Wno-dev to suppress it.

-- Configuring incomplete, errors occurred!
==> ERROR: A failure occurred in build().
    Aborting...

Does anyone know how to fix it?

I haven't build Unity, but the error you are getting from building compiz can be resolved by downgrading Cmake (to Cmake 2.8.7). I've been hit by this building compiz from bzr. The Compiz devs are aware of this build issue, but for now downgrading is the quick fix.

cheerz

fat0troll · 2012-04-25 21:56:44

triplesquarednine wrote:

I haven't build Unity, but the error you are getting from building compiz can be resolved by downgrading Cmake (to Cmake 2.8.7). I've been hit by this building compiz from bzr. The Compiz devs are aware of this build issue, but for now downgrading is the quick fix.
cheerz

Compiz devs are strange… it works, thank you!

chenxiaolong · 2012-04-25 22:05:32

triplesquarednine wrote:

I haven't build Unity, but the error you are getting from building compiz can be resolved by downgrading Cmake (to Cmake 2.8.7). I've been hit by this building compiz from bzr. The Compiz devs are aware of this build issue, but for now downgrading is the quick fix.
cheerz

Could you post a link where the Compiz devs said that? The issue is with CMake (affects many packages) and there's a patch for CMake to fix it.

Btw, I submitted a bug report about cmake and the issue is fixed in cmake 2.8.8-2.

fat0troll · 2012-04-25 22:08:54

chenxiaolong, thanks for your work, it's too pretty to think that I can try (good) Unity without (crappy) Ubuntu

btw, did you know, when your notebook will be working again?

// oh, sorry my bad english)

triplesquarednine · 2012-04-25 22:48:17

chenxiaolong wrote:

Could you post a link where the Compiz devs said that? The issue is with CMake (affects many packages) and there's a patch for CMake to fix it.

Go to lp:compiz-plugins-main and search the bug reports for 'cmake'. I 1st submitted a bug report a couple of days ago, then in another bug report i made a comment directly to Sam about it. Rufflove (who maintains compiz-bzr/dev in AUR) also, made a comment to the devs elsewhere on LP, a day or two ago.

I wasn't aware of the patch for cmake.

chenxiaolong wrote:

Btw, I submitted a bug report about cmake and the issue is fixed in cmake 2.8.8-2.

Cool. thanks for the info ~ I'll remove cmake from NoUpgrade (in pacman.conf)

cheerz

fat0troll · 2012-04-25 23:11:41

unity crashes when I hovering main menu icon, or indicators panel, or choosing "applications" lense (strange random crashes, really).

When it crashed one time it will crash on every start if didn't clean settings as described in github's README.

Here is the trace: http://paste.kde.org/463760/

Any suggestions?

chenxiaolong · 2012-04-26 00:06:08

fat0troll wrote:

chenxiaolong, thanks for your work, it's too pretty to think that I can try (good) Unity without (crappy) Ubuntu
btw, did you know, when your notebook will be working again?
// oh, sorry my bad english)

I actually got my notebook back from the repair center today, but they broke the power connector. 5 more hours until the battery runs out and I don't have a computer anymore

By the way, your english is very good

Arch Linux

#426 2012-04-04 03:44:19

Re: Progress on Unity under Arch Linux!

#427 2012-04-04 22:22:21

Re: Progress on Unity under Arch Linux!

#428 2012-04-05 04:44:16

Re: Progress on Unity under Arch Linux!

#429 2012-04-05 12:49:53

Re: Progress on Unity under Arch Linux!

#430 2012-04-05 12:56:03

Re: Progress on Unity under Arch Linux!

#431 2012-04-05 17:47:11

Re: Progress on Unity under Arch Linux!

#432 2012-04-05 17:58:45

Re: Progress on Unity under Arch Linux!

#433 2012-04-05 22:09:07

Re: Progress on Unity under Arch Linux!

#434 2012-04-06 01:06:25

Re: Progress on Unity under Arch Linux!

#435 2012-04-06 18:13:38

Re: Progress on Unity under Arch Linux!

#436 2012-04-06 19:19:18

Re: Progress on Unity under Arch Linux!

#437 2012-04-06 20:03:53

Re: Progress on Unity under Arch Linux!

#438 2012-04-08 08:13:07

Re: Progress on Unity under Arch Linux!

#439 2012-04-08 16:17:21

Re: Progress on Unity under Arch Linux!

#440 2012-04-09 11:14:28

Re: Progress on Unity under Arch Linux!

#441 2012-04-09 17:16:17

Re: Progress on Unity under Arch Linux!

#442 2012-04-20 05:06:16

Re: Progress on Unity under Arch Linux!

EDIT 2: WARNING: Do not perform the steps below. AGAIN, do NOT perform the steps below. The half-GNOME 3.2 and half-GNOME 3.4 situation will break your machine. Do NOT do the steps below unless you know what you are doing!

#443 2012-04-25 21:33:22

Re: Progress on Unity under Arch Linux!

#444 2012-04-25 21:48:27

Re: Progress on Unity under Arch Linux!

#445 2012-04-25 21:56:44

Re: Progress on Unity under Arch Linux!

#446 2012-04-25 22:05:32

Re: Progress on Unity under Arch Linux!

#447 2012-04-25 22:08:54

Re: Progress on Unity under Arch Linux!

#448 2012-04-25 22:48:17

Re: Progress on Unity under Arch Linux!

#449 2012-04-25 23:11:41

Re: Progress on Unity under Arch Linux!

#450 2012-04-26 00:06:08

Re: Progress on Unity under Arch Linux!

Board footer