-
Hi, We updated our meta-tegra layer from commit 387d97e to branch dunfell-l4t-r32.5.0. When we went to build our Yocto image, bitbake ran into the following error when parsing recipes: [mbilloo@mbilloo-blues build]$ bitbake custom-image-base Can anybody point to what we're doing wrong? Thanks |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 2 replies
-
I think this is the hint that you need the instructions in https://github.com/OE4T/meta-tegra/wiki/L4T-R32.3.1-Notes#sdk-manager-downloads-required to setup the devnet mirror for cuda host tool binaries. I've setup a new page at https://github.com/OE4T/meta-tegra/wiki/NVIDIA_DEVNET_MIRROR-and-SDK-Manager to document the fact that we still need this for CUDA host tool content, until we can take this off the L4T Integration issues list at https://github.com/OE4T/meta-tegra/wiki/L4T-Integration-Issues with help from nvidia. |
Beta Was this translation helpful? Give feedback.
-
The earlier commit you mention was for L4T R32.4.3, and now you've upgraded to R32.5.0. One of the changes in the update is that NVIDIA has released sources for several of the Gstreamer plugins that used to be binary-only, and the layer has been updated to build them from source. Some of those plugins use CUDA, though, which is why they now have a dependency on the CUDA host-side tools, where they didn't before. |
Beta Was this translation helpful? Give feedback.
-
Thanks! I ended up just removing the gstreamer plugin that was causing this trouble as a dependency in our final build image. |
Beta Was this translation helpful? Give feedback.
The earlier commit you mention was for L4T R32.4.3, and now you've upgraded to R32.5.0. One of the changes in the update is that NVIDIA has released sources for several of the Gstreamer plugins that used to be binary-only, and the layer has been updated to build them from source. Some of those plugins use CUDA, though, which is why they now have a dependency on the CUDA host-side tools, where they didn't before.