On Mon, Apr 15, 2013 at 9:45 PM, Bruce Ashfield < bruce.ashfi...@windriver.com> wrote:
> Richard, > > As was reported on the oe-core mailing list earlier today, custom > BSPs (other than the ones generated by the BSP tooling) that relied > on generated BSP descriptions started failing. > > I did the following one line patch to fix them. > > Updating the SCRCREV to pick up the following fix > > updateme: use absolute path for generated BSP descriptions > > When a custom BSP is used, a top level BSP is generated by the > tools and fed > to the build system just as a user defined BSP would be located and > passed. The location of the generated file is placed in the top_tgt > file, > which is used by subsequent stages. A relative path was being > placed into > top_tgt, which binds the build to a particular directory structure > and > working directory. > > The location of parts of the build have changed, and this relative > path is > no longer accurate. Changing it to an absolute path solve the build > issues > related to custom BSPs. > > There's no risk to existing kernels, or built binary images. The > only thing that runs this code is BSP generation routines that are > triggered by linux-yocto-custom. > > If there's any room in 1.4, this one-line would be a good idea! > 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). Cheers, Anders -- Anders Darander EPO guidelines 1978: "If the contribution to the known art resides solely in a computer program then the subject matter is not patentable in whatever manner it may be presented in the claims."
_______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
