<p dir="ltr"></p>
<p dir="ltr">On Jul 10, 2016 2:53 AM, "Burton, Ross" <<a href="mailto:ross.burton@intel.com">ross.burton@intel.com</a>> wrote:<br>
><br>
><br>
> On 10 July 2016 at 00:27, Khem Raj <<a href="mailto:raj.khem@gmail.com">raj.khem@gmail.com</a>> wrote:<br>
>><br>
>> + local m=`uname -m`<br>
>> + if [ "$m" = "i686" -o "$m" = "i586" -o "$m" = "i486" -o "$m" = "i386" ]; then<br>
>> + echo "n";<br>
>> +- elif [ "$m" = "x86_64" ]; then<br>
>> ++ elif [ "$m" = "x86_64" -o "$m" = "aarch64" ]; then<br>
>> + echo "y";<br>
>> + else<br>
><br>
><br>
> Surely this entire block is wrong for cross-compilation - looking at uname to determine what to build for the target?</p>
<p dir="ltr">Yes it is however the recipe is limited to x86 and now that we add a non x86 build host this is a compromise I came up with. Hopefully we wont have folks adding host architectures to Build oe on so regularly. Otherwise we wont need cross compiling ;)<br>
><br>
> Ross<br></p>