Summary: | x11-libs/gdk-pixbuf-2.26.4: ERROR: failed (compile phase): emake failed | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Alexandre <alexandre.guimaraes> |
Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | mk106c-gentoo |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
Complete build log.
Complete build log. Complete build log. Complete build log. |
Description
Alexandre
2012-11-11 14:37:57 UTC
Created attachment 329214 [details]
Complete build log.
I cannot reproduce the problem. Is it repeatable? What versions of dev-libs/glib and dev-libs/gobject-introspection do you have? MAKEOPTS="-j3 -s" Try again with MAKEOPTS="-j1" - it might be a parallel make problem (and '-s' makes the log far less useful than it should be). Since yesterday I am having this issue. dev-libs/glib-2.32.4-r1 USE="-debug (-fam) (-selinux) -static-libs -systemtap {-test} -utils -xattr" dev-libs/gobject-introspection-1.32.1 USE="-doc -doctool {-test}" *Compiling now with MAKEOPTS="-j1" *I already removed ccache but also failed. Created attachment 329246 [details]
Complete build log.
MAKEOPTS="-j1" - without ccache.
I still can't see why this would be happening :/ Please attach an extra-verbose build log with MAKEOPTS="-j1 V=1 --debug=a" Created attachment 329248 [details]
Complete build log.
MAKEOPTS="-j1 V=1 --debug=a"
Thank you!
Thanks; the cause of the failure seems clear now. I think that you had either accidentally uninstalled dev-libs/gobject-introspection-common, or deleted the /usr/share/gobject-introspection-1.0/Makefile.introspection file To fix the problem, simply "emerge -1av dev-libs/gobject-introspection-common" I re-emerged (already installed) dev-libs/gobject-introspection-common but x11-libs/gdk-pixbuf-2.26.4 still failing. :-( Created attachment 329254 [details]
Complete build log.
After "emerge -1av dev-libs/gobject-introspection-common".
*The log appear to be different.
*I'm on KDE profile.
I re-emerged dev-libs/gobject-introspection-1.32.1 and x11-libs/gdk-pixbuf-2.26.4 is compiled. :-D Thanks you! (In reply to comment #10) > Created attachment 329254 [details] > Complete build log. > > After "emerge -1av dev-libs/gobject-introspection-common". > > *The log appear to be different. > *I'm on KDE profile. This is good progress! The build system is now correctly calling g-ir-scanner. g-ir-scanner is returning an error because /usr/share/gobject-introspection-1.0/gdump.c cannot be found. That file should be installed by gobject-introspection; so do "emerge -1av dev-libs/gobject-introspection" and it should fix the problem. Now, a big warning: two packages that you say you already had emerged (gobject-introspection and gobject-introspection-common) should have installed certain files, but these files were either missing or corrupt on your hard drive. It's possible that you had filesystem corruption (e.g. from power failure, bad hardware, or a kernel bug), or some command or script that you had run as root had deleted random files in /usr/share. I would suggest you try to figure out what had gone wrong with your system, and take appropriate steps. (In reply to comment #11) > I re-emerged dev-libs/gobject-introspection-1.32.1 and > x11-libs/gdk-pixbuf-2.26.4 is compiled. :-D > > Thanks you! Good to hear. But please read my warning in comment #12: I believe the problem had been caused either by filesystem corruption or because some command/script had deleted random system files. Thank you for the tip! I'll take a look on it! Maybe I was 'victim' of the already fixed 'EXT4 Data Corruption Bug'. I used that version for a couple of days and I already know: some music files gone. Perhaps is better to use 'emerge -e world'. But it will take around 2 days on my 'old low cost mobile processor'. :-/ The "resolved invalid" status means that the problem was caused not by a bug in gentoo ebuilds, but by some factor outside gentoo developer control like filesystem corruption, hardware issues, manually installed software not supported by gentoo, etc. (In reply to comment #14) > Thank you for the tip! > > I'll take a look on it! > > Maybe I was 'victim' of the already fixed 'EXT4 Data Corruption Bug'. I used > that version for a couple of days and I already know: some music files gone. > IIRC, that bug was sort of bogus - you needed to use mount options that were meant to be used only by kernel devs *and* shutdown in a very atypical way. |