Adding the oe-core list back to the cc list since I accidentally dropped the list on my first response.<br><br><div class="gmail_quote">On Wed, Jun 19, 2013 at 10:37 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="im">On Wed, 2013-06-19 at 10:15 -0400, Joe MacDonald wrote:<br>
><br>
><br>
</div><div><div class="h5">> 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> wrote:<br>
> > From: Joe MacDonald <<a href="mailto:joe@deserted.net">joe@deserted.net</a>><br>
> ><br>
> > Building bdwgc-native on systems with older 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 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>
> > 1 file changed, 9 insertions(+)<br>
> ><br>
> > I tripped over this yesterday on one of my older builders.<br>
> It happens to still<br>
> > be Ubuntu 12.04.2. I don't know if it's unique to my<br>
> configuration, but after<br>
> > doing some digging around on the web I can't see any obvious<br>
> indications that<br>
> > I'm missing any autotools package and the general consensus<br>
> seems to be that<br>
> > autoreconf is the best option when the failures are<br>
> relatively beign as they<br>
> > are here.<br>
> ><br>
> > -J.<br>
> ><br>
> > diff --git 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 autoconf<br>
> errors crop up during configure:<br>
> > + # | <a href="http://configure.ac:70" target="_blank">configure.ac:70</a>: error: possibly undefined macro:<br>
> AC_MSG_ERROR<br>
> > + # | If this token and others are 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 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 of the<br>
> autobuilders. We should be autoreconfing by default 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 should be<br>
> autoreconfing. Is it explciit in the do_configure step, or implicit?<br>
> Maybe it's a timestamp issue or something? The only machine I've got<br>
> left that has this problem is pretty fast, so maybe on a slower (or<br>
> more heavily loaded) machine an implicit rule will fire where a beefy,<br>
> unloaded one won't? Just a wild guess.<br>
<br>
</div></div>Reading the link you supplied further, it could be a missing pkgconfig<br>
dependency?<br></blockquote><div><br></div><div>I thought so at first, but I couldn't find anything absent on my builder that looked even remotely pkgconfig-related. Then I started digging into the autotools stuff, since the warning is clearly about expanding autoconf macros and that's when I finally started paying attention to the version numbers on the failing host versus the builders I use that weren't complaining.</div>
<div><br></div><div>It could still be that there's something missing, but when I noticed the comment just below the "closed" bar in the issue I linked:</div><div><br></div><div><div class="comment-header normal-comment-header" style="height:33px;padding:0px 10px 0px 6px;border-bottom-width:1px;border-bottom-style:solid;border-bottom-color:rgb(204,204,204);background-color:rgb(225,225,225);background-image:linear-gradient(rgb(248,248,248),rgb(225,225,225));font-size:13.333333969116211px;color:rgb(51,51,51);font-family:Helvetica,arial,freesans,clean,sans-serif;background-repeat:repeat no-repeat">
<a href="https://github.com/ivmai/bdwgc/issues/16#issuecomment-7854845" class="comment-type-icon octicon octicon-mail-read tooltipped downwards" style="color:rgb(147,154,160);text-decoration:none;font-size:16px;font-family:github-octicons;line-height:1;display:inline-block;margin:8px 2px 0px 1px"></a> <a href="https://github.com/ivmai" class="comment-header-author" style="color:rgb(34,34,34);text-decoration:none;max-width:600px;line-height:33px;font-weight:bold;overflow:hidden;white-space:nowrap;text-overflow:ellipsis">ivmai</a> <span class="comment-header-action-text"><a href="https://github.com/ivmai/bdwgc/issues/16#issuecomment-7854845" style="color:rgb(102,102,102);text-decoration:none">commented</a></span><span class="comment-header-right" style="float:right"><a href="https://github.com/ivmai/bdwgc/issues/16#issuecomment-7854845" class="comment-header-date" style="color:rgb(119,119,119);text-decoration:none;display:inline-block;margin:0px;height:33px;font-size:11px;line-height:33px">10 months ago</a></span></div>
<div class="comment-content" style="padding:0px;color:rgb(51,51,51);font-size:13.333333969116211px;background-color:rgb(251,251,251);font-family:Helvetica,arial,freesans,clean,sans-serif"><div class="edit-comment-hide"><div class="js-comment-body comment-body markdown-body" style="line-height:1.7;overflow:auto;padding:10px;width:731.8056030273438px">
<div class="email-fragment" style="margin-top:0px!important">I have tested the git sources from bdwgc and they only configure properly with autoconf >= 2.69. [...]</div></div></div></div></div><div>It seemed like I'd found at least confirmation that what I was seeing was expected.</div>
<div><br></div><div>I have no idea why the <span style="background-color:rgb(255,255,255);color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px">autotools.bbclass' autoreconf wouldn't do it, though. I'll go have a quick look to see if the tree is different because I also passed it -i when I did the autoreconf.</span></div>
<div><span style="background-color:rgb(255,255,255);color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px"><br></span></div></div>-- <br>Joe MacDonald<br>:wq