From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Adam Lee <adam.yh.lee@gmail.com>
Cc: "openembedded-devel@lists.openembedded.org"
<openembedded-devel@lists.openembedded.org>
Subject: Re: exo build fail on master and master-next
Date: Wed, 26 Mar 2014 08:07:46 +0000 [thread overview]
Message-ID: <1395821266.24890.80.camel@ted> (raw)
In-Reply-To: <CAFeBWL7xAbqbsAZhJGaPBrL9DCdctfdau828WzE-Bojynodnsw@mail.gmail.com>
On Tue, 2014-03-25 at 17:46 -0700, Adam Lee wrote:
> exo-native (one of xfce4-taskmanager deps) was the point of failure.
> More specifically, exo-native was failing during configuration time. I
> discovered that, on master-next, exo-native build finishes by
> reverting this commit in autoconf.bbclass. This commit was new this
> year in Yocto Project 1.6. I have no idea how this commit breaks
> exo-native build. So I can't discern if the commit has errors. This
> still could very be a configuration issue in my build machine.
>
> Can anyone take a look at the commit one more time?
>
>On Mon, Mar 24, 2014 at 2:29 PM, Adam Lee <adam.yh.lee@gmail.com>
wrote:
> The error is occurring on master-next (and master I presume)
> when building xfce4-taskmanager (as part of XFCE4 Extended
> package group). I confirmed it on both qemuarm and on Gumstix
> Overo as build targets. This tells me it's a bug, but there
> still might be something unique about my setup.
>
> Can anyone verify if xfce4-taskmanager can be built
> successfully?
>
> On Fri, Mar 21, 2014 at 2:08 PM, Adam Lee
> <adam.yh.lee@gmail.com> wrote:
> Good day everyone,
> On both master and master-next, I get build fail on
> exo like below:
> configure.ac:112: error: possibly undefined macro: AC_PROG_INTLTOOL
> If this token and others are legitimate, please use m4_pattern_allow.
> See the Autoconf documentation.
That commit makes the system more strict about dependencies and they're
probably incorrect in your recipe. The above error suggests you're
missing a dependency on intltool-native.
Cheers,
Richard
next prev parent reply other threads:[~2014-03-26 8:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-21 21:08 exo build fail on master and master-next Adam Lee
2014-03-24 21:29 ` Adam Lee
2014-03-26 0:46 ` Adam Lee
2014-03-26 8:07 ` Richard Purdie [this message]
2014-03-26 21:00 ` Adam Lee
2014-03-26 21:08 ` Richard Purdie
2014-03-26 21:28 ` Adam Lee
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=1395821266.24890.80.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=adam.yh.lee@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
/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.