Gentoo Archives: gentoo-user

From: ABCD <en.ABCD@×××××.com>
To: gentoo-user@l.g.o
Subject: [gentoo-user] Re: Cannot emerge libgksu: lacks XML::Parser
Date: Sat, 01 Aug 2009 04:52:16
Message-Id: h50hl1$lge$1@ger.gmane.org
In Reply to: [gentoo-user] Cannot emerge libgksu: lacks XML::Parser by Kevin O'Gorman
1 Kevin O'Gorman wrote:
2
3 > I've got portage's dev-perl/XML-Parser-2.36, but nevertheless several
4 > packages have started to fail during emerge for lack of Perl's
5 > XML::Parser.
6 > Even the simple script fails to run under perl:
7 >> #!/usr/bin/perl -w
8 >>
9 >> use XML::Parser;
10 >>
11 >> print "yes\n";
12 >
13 > Do I have to get it from CPAN?
14 >
15 > Consider libgksu; here's the end of the emerge output, where
16 > XML::Parser is required by intltool:
17 >
18 > checking for perl... /usr/bin/perl
19 > checking for XML::Parser... configure: error: XML::Parser perl module
20 > is required for intltool
21 >
22 > !!! Please attach the following file when seeking support:
23 > !!! /var/tmp/portage/x11-libs/libgksu-2.0.9/work/libgksu-2.0.9/config.log
24 > *
25 > * ERROR: x11-libs/libgksu-2.0.9 failed.
26 > * Call stack:
27 > * ebuild.sh, line 49: Called src_compile
28 > * environment, line 2896: Called gnome2_src_compile
29 > * environment, line 2264: Called gnome2_src_configure
30 > * environment, line 2278: Called econf '--enable-nls'
31 > '--disable-gtk-doc'
32 > * ebuild.sh, line 534: Called die
33 > * The specific snippet of code:
34 > * die "econf failed"
35 > * The die message:
36 > * econf failed
37 > *
38 > * If you need support, post the topmost build error, and the call
39 > stack if relevant.
40 > * A complete build log is located at
41 > '/var/tmp/portage/x11-libs/libgksu-2.0.9/temp/build.log'.
42 > * The ebuild environment file is located at
43 > '/var/tmp/portage/x11-libs/libgksu-2.0.9/temp/environment'.
44 > *
45 >
46 >>>> Failed to emerge x11-libs/libgksu-2.0.9, Log file:
47 >
48 >>>> '/var/tmp/portage/x11-libs/libgksu-2.0.9/temp/build.log'
49 >
50
51 Have you recently changed the "ithreads" USE flag on dev-lang/perl? If so,
52 then you will need to remerge all ebuilds that installed files in
53 /usr/lib*/perl5/vendor_perl/${PERL_VER}/${CHOST%%-*}-linux if "ithreads" was
54 disabled, and /usr/lib*/perl5/vendor_perl/${PERL_VER}/${CHOST%%-*}-linux-
55 thread-multi if "ithreads" was enabled.
56
57 Also, if you have recently upgraded perl, the same provisions apply.
58
59 NOTE: In the above expansion, the following applies [sorry if you already
60 know this]:
61
62 - "lib*" is lib on x86, lib64 on amd64
63 - ${PERL_VER} is your perl version, probably 5.8.8
64 - ${CHOST%%-*} is the part of the CHOST before the first "-":
65 * on x86, it will be one of i486, i586, or i686
66 * on amd64, it will be x86_64
67
68 If you aren't on x86 or amd64, I assume you can figure it out :).
69
70 --
71 ABCD

Replies

Subject Author
Re: [gentoo-user] Re: Cannot emerge libgksu: lacks XML::Parser Kevin O'Gorman <kogorman@×××××.com>