<div dir="ltr">Thanks,<div><br></div><div>this will most likely fix the issue I've reported earlier in:</div><div><a href="http://lists.openembedded.org/pipermail/openembedded-core/2017-December/145278.html">http://lists.openembedded.org/pipermail/openembedded-core/2017-December/145278.html</a><br></div><div>as well.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Dec 6, 2017 at 12:28 PM, Otavio Salvador <span dir="ltr"><<a href="mailto:otavio.salvador@ossystems.com.br" target="_blank">otavio.salvador@ossystems.com.br</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello Armin,<br>
<br>
There was one patch which was mistakenly forgotten on rocko-next, and<br>
ended being merged. It ended being reworked in master and I did the<br>
needed backports/revert in our repo[1].<br>
<br>
1. <a href="https://github.com/OSSystems/oe-core/compare/rocko...rocko-next" rel="noreferrer" target="_blank">https://github.com/OSSystems/<wbr>oe-core/compare/rocko...rocko-<wbr>next</a><br>
<br>
Please consider applying those soon as rocko is currently with a<br>
broken Go toolchain.<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Otavio Salvador O.S. Systems<br>
<a href="http://www.ossystems.com.br" rel="noreferrer" target="_blank">http://www.ossystems.com.br</a> <a href="http://code.ossystems.com.br" rel="noreferrer" target="_blank">http://code.ossystems.com.br</a><br>
Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750<br>
--<br>
______________________________<wbr>_________________<br>
Openembedded-core mailing list<br>
<a href="mailto:Openembedded-core@lists.openembedded.org">Openembedded-core@lists.<wbr>openembedded.org</a><br>
<a href="http://lists.openembedded.org/mailman/listinfo/openembedded-core" rel="noreferrer" target="_blank">http://lists.openembedded.org/<wbr>mailman/listinfo/openembedded-<wbr>core</a><br>
</font></span></blockquote></div><br></div>