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] avahi build failure on intltool-update
Date: Sat, 20 Feb 2010 19:37:16 +0100	[thread overview]
Message-ID: <20100220193716.3a92b370@surf> (raw)
In-Reply-To: <20100214120039.2c7ff159@surf>

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

      reply	other threads:[~2010-02-20 18:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-14 11:00 [Buildroot] avahi build failure on intltool-update Thomas Petazzoni
2010-02-20 18:37 ` Thomas Petazzoni [this message]

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=20100220193716.3a92b370@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