<div dir="ltr"><div class="gmail_extra">Hi Maxin,</div><div class="gmail_extra"><br></div><div class="gmail_extra"><div class="gmail_quote">On 2 December 2015 at 07:56, Maxin B. John <span dir="ltr"><<a href="mailto:maxin.john@intel.com" target="_blank">maxin.john@intel.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div id=":9nz" class="" style="overflow:hidden">Moving libjpeg-turbo from meta-oe as a replacement for libjpeg<br>
package. libjpeg-turbo has same API/ABI as libjpeg. It is<br>
relatively faster in <span class="">JPEG</span> compression/decompression than libjpeg.<br></div></blockquote></div><br>As jpeg-turbo has assembler bits it's getting all confused about x32:</div><div class="gmail_extra"><br></div>| checking if we have SIMD optimisations for cpu type... yes (x86_64)<div>| checking for nasm... nasm</div><div>| checking for object file format of host system... ELF64</div><div>| checking for object file format specifier (NAFLAGS) ... -felf64 -DELF -D__x86_64__</div><div>| checking whether the assembler (nasm -felf64 -DELF -D__x86_64__) works... yes</div><div>| checking whether the linker accepts assembler output... no</div><div>| configure: error: configuration problem: maybe object file format mismatch.</div><div><br></div><div>(<a href="https://autobuilder.yoctoproject.org/main/builders/nightly-x32/builds/545">https://autobuilder.yoctoproject.org/main/builders/nightly-x32/builds/545</a>)</div><div><br></div><div>Ross</div></div>