I've looked at the other bugs on XML-Parser and gnome-icon-theme, where people were told to rebuild perl modules whenever they upgrade perl, but I DIDN"T upgrade perl!
All I did was a stage 3 2004.1 install, and then tried to emerge gnome-icon-theme.
Steps to Reproduce:
1. stage 3 2004.1 Gentoo install
2. emerge gnome-icon-theme
I get the exact same error message as in bug #52668:
configure: WARNING: If you wanted to set the --build type, don't use --host.
If a cross compiler is detected then cross compile mode will be used.
checking for a BSD-compatible install... /bin/install -c
checking whether build environment is sane... yes
Unknown `--run' option
--help' for more information
configure: WARNING: `missing' script is too old or missing
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for i686-pc-linux-gnu-strip... no
checking for strip... strip
checking whether to enable maintainer-specific portions of Makefiles... no
checking for perl... /usr/bin/perl
configure: error: XML::Parser perl module is required for intltool
!!! ERROR: x11-themes/gnome-icon-theme-1.2.1 failed.
!!! Function econf, Line 365, Exitcode 1
!!! econf failed
Perhaps perl was upgraded without rebuilding modules on the machine used to
generate the stage 3 tarball. My stage 3 install seems to have come that way.
I think part of the problem is simply dev-perl/XML-Parser needs to be added as a dependency of x11-themes/gnome-icon-theme (in some way). I did not have dev-perl/XML-Parser installed and was allowed to emerge x11-themes/gnome-icon-theme none-the-less.
Hope this helps :-).
this is currently:
Quoting intltool deps:
Which translates as "Build dependency of gnome-icon-theme includes XML-Parser"
So, could you please check your emerge.log? (attach it if nothing else) because something was weird with your perl/XML-Parser install
My install of XML-Parser came with the stage 3 tarball, so there's nothing in emerge.log about it. If there's something weird with it, I think it's probably a problem with the stage 3 tarball.
*** This bug has been marked as a duplicate of bug 41124 ***