If the uninative link is set from a file URL, a symlink will be created. If that file is later deleted (i.e. referenced a file in another project layer).
The system will fail on a backtrace during the os.symlink. The same type of problem must have existed in the bitbake fetcher, as the code there was already written to allow this case. This copies that design and does the same procedure of checking for a broken symlink, and unlinks in that case. This also adds the secondary step if there are two processes that happen to get to there at the same time (shared DL_DIR for two projects), the exitence of the link will not trigger a failure due to the try/except. Mark Hatle (1): uninative.bbclass: Fix broken symlink issue meta/classes/uninative.bbclass | 12 ++++++++++++ 1 file changed, 12 insertions(+) -- 2.14.2.666.gea220ee -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core