<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Thu, Jan 19, 2017 at 8:32 AM, Wold, Saul <span dir="ltr"><<a href="mailto:saul.wold@intel.com" target="_blank">saul.wold@intel.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Thu, 2017-01-05 at 12:46 -0700, Christopher Larson wrote:<br>
> From: Christopher Larson <<a href="mailto:chris_larson@mentor.com">chris_larson@mentor.com</a>><br>
><br>
> We're targeting the x86_64 EFI ABI.<br>
><br>
</span>Chris, <br>
<br>
Firstly, thanks for all the x32 patches!<br>
<br>
I tried to build gnu-efi for x32 via genericx86-64 and still got a<br>
failure about missing the gnu/stubs-64.h. I am building pure x32, is it<br>
possibly you build x32 in a TMPDIR that already had a 64bit build?<br>
<br>
There is a generated stubs-x32.h, but not the required -64 variant.<br>
<br>
Can you confirm this builds correctly?</blockquote></div><br>I'm building x32-only, but admittedly 90% of my builds are with an external toolchain, so any bugs in the build of the toolchain obviously wouldn't be encountered in that case. I suspect that's what's happening here, so this would be a new issue to dive into.<br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr">Christopher Larson<br>kergoth at gmail dot com<br>Founder - BitBake, OpenEmbedded, OpenZaurus<br>Senior Software Engineer, Mentor Graphics</div></div></div></div>
</div></div>