Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 172924

Summary: x11-misc/xkeyboard-config-0.9 fails on XML::Parser
Product: Gentoo Linux Reporter: Jerzy SÅ‚adkowski <admin>
Component: New packagesAssignee: Gentoo Linux bug wranglers <bug-wranglers>
Status: RESOLVED DUPLICATE    
Severity: normal    
Priority: High    
Version: unspecified   
Hardware: AMD64   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---

Description Jerzy SÅ‚adkowski 2007-03-31 19:43:01 UTC
This bug is similar to bug# 41124 "XML::Parser not found in Gnome package" but not the same.

When I emerge modular xorg with command "emerge -Dvat xorg-x11" I have configure error in x11-misc/xkeyboard-config-0.9:

=====
checking for xkbcomp... /usr/bin/xkbcomp
checking for intltool >= 0.30... 0.33 found
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 filing a report to bugs.gentoo.org:
!!! /var/tmp/portage/x11-misc/xkeyboard-config-0.9/work/xkeyboard-config-0.9/config.log

!!! ERROR: x11-misc/xkeyboard-config-0.9 failed.
Call stack:
  ebuild.sh, line 1614:   Called dyn_compile
  ebuild.sh, line 971:   Called qa_call 'src_compile'
  ebuild.sh, line 44:   Called src_compile
  xkeyboard-config-0.9.ebuild, line 42:   Called econf '--with-xkb-base=/usr/share/X11/xkb' '--enable-compat-rules' '--disable-xkbcomp-symlink' '--with-xkb-rules-symlink=xorg'
  ebuild.sh, line 577:   Called die

!!! 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-misc/xkeyboard-config-0.9/temp/build.log'.
=====

Reproducible: Always




Re-emerging dev-perl/XML-Parser solve this promblem, but I think that must be more naturally solution for it.
Comment 1 Jakub Moc (RETIRED) gentoo-dev 2007-03-31 21:09:50 UTC
You need to run perl-cleaner after upgrading perl.

*** This bug has been marked as a duplicate of bug 41124 ***