Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] troubles with intltool
Date: Thu, 9 Sep 2010 10:58:38 +0200	[thread overview]
Message-ID: <20100909105838.5ae25c27@surf> (raw)
In-Reply-To: <AANLkTikqwN4vkKaXWrA0SiGTwoYUYrST8vggtUwRVJRN@mail.gmail.com>

Hello,

On Thu, 9 Sep 2010 10:27:30 +0200
Aurele Traynard <aurele.traynard@laposte.net> wrote:

> I am trying to build an image with X11, an I am experimenting some
> problems with intltool
> the problem is when the script call /usr/bin/perl -e "require
> XML::Parser" i tried to use the following command : /usr/bin/perl -e
> "require XML::Parser"  to know what is the problem but it says
> nothing... could someone help, me next is the report

I've just tested, and xkeyboard-config builds fine here.
xkeyboard-config has a dependency on host-intltool, which itself has a
dependency on host-libxml-parser-perl.

And as you can see, we are properly passing:
 PERLLIB="/media/disk3/buildroot-2010.08/output/host/usr/lib/perl"
to the xkeyboard-config ./configure script.

Can you check
in /media/disk3/buildroot-2010.08/output/host/usr/lib/perl if
libxml-parser-perl is installed ?

Could you restart the build from scratch and keep the full build log:
 make 2>&1 | tee build.log
and then put online somewhere the full build log and your Buildroot
configuration ?

Thanks,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2010-09-09  8:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-09  8:27 [Buildroot] troubles with intltool Aurele Traynard
2010-09-09  8:58 ` Thomas Petazzoni [this message]
2010-09-10 14:17   ` Aurele Traynard
2010-09-12 21:12     ` Thomas Petazzoni

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=20100909105838.5ae25c27@surf \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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