Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
* [Buildroot] avahi build failure on intltool-update
@ 2010-02-14 11:00 Thomas Petazzoni
  2010-02-20 18:37 ` Thomas Petazzoni
  0 siblings, 1 reply; 2+ messages in thread
From: Thomas Petazzoni @ 2010-02-14 11:00 UTC (permalink / raw)
  To: buildroot

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>

^ permalink raw reply	[flat|nested] 2+ messages in thread

* [Buildroot] avahi build failure on intltool-update
  2010-02-14 11:00 [Buildroot] avahi build failure on intltool-update Thomas Petazzoni
@ 2010-02-20 18:37 ` Thomas Petazzoni
  0 siblings, 0 replies; 2+ messages in thread
From: Thomas Petazzoni @ 2010-02-20 18:37 UTC (permalink / raw)
  To: buildroot

Hello,

On Sun, 14 Feb 2010 12:00:39 +0100
Thomas Petazzoni <thomas.petazzoni@free-electrons.com> wrote:

> 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.
> =============================================================================================

This problem occurs with several other packages as well, if intltool is
not installed on the host system.

Two options :

 1. Build intltool. intltool depends on Perl and the XML::Parser Perl
    module. Which of these do we build, and which of these do we
    require ?

 2. Depend on intltool unconditionnally in
    toolchain/dependencies/depencies.sh. This is the simplest solution,
    but would mean that all of our users would have to install intltool
    even if they don't build one the packages using it.

 3. Depend on intltool only if one of the packages needing it is
    enabled. But we could still do the check at the beginning of the
    build process.

Which solution?

Cheers,

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2010-02-20 18:37 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-02-14 11:00 [Buildroot] avahi build failure on intltool-update Thomas Petazzoni
2010-02-20 18:37 ` Thomas Petazzoni

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox