Skip to main content
debugging
Lead
September 24, 2025
Solved

STM32MP257F-DK Building Yocto with docker fails for SDK at glibc

  • September 24, 2025
  • 1 reply
  • 541 views

 

 bitbake st-image-weston -c populate_sdk 

This works without the populate-sdk option

with the SDK an python error occurs

I can't find a way to get around this by cleanstate or clean glibc.

Attached the log.

Then did:

bitbake -ccleansstate glibc-locale

bitbake glibc-locale 

which  went fine (see attachment)

but then the build failed again with the same error

 

 

Best answer by debugging

Deleted the repo and started the build all over again. Now the SDK and Weston image are all successfully build. it takes about 160GB. This after about 4 to 5 errors that could be recovered from with cleanall. Attached the result. There are a few warnings.  Question remains, how to recover from failures as in this post that could not be recovered from ? Perhaps ST can dedicate a wiki about such Yocto issues (assuming engineered have encountered these as well (they may have a knowledge base).

1 reply

debugging
debuggingAuthorBest answer
Lead
September 26, 2025

Deleted the repo and started the build all over again. Now the SDK and Weston image are all successfully build. it takes about 160GB. This after about 4 to 5 errors that could be recovered from with cleanall. Attached the result. There are a few warnings.  Question remains, how to recover from failures as in this post that could not be recovered from ? Perhaps ST can dedicate a wiki about such Yocto issues (assuming engineered have encountered these as well (they may have a knowledge base).