Other Parts Discussed in Thread: AM62P
Dear Ti
we use yocto builds AM62P
But when we build bitbake tisdk-default-image there are some errors
there are bitbake log
This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Dear Ti
we use yocto builds AM62P
But when we build bitbake tisdk-default-image there are some errors
there are bitbake log
gcc_log.do_compile.txtopengl-es-cts_log.do_compile.txtnodejs_log.do_compile.txtvulkan-cts_log.do_compile.txt
DEBUG: Executing shell function do_compile go: github.com/gorilla/websocket@v1.4.0: Get "https://proxy.golang.org/github.com/gorilla/websocket/@v/v1.4.0.mod": dial tcp 142.251.43.17:443: i/o timeout go: downloading github.com/gorilla/websocket v1.4.0 go: github.com/gorilla/websocket@v1.4.0: Get "https://proxy.golang.org/github.com/gorilla/websocket/@v/v1.4.0.mod": dial tcp 142.251.43.17:443: i/o timeout go: github.com/gorilla/websocket@v1.4.0: Get "https://proxy.golang.org/github.com/gorilla/websocket/@v/v1.4.0.mod": dial tcp 142.251.43.17:443: i/o timeout go: downloading github.com/gorilla/websocket v1.4.0 go: github.com/gorilla/websocket@v1.4.0: Get "https://proxy.golang.org/github.com/gorilla/websocket/@v/v1.4.0.mod": dial tcp 142.251.43.17:443: i/o timeout WARNING: exit code 1 from a shell command.
This recipe is trying to use the network connection during the 'compile' phase, and sometimes this causes issues especially when the computer is behind a proxy or firewall.
Can you please double check you have the `http_proxy` and `https_proxy` environmental variables set?
You can see from this commit here how the recipe is trying to utilize those network proxy ENV settings.
websocketd: enable network access for compile task
https://git.ti.com/cgit/arago-project/meta-arago/commit/?h=kirkstone&id=29ef988fae74cd26c418d0e728f757b3c26f23da
Also what you can try is building on a computer that's directly connected to the internet (not behind firewall, etc.).
Regards, Andreas
Dear Andreas Dannenberg
Now we bitbake -c compile opengl-es-cts
there are some errors , there is the log
This could be an out-of-memory error, which affected the compilation. Try this:
MACHINE=am62pxx-evm bitbake -c cleanall
Try reducing the parallelism of the Yocto build which will greatly reduce strain on your build environment (esp. RAM), see BB_NUMBER_THREADS and PARALLEL_MAKE in conf/local.conf, try setting those to 4 for both settings, or even lower.
Regards, Andreas