From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] avahi build failure on intltool-update
Date: Sun, 14 Feb 2010 12:00:39 +0100 [thread overview]
Message-ID: <20100214120039.2c7ff159@surf> (raw)
Hello,
With the attached .config, I get the following build failure on avahi
(and I must leave so I don't have the time to dig into it now) :
=============================================================================================
checking for intltool >= 0.35.0... ./configure: line 28714: intltool-update: command not found
found
configure: error: Your intltool is too old. You need intltool 0.35.0 or later.
=============================================================================================
Looks strange to me, since intltool isn't packaged at all in Buildroot,
and I know that Peter is using avahi regularly. Peter, in
bc9512c09d59d731a2ad0b96ce778ca8f90964c1, you made some changes
regarding locale/gettext/intl support in avahi. Can you explain how
these things work, and maybe why intltool-update seems to be required
in my config ?
The configure.ac on avahi seems pretty clear that intltool is required
in any case.
The full build log is available at
http://free-electrons.com/~thomas/buildroot/avahi-intl/build.log.bz2
(bz2 compressed, because it is 25M uncompressed).
Cheers,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: config
Type: application/octet-stream
Size: 31124 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20100214/3481150d/attachment-0001.obj>
next reply other threads:[~2010-02-14 11:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-14 11:00 Thomas Petazzoni [this message]
2010-02-20 18:37 ` [Buildroot] avahi build failure on intltool-update 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=20100214120039.2c7ff159@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 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.