| Summary: | x11-libs/gtk+-2.12.10-r1: compile fails with: gtk-update-icon-cache: The generated cache was invalid | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Flo Gravo <even.more.spam.for.me> |
| Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
| Status: | RESOLVED NEEDINFO | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | PPC | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | Complete /var/tmp/portage/x11-libs/gtk+-2.12.10-r1/temp/build.log | ||
|
Description
Flo Gravo
2008-07-14 10:17:36 UTC
Created attachment 160314 [details]
Complete /var/tmp/portage/x11-libs/gtk+-2.12.10-r1/temp/build.log
could you try with -O2 in place of -Os ? (In reply to comment #2) > could you try with -O2 in place of -Os ? > Same result... could you try to run gtk-update-icon-cache with gdb ? please make sure to rebuild whatever is needed with debugging symbols and appropriate FEATURES settings (here only glib and gtk itself I guess). (In reply to comment #0) Hi I get quite the same problem : gtk+-2.12.11 failed with same error and trying to see for a difference with my current gtk+-2.12.10-r1, I launched ebuild ...gtk+-2.12.10-r1 which failed. So with what I've read on the net looking for "gtk-update-icon-cache..." it could be a theme installed since I succeeded with (my) current gtk (june 13). Investigating. I'm having this problem with x11-libs/gtk+-2.12.11 on ~sparc. please provide informations asked for in comment #4. In my case at least, running the already installed gtk-update-icon-cache doesn't segfault or anything. The error during the build isn't a segfault or similar, either. It won't be trivial to debug with gdb. An idea I have is maybe to delete the icon cache, then emerge -u gtk+, but I have no idea where that icon cache is stored anyways. This is caused by glib-2.16.4. See http://bugzilla.gnome.org/show_bug.cgi?id=542919. I've verified that an upgrade to glib-2.16.5 resolves the issue. (In reply to comment #9) > This is caused by glib-2.16.4. See > http://bugzilla.gnome.org/show_bug.cgi?id=542919. I've verified that an upgrade > to glib-2.16.5 resolves the issue. > Not for me; upgraded glib and then tried to upgrade gtk+, to no avail; same problem. I had the same problem. Downgrading glib to 2.16.3-r1 helped |