<br><br><div class="gmail_quote">On Wed, Jun 19, 2013 at 11:02 AM, Richard Purdie <span dir="ltr"><<a href="mailto:richard.purdie@linuxfoundation.org" target="_blank">richard.purdie@linuxfoundation.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On Wed, 2013-06-19 at 10:50 -0400, Joe MacDonald wrote:<br>
> Adding the oe-core list back to the cc list since I accidentally<br>
> dropped the list on my first response.<br>
><br>
> On Wed, Jun 19, 2013 at 10:37 AM, Richard Purdie<br>
> <<a href="mailto:richard.purdie@linuxfoundation.org">richard.purdie@linuxfoundation.org</a>> wrote:<br>
> On Wed, 2013-06-19 at 10:15 -0400, Joe MacDonald wrote:<br>
> ><br>
> ><br>
><br>
> > On Wed, Jun 19, 2013 at 10:10 AM, Richard Purdie<br>
> > <<a href="mailto:richard.purdie@linuxfoundation.org">richard.purdie@linuxfoundation.org</a>> wrote:<br>
> > On Wed, 2013-06-19 at 09:56 -0400, <a href="mailto:joe@deserted.net">joe@deserted.net</a><br>
> wrote:<br>
> > > From: Joe MacDonald <<a href="mailto:joe@deserted.net">joe@deserted.net</a>><br>
> > ><br>
> > > Building bdwgc-native on systems with older<br>
> versions of<br>
> > autoconf (earlier<br>
> > > than 2.69) is known to have issues:<br>
> > ><br>
> > > <a href="https://github.com/ivmai/bdwgc/issues/16" target="_blank">https://github.com/ivmai/bdwgc/issues/16</a><br>
> > ><br>
> > > An option is to simply mask the errors with<br>
> > m4_pattern_allow(...) for each<br>
> > > of the macros, but rerunning autoreconf produces a<br>
> > functional configure<br>
> > > script that builds a functional native version of<br>
> bdwgc.<br>
> > ><br>
> > > Signed-off-by: Joe MacDonald <<a href="mailto:joe@deserted.net">joe@deserted.net</a>><br>
> > > ---<br>
> > > meta/recipes-support/bdwgc/<a href="http://bdwgc_7.2d.bb" target="_blank">bdwgc_7.2d.bb</a> | 9<br>
> +++++++++<br>
> > > 1 file changed, 9 insertions(+)<br>
> > ><br>
> > > I tripped over this yesterday on one of my older<br>
> builders.<br>
> > It happens to still<br>
> > > be Ubuntu 12.04.2. I don't know if it's unique to<br>
> my<br>
> > configuration, but after<br>
> > > doing some digging around on the web I can't see<br>
> any obvious<br>
> > indications that<br>
> > > I'm missing any autotools package and the general<br>
> consensus<br>
> > seems to be that<br>
> > > autoreconf is the best option when the failures<br>
> are<br>
> > relatively beign as they<br>
> > > are here.<br>
> > ><br>
> > > -J.<br>
> > ><br>
> > > diff --git<br>
> a/meta/recipes-support/bdwgc/<a href="http://bdwgc_7.2d.bb" target="_blank">bdwgc_7.2d.bb</a><br>
> > b/meta/recipes-support/bdwgc/<a href="http://bdwgc_7.2d.bb" target="_blank">bdwgc_7.2d.bb</a><br>
> > > index 46e5257..d8e2de5 100644<br>
> > > --- a/meta/recipes-support/bdwgc/<a href="http://bdwgc_7.2d.bb" target="_blank">bdwgc_7.2d.bb</a><br>
> > > +++ b/meta/recipes-support/bdwgc/<a href="http://bdwgc_7.2d.bb" target="_blank">bdwgc_7.2d.bb</a><br>
> > > @@ -36,3 +36,12 @@ ARM_INSTRUCTION_SET = "arm"<br>
> > ><br>
> > > inherit autotools<br>
> > > BBCLASSEXTEND = "native nativesdk"<br>
> > > +<br>
> > > +do_configure_prepend() {<br>
> > > + # Without this, on older installations of<br>
> autoconf<br>
> > errors crop up during configure:<br>
> > > + # | <a href="http://configure.ac:70" target="_blank">configure.ac:70</a>: error: possibly<br>
> undefined macro:<br>
> > AC_MSG_ERROR<br>
> > > + # | If this token and others are<br>
> legitimate,<br>
> > please use m4_pattern_allow.<br>
> > > + # | See the Autoconf documentation.<br>
> > > + # | <a href="http://configure.ac:358" target="_blank">configure.ac:358</a>: error: possibly<br>
> undefined macro:<br>
> > AS_IF<br>
> > > + ( cd ${S}; autoreconf -i )<br>
> > > +}<br>
> ><br>
> ><br>
> > This is timely since we're seeing this issue on some<br>
> of the<br>
> > autobuilders. We should be autoreconfing by default<br>
> though,<br>
> > any idea why<br>
> > it doesn't in this case?<br>
> ><br>
> ><br>
> > No, I didn't actually dig into that, I didn't realize it<br>
> should be<br>
> > autoreconfing. Is it explciit in the do_configure step, or<br>
> implicit?<br>
> > Maybe it's a timestamp issue or something? The only<br>
> machine I've got<br>
> > left that has this problem is pretty fast, so maybe on a<br>
> slower (or<br>
> > more heavily loaded) machine an implicit rule will fire<br>
> where a beefy,<br>
> > unloaded one won't? Just a wild guess.<br>
><br>
><br>
> Reading the link you supplied further, it could be a missing<br>
> pkgconfig<br>
> dependency?<br>
><br>
><br>
> I thought so at first, but I couldn't find anything absent on my<br>
> builder that looked even remotely pkgconfig-related. Then I started<br>
> digging into the autotools stuff, since the warning is clearly about<br>
> expanding autoconf macros and that's when I finally started paying<br>
> attention to the version numbers on the failing host versus the<br>
> builders I use that weren't complaining.<br>
><br>
><br>
> It could still be that there's something missing, but when I noticed<br>
> the comment just below the "closed" bar in the issue I linked:<br>
><br>
><br>
> ivmai commented10 months ago<br>
> I have tested the git sources from bdwgc and they only configure<br>
> properly with autoconf >= 2.69. [...]<br>
> It seemed like I'd found at least confirmation that what I was seeing<br>
> was expected.<br>
><br>
><br>
> I have no idea why the autotools.bbclass' autoreconf wouldn't do it,<br>
> though. I'll go have a quick look to see if the tree is different<br>
> because I also passed it -i when I did the autoreconf.<br>
><br>
<br>
</div></div>I have a reproducer:<br>
<br>
bitbake bdwgc-native pkgconfig-native -c clean; bitbake bdwgc-native<br>
<br>
Pretty sure its a missing pkgconfig dependency.<br></blockquote><div><br></div><div>Confirmed on the failing machine here too. You've got this, then? Or do you want me to send a new patch? </div></div><div><br></div>
-- <br>Joe MacDonald<br>:wq