Summary: | app-text/evince-3.8.3 fails to compile | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Agostino Sarubbo <ago> |
Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED CANTFIX | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
build log
build log |
Description
Agostino Sarubbo
2013-12-22 22:39:38 UTC
Not that it will help much (as the problem seems to be a segfault), but could you attach a build log without '-s' in MAKEOPTS ? Created attachment 365948 [details]
build log
Does it also fail with MAKEOPTS="-j1"? What gobject-introspection / gobject-introspection-common / glib do you had at the time it was compiling? (In reply to Pacho Ramos from comment #3) > Does it also fail with MAKEOPTS="-j1"? Yes > What gobject-introspection / > gobject-introspection-common / glib do you had at the time it was compiling? desktop ~ # eix gobject -I [I] dev-libs/gobject-introspection Available versions: 1.32.1 ~1.34.2-r1 1.36.0-r1 {cairo doc doctool test PYTHON_SINGLE_TARGET="python2_7" PYTHON_TARGETS="python2_7"} Installed versions: 1.36.0-r1(10:49:29 22/12/2013)(-cairo -doctool -test PYTHON_SINGLE_TARGET="python2_7" PYTHON_TARGETS="python2_7") Homepage: http://live.gnome.org/GObjectIntrospection/ Description: Introspection infrastructure for generating gobject library bindings for various languages [I] dev-libs/gobject-introspection-common Available versions: 1.32.1 ~1.34.2 1.36.0 Installed versions: 1.36.0(10:08:58 22/12/2013) Homepage: http://live.gnome.org/GObjectIntrospection/ Description: Build infrastructure for GObject Introspection [I] dev-python/pygobject Available versions: (2) 2.28.6-r53 ~2.28.6-r54 2.28.6-r55 (3) 3.2.2-r1 ~3.4.2-r1 3.8.3 {+cairo examples libffi test +threads PYTHON_TARGETS="python2_6 python2_7 python3_2 python3_3"} Installed versions: 2.28.6-r55(2)(13:05:10 22/12/2013)(-examples -libffi -test PYTHON_TARGETS="python2_7 -python2_6") 3.8.3(3)(13:15:05 22/12/2013)(cairo threads -examples -test PYTHON_TARGETS="python2_7 -python2_6 -python3_2 -python3_3") Homepage: http://www.pygtk.org/ Description: GLib's GObject library bindings for Python I] dev-libs/glib Available versions: (1) 1.2.10-r5 (2) 2.32.4-r1 ~2.34.3-r1 2.36.4-r1 {debug fam hardened selinux static-libs systemtap test utils xattr ABI_MIPS="n32 n64 o32" ABI_X86="32 64 x32" KERNEL="linux" PYTHON_TARGETS="python2_6 python2_7"} Installed versions: 2.36.4-r1(2)(10:22:23 22/12/2013)(-debug -fam -selinux -static-libs -systemtap -test -utils -xattr ABI_MIPS="-n32 -n64 -o32" ABI_X86="64 -32 -x32" KERNEL="linux" PYTHON_TARGETS="python2_7 -python2_6") Homepage: http://www.gtk.org/ Description: The GLib library of C routines the problem appears when glib/gobject-introspection are compiled with my extra_econf="--disable-static --disable-debug --disable-dependency-tracking" Per glib ebuild: # Building with --disable-debug highly unrecommended. It will build glib in # an unusable form as it disables some commonly used API. Please do not # convert this to the use_enable form, as it results in a broken build. use debug && myconf="--enable-debug" I also remember that upstream told us to never completely disable debug, especially for glib, but that dates back from years ago. I would be inclined to fix this bug is invalid or cantfix because we explicitly handle this case and overriding it with extra_econf is, well, putting you in charge :) you right.. |