<div>Solved, updating bitbake to commit <a href="http://cgit.openembedded.org/bitbake/commit/?id=3d8044bc79c482c5ea008ddf12a8128dcd1527ee">3d8044bc79c482c5ea008ddf12a8128dcd1527ee</a> solved the issue.</div><div>Since now I've worked against the commit <a href="http://cgit.openembedded.org/bitbake/commit/?id=6acd444a557bba977ae1772371fdadf5f510e3b6">6acd444a557bba977ae1772371fdadf5f510e3b6</a>, which indicates the new 1.19.1 version.</div>
<div> </div><div>Thanks,</div><div>Giuseppe<br></div><div class="gmail_quote">2013/6/25 Giuseppe Condorelli <span dir="ltr"><<a href="mailto:giuseppe.condorelli@gmail.com" target="_blank">giuseppe.condorelli@gmail.com</a>></span><br>
<blockquote style="margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid" class="gmail_quote"><div>Hi All,</div><div> </div><div>I'm working with the best so far master openembedded-core repository plus the bitbake version 1.19.1</div>
<div>Using the external toolchain csl I'm in trouble because it seems the latest modification in the csl-versions.inc</div>
<div>breaks the csl_get_version routine. I mean, it is not able to find the gcc version due to wrong binary name:</div><div>it doesn't attach the TARGET_PREFIX so it finds for gcc only (failing).</div><div>The issue seems located to the csl_versions_handler routine, backporting it solves the issue.</div>
<div> </div><div>Please can you look at that routine and let me know if I'm wrong in something?</div><div> </div><div>Cheers,</div><div>Giuseppe</div>
</blockquote></div><br>