Trouble emerging Gnome 2.18?

[thtroyer]

Ok. I keep compile errors while trying to install the gnome package. On a previous install (last week), I emerged Gnome 2.16 without any problems(I'm not exactly sure why that was installed, whether I hadn't synced portage or whether Gentoo just updated to Gnome 2.18, I don't know (I'm kinda new here).

In any case, with my previous install and with this one, I keep hitting compile bugs. Here's one I'm not sure what to do with:
The package is app-pda/gnome-pilot (which I don't really have a need for, but it appears to be a dependency of Gnome).

Compile error:

Code: Select all

util.c:36: error: initializer element is not constant
util.c:36: error: (near initialization for 'synctypes[0]')
util.c:37: error: initializer element is not constant
util.c:37: error: (near initialization for 'synctypes[1]')
util.c:38: error: initializer element is not constant
util.c:38: error: (near initialization for 'synctypes[2]')
util.c:39: error: initializer element is not constant
util.c:39: error: (near initialization for 'synctypes[3]')
util.c:40: error: initializer element is not constant
util.c:40: error: (near initialization for 'synctypes[4]')
util.c:41: error: initializer element is not constant
util.c:41: error: (near initialization for 'synctypes[5]')
util.c: In function 'get_default_pilot':
util.c:248: warning: assignment discards qualifiers from pointer target type
make[2]: *** [util.o] Error 1
make[2]: Leaving directory `/var/tmp/portage/app-pda/gnome-pilot-2.0.13/work/gnome-pilot-2.0.13/capplet'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/app-pda/gnome-pilot-2.0.13/work/gnome-pilot-2.0.13'
make: *** [all] Error 2

!!! ERROR: app-pda/gnome-pilot-2.0.13 failed.
Call stack:
  ebuild.sh, line 1632:   Called dyn_compile
  ebuild.sh, line 983:   Called qa_call 'src_compile'
  ebuild.sh, line 44:   Called src_compile
  ebuild.sh, line 1322:   Called gnome2_src_compile
  gnome2.eclass, line 71:   Called die

I can post the entire build log if I need to, but above that is compiler garble (though, it does have some warnings about pointers far above). Not really sure what to do with this one.

Even still, should I really be hitting that many compile errors while installing something like Gnome? I've had to manually fix 3-4 'problems' already, and I still have plenty of packages to install to get Gnome working. Is there something deeper wrong?

Again, I'm new to Gentoo, not so much to Linux (coming up on 2 years using Ubuntu).

Thanks.

[didymos]

Running into to compile errors isn't unusual. It's just the sort of thing you only see on binary distros if you are:

a. A package maintainer
b. Building from source on the binary distro
c. Developing on a binary distro

Most users probably don't do any of those very often, if at all. This particular bug is known, and there is a patch, but you'd have to apply it yourself as the fix hasn't been committed to the tree yet. The other options are to mask >gnome-pilot-2.0.10-r1, which is the latest stable, or to try and emerge successively lower unstable versions until you get one that builds. To continue on with the gnome emerge, you can do:

Code: Select all

emerge --resume --skipfirst

and leave gnome-pilot for later. If you run into something that depends on it (if anything does; I don't know), skip over that as well.

Here's the bug:


[bug=182699]app-pda/gnome-pilot-2.0.13 doesn't compile with gcc-4.1.2[/bug]


[edit] BTW, if you don't have a PDA, then you don't even need the package. If that's the case, then disable the pda USE flag in /etc/make.conf and gnome-pilot will probably just go away.

[thtroyer]

Alright. I didn't notice that there was a pda flag. That seems to work, and the '--resume --skipfirst' will definitely come in handy when snags show up.

I'm just finding it annoying that lately I've been doing compiles overnight, only to find that not even 10% was completed due to some random error.

I'll keep emerging Gnome... hopefully that's the end of the bugs, but I'll be back here if I find more.

Thanks!

[didymos]

I'm just finding it annoying that lately I've been doing compiles overnight, only to find that not even 10% was completed due to some random error.

Yeah, that can grate, but it's just part of the deal with a source-based distro. There are some scripts around that can ameliorate this to some extent by just skipping whatever fails then printing a list of failed packages when it's done. You can find some of them in the forums, but I don't know exactly which threads.

[Rcomian]

Yeah, that got me too, so I've ended up writing this:
http://forums.gentoo.org/viewtopic-t-473424.html

[sawatts]

This is also where I am now stuck. Everything else (not dependant on gnome-pilot) has been rebuilt against the new expat libraries (leaving evolution).

From capplet/util.c, global variable 'synctypes' is declared:

Code: Select all

static const char *synctypes[] = {_("Use conduit settings"), ...

So it is setting a global variable from the result of a function call, which you can't do in a C TU (gcc 3.4.6).

Rather than "_()", shouldn't the code be using "N_()", which is suppose to work with static strings.

Note: This appears to have been fixed in gnome-pilot 2.0.14, where 'synctypes' have been removed from utils.c.

[rem_proc_call]

fixed in 2.0.15 - just mark it ~arch in your package.keywords and move on.