* ERROR: x11-libs/pango-1.26.2 failed: * econf failed * Reproducible: Always Steps to Reproduce: 1. emerge x11-libs/pango-1.26.2 Actual Results: * ERROR: x11-libs/pango-1.26.2 failed: * econf failed * * Call stack: * ebuild.sh, line 54: Called src_configure * environment, line 3120: Called gnome2_src_configure * environment, line 2462: Called econf '--disable-introspection' '--with-x' '--disable-gtk-doc' * ebuild.sh, line 544: Called die * The specific snippet of code: * die "econf failed" * * If you need support, post the output of 'emerge --info =x11-libs/pango-1.26.2', * the complete build log and the output of 'emerge -pqv =x11-libs/pango-1.26.2'. * The complete build log is located at '/var/tmp/portage/x11-libs/pango-1.26.2/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/x11-libs/pango-1.26.2/temp/environment'. * S: '/var/tmp/portage/x11-libs/pango-1.26.2/work/pango-1.26.2' sandbox:main signal SIGQUIT already had a handler ... Expected Results: successful emerge I'll attach the build log and environment file forthwith.
Created attachment 239617 [details] build log
Created attachment 239619 [details] suggested emerge infos emerge -pqv =x11-libs/pango-1.26.2 and emerge --info =x11-libs/pango-1.26.2
Created attachment 239621 [details] envirionment
Check this out: # emerge --info =x11-libs/pango-1.26.2 !!! No gcc found. You probably need to 'source /etc/profile' !!! to update the environment of this terminal and possibly !!! other terminals also. How about trying again after sourcing /etc/profile
(In reply to comment #4) > Check this out: > > # emerge --info =x11-libs/pango-1.26.2 > !!! No gcc found. You probably need to 'source /etc/profile' > !!! to update the environment of this terminal and possibly > !!! other terminals also. > > How about trying again after sourcing /etc/profile > Anticipating you might ask that, you'll see that I already did in the emerge file right before I did the "emerge --info": # source /etc/profile # emerge --info =x11-libs/pango-1.26.2
gcc-config then ?
!!! Please attach the following file when seeking support: !!! /var/tmp/portage/x11-libs/pango-1.26.2/work/pango-1.26.2/config.log
/var/tmp/portage/x11-libs/pango-1.26.2/work is empty. Sorry, I missed the: !!! Please attach the following file when seeking support: !!! /var/tmp/portage/x11-libs/pango-1.26.2/work/pango-1.26.2/config.log since it appeared above the red stars and there was this similar section that caught my attention: * If you need support, post the output of 'emerge --info =x11-libs/pango-1.26.2', * the complete build log and the output of 'emerge -pqv =x11-libs/pango-1.26.2'. * The complete build log is located at '/var/tmp/portage/x11-libs/pango-1.26.2/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/x11-libs/pango-1.26.2/temp/environment'. * S: '/var/tmp/portage/x11-libs/pango-1.26.2/work/pango-1.26.2' sandbox:main signal SIGQUIT already had a handler ...
jlpoole-hip ~ # gcc-config --get-current-profile * gcc-config: Active gcc profile is invalid! [1] i686-pc-linux-gnu-4.4.3 jlpoole-hip ~ # hmmm, the emerging of x11-libs/pango-1.26.2 came during a routine: emerge --update --deep --newuse world --pretend emerge --depclean revdep-rebuild I'm attaching a session I just ran in response to the questions just raised in previous comments. There I: emerge --update --deep --newuse world --pretend emerge --update --deep --newuse world emerge --depclean revdep-rebuild The revdep-rebuild is what causes pango, and others, to be emerged.
Created attachment 239693 [details] standard emerge maintenace session the revdep-rebuild causes pango to be brought in for emerge which then breaks.
Read this again: * gcc-config: Active gcc profile is invalid! Set it to a valid value, the bug is most likely INVALID.
I select the only profile "[1] i686-pc-linux-gnu-4.4.3 ": gcc-config 1 and then ran redep-rebuild and the chain kicked off, this time x11-libs/pango-1.26.2 successfully emerged. Thank you. Question: I've been managing Gentoo on this machine for several months with performing updates at frequent intervals without having to specify the only gcc instance, e.g. "1". It may be that GCC updated itself, I manage several instances of Gentoo and recall recently seeing GCC listed on emerge updates. Is the unsetting of a profile a normal occurrence when GCC is updated, or should I be logging a bug with some other product?
Hard to tell, what most likely happened was old version of gcc (4.3, probably) getting depcleaned. I'm not sure whether that is properly (or at all) handled by the ebuild.
