Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 110842 - Hal-0.4.7r2 emerge failed: "econf failed" XML::Parser config error
Summary: Hal-0.4.7r2 emerge failed: "econf failed" XML::Parser config error
Status: RESOLVED DUPLICATE of bug 41124
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: x86 Linux
: High blocker (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-29 15:59 UTC by Elliott Rezny
Modified: 2005-10-29 16:58 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---

Attachments
The config log portage specified to post to help debugging (config.log,54.92 KB, text/plain)
2005-10-29 16:01 UTC, Elliott Rezny 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Elliott Rezny 2005-10-29 15:59:22 UTC 
When hal-0.4.7r2 is emerged (new, no use flags used), the Emerge quits after
"checking for XML::Parser... configure: error: XML::Parser perl module is
required for intltool"

Portage then prints the error message:
!!! Please attach the config.log to your bug report:
!!! /var/tmp/portage/hal-0.4.7-r2/work/hal-0.4.7/config.log

!!! ERROR: sys-apps/hal-0.4.7-r2 failed.
!!! Function econf, Line 485, Exitcode 0
!!! econf failed
!!! If you need support, post the topmost build error, NOT this status message.

If you need any more info, Just tell me how to post it.

Reproducible: Always
Steps to Reproduce:
1. emerge -uvD --newuse world
or
1. emerge sys-apps/hal

Actual Results:  
The emerge quit during the config stage

Expected Results:  
The emerge should have continued through and installed hal.
Comment 1 Elliott Rezny 2005-10-29 16:01:32 UTC 
Created attachment 71696 [details]
The config log portage specified to post to help debugging
Comment 2 Carsten Lohrke (RETIRED) gentoo-dev 2005-10-29 16:58:41 UTC 

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