<div dir="ltr">This could be caused by chromium using own bundled binutils where the version doesn't match, I've solved it in our recipe by:<div><div>+GYP_DEFINES_append = " linux_use_bundled_gold=0"</div><div>+GYP_DEFINES_append = " linux_use_bundled_binutils=0"</div></div><div><br></div><div><br></div><div>In my cases it was failing while building native libvpx (also bundled in chromium sources) when I've upgraded host binutils to</div><div>(GNU gold (GNU Binutils for Ubuntu 2.25.90.20160101) 1.11) included in Ubuntu-16.04 Alpha<br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Feb 3, 2016 at 9:21 PM, Khem Raj <span dir="ltr"><<a href="mailto:raj.khem@gmail.com" target="_blank">raj.khem@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5"><br>
> On Feb 3, 2016, at 12:09 PM, Paul Eggleton <<a href="mailto:paul.eggleton@linux.intel.com">paul.eggleton@linux.intel.com</a>> wrote:<br>
><br>
> On Wed, 03 Feb 2016 11:56:45 Khem Raj wrote:<br>
>>> On Feb 3, 2016, at 11:29 AM, Trevor Woerner <<a href="mailto:twoerner@gmail.com">twoerner@gmail.com</a>> wrote:<br>
>>><br>
>>> My chromium build is now failing due to:<br>
>>> commit 86ade2cc2553c942d9526c5323a11ae151653505<br>
>>><br>
>>> binutils: Upgrade to 2.26<br>
>>> |<br>
>>> | FAILED: x86_64-oe-linux-gcc -m64 -march=corei7 -mtune=corei7<br>
>>> | -mfpmath=sse -msse4.2<br>
>>> | --sysroot=/z/chromium-49/build/tmp-glibc/sysroots/intel-corei7-64<br>
>>> | -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed -Wl,-z,now -Wl,-z,relro<br>
>>> | -Wl,-z,defs -pthread -Wl,-z,noexecstack -fPIC<br>
>>> | -B/z/chromium-49/build/tmp-glibc/work/corei7-64-oe-linux/chromium/49.0.<br>
>>> | 2612.0-r0/chromium-49.0.2612.0/third_party/binutils/Linux_x64/Release/bi<br>
>>> | n -Wl,--disable-new-dtags -m64 -Wl,-O1 -Wl,--as-needed -Wl,--gc-sections<br>
>>> | -o chrome_sandbox -Wl,--start-group<br>
>>> | obj/sandbox/linux/suid/chrome_sandbox.process_util_linux.o<br>
>>> | obj/sandbox/linux/suid/chrome_sandbox.sandbox.o -Wl,--end-group<br>
>>> | /z/chromium-49/build/tmp-glibc/work/corei7-64-oe-linux/chromium/49.0.26<br>
>>> | 12.0-r0/chromium-49.0.2612.0/third_party/binutils/Linux_x64/Release/bin/<br>
>>> | ld: error:<br>
>>> | /z/chromium-49/build/tmp-glibc/sysroots/intel-corei7-64/usr/lib/../lib/<br>
>>> | crti.o: unsupported reloc 42 against global symbol __gmon_start__<br>
>>> | ../sysdeps/x86_64/crti.S:66: error: unsupported reloc 42<br>
>>><br>
>>> Any suggestions on how to approach this?<br>
>><br>
>> do a clean build. Its mixing objects<br>
><br>
> Should we have bumped PR somewhere to avoid this?<br>
<br>
</div></div>Don’t think so. this could happen due to new relocs appearing in glibc due to the fact<br>
thats its now compiled with newer binutils but we are still using old linker<br>
to link the app which does not understand these relocations. Why would that happen<br>
don’t know.<br>
<div class="HOEnZb"><div class="h5"><br>
><br>
> Cheers,<br>
> Paul<br>
><br>
> --<br>
><br>
> Paul Eggleton<br>
> Intel Open Source Technology Centre<br>
<br>
</div></div><br>--<br>
_______________________________________________<br>
Openembedded-core mailing list<br>
<a href="mailto:Openembedded-core@lists.openembedded.org">Openembedded-core@lists.openembedded.org</a><br>
<a href="http://lists.openembedded.org/mailman/listinfo/openembedded-core" rel="noreferrer" target="_blank">http://lists.openembedded.org/mailman/listinfo/openembedded-core</a><br>
<br></blockquote></div><br></div>