<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Apr 15, 2013 at 9:45 PM, Bruce Ashfield <span dir="ltr"><<a href="mailto:bruce.ashfield@windriver.com" target="_blank">bruce.ashfield@windriver.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Richard,<br>
<br>
As was reported on the oe-core mailing list earlier today, custom<br>
BSPs (other than the ones generated by the BSP tooling) that relied<br>
on generated BSP descriptions started failing.<br>
<br>
I did the following one line patch to fix them.<br>
<br>
Updating the SCRCREV to pick up the following fix<br>
<br>
updateme: use absolute path for generated BSP descriptions<br>
<br>
When a custom BSP is used, a top level BSP is generated by the tools and fed<br>
to the build system just as a user defined BSP would be located and<br>
passed. The location of the generated file is placed in the top_tgt file,<br>
which is used by subsequent stages. A relative path was being placed into<br>
top_tgt, which binds the build to a particular directory structure and<br>
working directory.<br>
<br>
The location of parts of the build have changed, and this relative path is<br>
no longer accurate. Changing it to an absolute path solve the build issues<br>
related to custom BSPs.<br>
<br>
There's no risk to existing kernels, or built binary images. The<br>
only thing that runs this code is BSP generation routines that are<br>
triggered by linux-yocto-custom.<br>
<br>
If there's any room in 1.4, this one-line would be a good idea!<br></blockquote><div><br></div><div style>As Bruce states that there's no risk for existing kernels, I hope that you'll take this one, as linux-yocto-custom currently is broken (at least when using it together with only a defconfig).</div>
<div style><br></div><div style>Cheers,</div><div style>Anders </div></div><div><br></div>-- <br>Anders Darander<br>EPO guidelines 1978: "If the contribution to the known art resides<br>solely in a computer program then the subject matter is not<br>
patentable in whatever manner it may be presented in the claims."
</div></div>