public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: YoYo siska <yoyo@gl.ksp.sk>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] emerge failures for libgsf & intltool
Date: Mon, 22 Feb 2010 16:35:36 +0100	[thread overview]
Message-ID: <20100222153536.GB11507@ksp.sk> (raw)
In-Reply-To: <201002221516.29678.gentoo@appjaws.plus.com>

On Mon, Feb 22, 2010 at 03:16:29PM +0100, Paul Stear wrote:
> Both of the above update emerges failed with the same error:
> For libgsf:-
> checking for XML::Parser... configure: error: XML::Parser perl module is 
> required for intltool
> For intitool
> checking for XML::Parser... configure: error: XML::Parser perl module is 
> required for intltool
> 
> How do I install a perl XML parser? Where is it located?
> Thanks for any help
> Paul

emerge -av1 XML-Parser

I the last update I had several failures due to perl packages missing,
they weren't actually missing, just in incorrect perl version and needed
remerging...

Is there something along the lines of python-updater for perl?

I just remerged the perl packages everytime something complained
(wasn't that much), usually replace :: with - to get the package name ;)

I was a bit more lucky, as the packages that failed for me didn't check
for the modules in configure, but just failed somewhere in the build
with a "XXXX not found" message, so I just ran qfile `locate XXXX` to
get the package...


yoyo

-- 
      _
      |            
YoYo () Siska      
===================
http://www.ksp.sk/




  parent reply	other threads:[~2010-02-22 16:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-22 14:16 [gentoo-amd64] emerge failures for libgsf & intltool Paul Stear
2010-02-22 15:34 ` Frank Peters
2010-02-22 18:37   ` Paul Stear
2010-02-22 15:35 ` YoYo siska [this message]
2010-02-22 16:56   ` Peter Humphrey
2010-02-22 18:09     ` YoYo siska
2010-02-22 16:02 ` John Keeping

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100222153536.GB11507@ksp.sk \
    --to=yoyo@gl.ksp.sk \
    --cc=gentoo-amd64@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox