This is my first Torizon build so I simply followed the steps here, link text
I went happy-path for these instructions but got this error - ERROR: Command Error: 'quilt --quiltrc /home/dave/yocto_torizon/build/tmp-torizon/work/colibri_imx7-tdx-linux-gnueabi/u-boot-toradex/1_2019.07+gitAUTOINC+4b833f0981-r0/recipe-sysroot-native/etc/quiltrc push' exited with 0 Output: Applying patch 0001-colibri_imx7-use-distro-boot-by-default.patch patching file include/configs/colibri_imx7.h Hunk #1 FAILED at 117.
I didn’t have quilt installed, so I first thought that it was simply that. But this problem persists, and I’m stuck here. Any thoughts? Thanks in advance…
What is reason to do a Torizon Core build? The main advantage of Torizon is that you can use Torizon core provided by Toradex and do all your development at container level.
As about your question what did you try Native TorizonCore Build or Containerized TorizonCore Build?
Greetings @buchmeister,
I believe this is a build issue that exists with that particular revision of the build.
Try recreating the build environment and resync the sources but instead with this command:
repo init -u https://github.com/toradex/toradex-torizon-manifest -b zeus -m integration.xml
This will cause the build to fetch sources from the tip of our zeus branch where this error should be resolved.
Though I must also ask for what purposes you are trying to build Torizon, if you could share?
Best Regards,
Jeremias
Sure, but I’ve been using Yocto for a while, so figured I’d try the instructions provided on the Toradex site…thanks for the other resources. I’ll check them out.
yeah, thanks, that worked. The build issues I saw were resolved later in the branch. We have imx7
modules in production that we built with Yocto from custom device trees and software over the past 3 years.
Now I’m diving deep into Torizon and custom containers, so I was just following the steps on the page ‘Build TorizonCore With Yocto’. Ultimately, I really need to create custom containers for Torizon.
thanks again.
Glad we were able to resolve the build issue.
We recognize Torizon approaches embedded development quite differently than it has been done traditionally. Please don’t hesitate to ask further questions on this forum if you need to.
Best Regards,
Jeremias
