From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1MXF2M-0000y2-UE for garchives@archives.gentoo.org; Sat, 01 Aug 2009 13:54:15 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id DB902E041B; Sat, 1 Aug 2009 13:54:13 +0000 (UTC) Received: from mail-vw0-f198.google.com (mail-vw0-f198.google.com [209.85.212.198]) by pigeon.gentoo.org (Postfix) with ESMTP id A888BE041B for ; Sat, 1 Aug 2009 13:54:13 +0000 (UTC) Received: by vws36 with SMTP id 36so661272vws.10 for ; Sat, 01 Aug 2009 06:54:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=P5XfsvJXgHnT2RNa0yVksuoN7LSWtaN/MBOFeQnpRVY=; b=EJ0GigTDvGydRipVv2kQrwilUD1nT+pH86lB8jXm4RXGBCeOZbZiUJsnrIM6u+TPMz 69rBzUj3arZ1/zd+bBDXpVbkQ4RoNlLVWAwQdJTbqY58Xdk6bRpJFrhfmlViEyFUpNSe CCO2hVXMuQK2qVz1UNqd1T3T9n6ShKgsTSzMY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=PRA8794Tn8+iV7zus+wsfwNr0/Sde2lzXtzZ2d1sc0BN/YY7EqM8mEojvqfHMGDCkW 5vr4/wRUuKifJPwlo+dBNrST/xkuRA4qxtI/bsMixt/KE8H59t2kDVxc9ewC08xVvMrr RlG60IAAzuxROGyII6eMcxI6pt7a6XxkHSfHQ= Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Received: by 10.220.75.21 with SMTP id w21mr3722720vcj.32.1249134853347; Sat, 01 Aug 2009 06:54:13 -0700 (PDT) In-Reply-To: References: <9acccfe50907312056v7e311f5al42370edb4e13dcd0@mail.gmail.com> Date: Sat, 1 Aug 2009 06:54:13 -0700 Message-ID: <9acccfe50908010654s3cd181a9ue4f847b1f8d6e7bc@mail.gmail.com> Subject: Re: [gentoo-user] Re: Cannot emerge libgksu: lacks XML::Parser From: "Kevin O'Gorman" To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: a031fb69-a293-4a9c-af0a-77dbf9bb4709 X-Archives-Hash: 528dfbcc9d5882d72316ac1658da9e28 On Fri, Jul 31, 2009 at 9:51 PM, ABCD wrote: > 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? >> >> 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.lo= g >> =A0* >> =A0* ERROR: x11-libs/libgksu-2.0.9 failed. >> =A0* Call stack: >> =A0* =A0 =A0 =A0 =A0 =A0 =A0 =A0 ebuild.sh, line =A0 49: =A0Called src_c= ompile >> =A0* =A0 =A0 =A0 =A0 =A0 =A0 environment, line 2896: =A0Called gnome2_sr= c_compile >> =A0* =A0 =A0 =A0 =A0 =A0 =A0 environment, line 2264: =A0Called gnome2_sr= c_configure >> =A0* =A0 =A0 =A0 =A0 =A0 =A0 environment, line 2278: =A0Called econf '--= enable-nls' >> '--disable-gtk-doc' >> =A0* =A0 =A0 =A0 =A0 =A0 =A0 =A0 ebuild.sh, line =A0534: =A0Called die >> =A0* The specific snippet of code: >> =A0* =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0die "econf failed" >> =A0* =A0The die message: >> =A0* =A0 econf failed >> =A0* >> =A0* If you need support, post the topmost build error, and the call >> stack if relevant. >> =A0* A complete build log is located at >> '/var/tmp/portage/x11-libs/libgksu-2.0.9/temp/build.log'. >> =A0* The ebuild environment file is located at >> '/var/tmp/portage/x11-libs/libgksu-2.0.9/temp/environment'. >> =A0* >> >>>>> Failed to emerge x11-libs/libgksu-2.0.9, Log file: >> >>>>> =A0'/var/tmp/portage/x11-libs/libgksu-2.0.9/temp/build.log' >> > > Have you recently changed the "ithreads" USE flag on dev-lang/perl? If so= , > then you will need to remerge all ebuilds that installed files in > /usr/lib*/perl5/vendor_perl/${PERL_VER}/${CHOST%%-*}-linux if "ithreads" = was > disabled, and /usr/lib*/perl5/vendor_perl/${PERL_VER}/${CHOST%%-*}-linux- > thread-multi if "ithreads" was enabled. > > Also, if you have recently upgraded perl, the same provisions apply. > > NOTE: In the above expansion, the following applies [sorry if you already > know this]: > > - "lib*" is lib on x86, lib64 on amd64 > - ${PERL_VER} is your perl version, probably 5.8.8 > - ${CHOST%%-*} is the part of the CHOST before the first "-": > =A0* on x86, it will be one of i486, i586, or i686 > =A0* on amd64, it will be x86_64 > > If you aren't on x86 or amd64, I assume you can figure it out :). This is helpful, as I do remember fooling with ithreads and not getting it completely right. I'm now emerging anything that has 'perl' in the name or category. It has always baffled me, given this sensitivity, that all such packages don't just declare that they use the 'ithreads' USE flag, even if they don't explicitly. Then my usual emerge --newuse would do the Right Thing (TM). ++ kevin --=20 Kevin O'Gorman, PhD