Re: [gentoo-user] Cannot emerge libgksu: lacks XML::Parser
On 1 Aug 2009, at 04:56, Kevin O'Gorman wrote: I've got portage's dev-perl/XML-Parser-2.36, but nevertheless several packages have started to fail during emerge for lack of Perl's XML::Parser. Even the simple script fails to run under perl: #!/usr/bin/perl -w use XML::Parser; print "yes\n"; Do I have to get it from CPAN? Why would you get it from CPAN? Have you tried re-emerging the package? Consider libgksu; here's the end of the emerge output, where XML::Parser is required by intltool: checking for perl... /usr/bin/perl checking for XML::Parser... configure: error: XML::Parser perl module is required for intltool It's surely saying that because the ebuild or makefile has a test script to see whether XML::Parser is present & working. Just as your `print "yes\n"` is failing so is the test run by the installation scripts, thus preventing install of libgksu. It sounds like ABCD is on the right track with his suggestion regarding the "ithreads" USE flag. But in any case you might normally try re-emerging the package and running revdep-rebuild before calling us. If I had this problem then - depending on how quick my machine was, how urgently I needed it fixed, and considering one might wait a few hours for a response here - I might well remerge everything with "perl" in the package name or category before becoming too flustered about this. You might well find that does the job. Stroller.
[gentoo-user] Cannot emerge libgksu: lacks XML::Parser
I've got portage's dev-perl/XML-Parser-2.36, but nevertheless several packages have started to fail during emerge for lack of Perl's XML::Parser. Even the simple script fails to run under perl: > #!/usr/bin/perl -w > > use XML::Parser; > > print "yes\n"; Do I have to get it from CPAN? Consider libgksu; here's the end of the emerge output, where XML::Parser is required by intltool: checking for perl... /usr/bin/perl 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/x11-libs/libgksu-2.0.9/work/libgksu-2.0.9/config.log * * ERROR: x11-libs/libgksu-2.0.9 failed. * Call stack: * ebuild.sh, line 49: Called src_compile * environment, line 2896: Called gnome2_src_compile * environment, line 2264: Called gnome2_src_configure * environment, line 2278: Called econf '--enable-nls' '--disable-gtk-doc' * ebuild.sh, line 534: Called die * The specific snippet of code: * die "econf failed" * The die message: * econf failed * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/x11-libs/libgksu-2.0.9/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/x11-libs/libgksu-2.0.9/temp/environment'. * >>> Failed to emerge x11-libs/libgksu-2.0.9, Log file: >>> '/var/tmp/portage/x11-libs/libgksu-2.0.9/temp/build.log' -- Kevin O'Gorman, PhD