<div dir="ltr">> <span style="font-size:12.8px">Can individual recipes choose to be built using the normal ld?</span><div class="gmail-yj6qo gmail-ajU" style="font-size:12.8px"></div><div><span style="font-size:12.8px"><br></span></div><div><span style="font-size:12.8px">yes, see example in:</span></div><div><span style="font-size:12.8px">meta/recipes-bsp/u-boot/u-boot.inc</span><br></div><div><span style="font-size:12.8px">meta/recipes-support/libunwind/<a href="http://libunwind_git.bb">libunwind_git.bb</a></span><br></div><div><span style="font-size:12.8px"><br></span></div><div><span style="font-size:12.8px">but it was working with older binutils, so maybe worth tracking down where it got borken.</span></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Mar 29, 2017 at 11:38 AM, Patrick Ohly <span dir="ltr"><<a href="mailto:patrick.ohly@intel.com" target="_blank">patrick.ohly@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 Wed, 2017-03-29 at 11:14 +0200, Martin Jansa wrote:<br>
> On Wed, Mar 29, 2017 at 10:35:23AM +0200, Patrick Ohly wrote:<br>
> > On Wed, 2017-03-29 at 09:23 +0200, Martin Jansa wrote:<br>
> > > INFO: jenkins-job.sh-1.8.19 Complete log available at <a href="http://logs.nslu2-linux.org/buildlogs/oe/world/pyro/log.report.20170328_014155.log" rel="noreferrer" target="_blank">http://logs.nslu2-linux.org/<wbr>buildlogs/oe/world/pyro/log.<wbr>report.20170328_014155.log</a><br>
> ><br>
> > That used OE-core 552bd78, if I read this right:<br>
> ><br>
> > == Tested changes (not included in master yet) - openembedded-core ==<br>
> > latest upstream commit:<br>
> > 552bd78 wic: use kernel_dir to find systemd-efi bootloader<br>
> ><br>
> > > * openembedded-core/meta/<wbr>recipes-core/ovmf/<a href="http://ovmf_git.bb">ovmf_git.bb</a>:<wbr>do_compile<br>
> ><br>
> > <a href="http://errors.yoctoproject.org/Errors/Details/135202/" rel="noreferrer" target="_blank">http://errors.yoctoproject.<wbr>org/Errors/Details/135202/</a><br>
> ><br>
> > "gcc-ar: not found" - that should have been fixed by OE-core 23a12d87a6<br>
> > "fix toolchain selection", which is included in OE-core 552bd78 and thus<br>
> > should have been included in the build.<br>
> ><br>
> > However, the error above was "Submitted on: 11/03/17 10:13", which was a<br>
> > while ago and in particular before that fix.<br>
> ><br>
> > Did ovmf really fail in the latest world build?<br>
><br>
> The report shows:<br>
> <a href="http://errors.yoctoproject.org/Errors/Build/34933/" rel="noreferrer" target="_blank">http://errors.yoctoproject.<wbr>org/Errors/Build/34933/</a><br>
> which leads to:<br>
><br>
> <a href="http://errors.yoctoproject.org/Errors/Details/138261/" rel="noreferrer" target="_blank">http://errors.yoctoproject.<wbr>org/Errors/Details/138261/</a><br>
> Submitted on: 27/03/17 05:31<br>
<br>
</span>Got it. I followed the wrong link at some point.<br>
<span class=""><br>
> So yes it failed again, but this time with different error:<br>
> TOPDIR/tmp-glibc/work/i586-oe-<wbr>linux/ovmf/git-r0/recipe-<wbr>sysroot-native/usr/bin/i586-<wbr>oe-linux/../../libexec/i586-<wbr>oe-linux/gcc/i586-oe-linux/6.<wbr>3.0/ld:<br>
> internal error in do_layout, at ../../gold/object.cc:1821<br>
<br>
</span>Hmm, internal error in gold. Not sure what to do about that :-/<br>
<br>
Can individual recipes choose to be built using the normal ld?<br>
<div class="HOEnZb"><div class="h5"><br>
--<br>
Best Regards, Patrick Ohly<br>
<br>
The content of this message is my personal opinion only and although<br>
I am an employee of Intel, the statements I make here in no way<br>
represent Intel's position on the issue, nor am I authorized to speak<br>
on behalf of Intel on this matter.<br>
<br>
<br>
<br>
</div></div></blockquote></div><br></div>