<div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Nov 14, 2012 at 6:01 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">> The reason for this failure has to do with a particular set of<br>
> circumstances. A header in the bash source tree defines STRING() based<br>
> on HAVE_STRINGIZE. This define overwrites the unistd.h define of the<br>
> same macro. The unistd.h definitions of read() and open() wrap the<br>
> call to the real functions to implement FORTIFY_SOURCES, and those<br>
> wrappers use STRING() to do it. As a result, for any host that<br>
> defaults to -DFORTIFY_SOURCES, STRING() returns 'x' resulting in a<br>
> concatenation rather than an assembly level rename of the function<br>
> being called.<br>
><br>
> If we add -DHAVE_STRINGIZE in the CROSS_COMPILE case, then STRING()<br>
> will be defined to something useful, and therefore the FORTIFY_SOURCES<br>
> wrappers don't get hosed.<br>
><br>
> See <a href="http://git.yoctoproject.org/cgit/cgit.cgi/meta-mentor/commit/?id=da0ff91" target="_blank">http://git.yoctoproject.org/cgit/cgit.cgi/meta-mentor/commit/?id=da0ff91</a> for an alternative fix which may be more likely to be accepted upstream.<br>
><br>
</div>This is better, yes. Is there a reason this is in meta-mentor and not<br>
OE-Core? I'd really like to pull it into OE-Core...</blockquote></div><br>Nope, it's just in the pending upstream pile. I'll send a patch against oe-core to the list today if you'd like.<br>-- <br>Christopher Larson<br>
</div>