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 <[email protected]> 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 > <[email protected]> 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 -- _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-devel
