From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 1813] New: xkeyboard-config fails to build because of intltool problem
Date: Sat, 22 May 2010 06:42:47 +0000 (UTC) [thread overview]
Message-ID: <bug-1813-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=1813
Summary: xkeyboard-config fails to build because of intltool
problem
Product: buildroot
Version: 2010.02
Platform: PC
OS/Version: Linux
Status: NEW
Severity: minor
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: paul at pauljones.id.au
CC: buildroot at uclibc.org
Estimated Hours: 0.0
checking dependency style of
/home/peejay/mini2440-dev/buildroot/output/staging/usr/bin/arm-unknown-linux-uclibcgnueabi-gcc
-Os -pipe -Os -mtune=arm920t -march=armv4t -mabi=aapcs-linux -msoft-float
-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64
-I/home/peejay/mini2440-dev/buildroot/output/staging/usr/include
-I/home/peejay/mini2440-dev/buildroot/output/staging/include
--sysroot=/home/peejay/mini2440-dev/buildroot/output/staging/ -isysroot
/home/peejay/mini2440-dev/buildroot/output/staging... none
checking for intltool >= 0.30... ./configure.lineno: 3745: intltool-update: not
found
found
configure: error: Your intltool is too old. You need intltool 0.30 or later.
make: ***
[/home/peejay/mini2440-dev/buildroot/output/build/xkeyboard-config-1.8/.stamp_configured]
Error 1
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2010-05-22 6:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-22 6:42 bugzilla at busybox.net [this message]
2010-06-05 15:31 ` [Buildroot] [Bug 1813] xkeyboard-config fails to build because of intltool problem bugzilla at busybox.net
2010-06-08 20:42 ` bugzilla at busybox.net
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=bug-1813-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.