checking for XML::Parser... configure: error: XML::Parser perl module is required for intltool !!! Please attach the following file when seeking support: !!! /var/tmp/portage/gnome-base/gnome-mime-data-2.18.0/work/gnome-mime-data-2.18.0/config.log * ERROR: gnome-base/gnome-mime-data-2.18.0 failed (compile phase): * econf failed * * Call stack: * ebuild.sh, line 56: Called src_compile * environment, line 3037: Called gnome2_src_compile * environment, line 2345: Called gnome2_src_configure * environment, line 2359: Called econf * ebuild.sh, line 557: Called die * The specific snippet of code: * die "econf failed"
Created attachment 268401 [details] config.log
Created attachment 268405 [details] emerge --info =gnome-base/gnome-mime-data-2.18.0
# emerge -pqv =gnome-base/gnome-mime-data-2.18.0 [ebuild R ] gnome-base/gnome-mime-data-2.18.0 USE="-debug*"
Usually such error suggests you need to use 'perl-cleaner' after perl upgrade, but last perl upgrade was quite awhile ago. Is dev-perl/XML-Parser emerged ?
Sorry for the delay. I tried to install plog to answer your question but failed (installed first paludis which required hours until I noticed it doesn't contain plog so that I installed paludis-tools manually which fails on "import paludis" in Python code). Grml, Debian is so much easier ... (In reply to comment #4) > Usually such error suggests you need to use 'perl-cleaner' after perl upgrade, > but last perl upgrade was quite awhile ago. I called perl-cleaner in the past after major pearl update. > Is dev-perl/XML-Parser emerged ? It was not (as /var/log/emerge.log reveals instead of plog). After installing it (which I did already yesterday before my system update) gnome-mime-data could be build. Please note that I have LINGUAS="de en" in /etc/make.conf which probably enables i18n support.
gnome-mime-data depends on intltool which runtime depends on dev-perl/XML-Parser. There is no reason it would be absent from your system under normal circumstances. From a pure dependency POV, if I didn't overlook something, this report is invalid. Maybe it's a bug in paludis ? Forwarding to paludis maintainer.
*** This bug has been marked as a duplicate of bug 41124 ***