I pulled V5.4.0 of Torizoncore in an attempt to bitbake it -
There’s nothing added/appended to it (although I need Java appended to it ultimately).
I got passed a few ‘Fetcher failure for URL’ failures, but got stuck on this -
'Can’t open perl script “/home/dave/yocto_torizon_imx8_5.4.0/build/tmp/work/aarch64-tdx-linux/openssl/1.1.1k-r0/build/configdata.pm”: No such file or directory
Please let me know how I can track this down?
Hi @buchmeister ,
We’re going to need more information on your side to better understand what’s going on.
Taking a quick look at the OpenSSL repo it seems that
configdata.pm is generated as part of the configuration process before compilation, so there could be another previous error that causes the
No such file or directory message.
Do you have a particular reason for trying to build TorizonCore instead of using one of our releases, specifically version 5.4.0 instead of the latest quarterly version (5.6.0 at this time)?
yeah, I’ve been doing Yocto builds for a while now for our production deploys, and for Torizon I also followed these for a native build (simpler). So I had all the expected software and utilities on my host machine.
I’m new to Torizon:
- we need java, so I figured I needed a jdk built into a custom image
- is the workflow just to take a stock image and modify it with TorizonCore Builder?
If I don’t have to build it I won’t.
20220624174835.log (3.7 KB)
run.do_configure.32136 (10.5 KB)
With TorizonCore we recommend running applications inside containers. Do you intend to run an application that needs Java?
If so you can create a container with JRE/JDK installed and then run your program inside it. For instance, if using a Debian container you can just install Java via
- You create a container that has your application and all of its dependencies;
- TorizonCore will run the container.
This means that you don’t usually need to install packages in TorizonCore itself or modify it directly, except if changing something like a Kernel option, in which case it is necessary to build a custom image using Bitbake/Yocto.
This article in our developer page has more details regarding my explanation:
I hope this made things clearer for you.
Thanks Lucas, this makes sense and that was initially the path I was going down. Instead of apt install on the jdk, I created a multi-stage dockerfile by adding a 2nd FROM command (‘FROM arm32v7/openjdk:8’) in addition to the original (‘FROM torizon/arm32v7-debian-base’).
A multi-stage dockerfile should also work well. Glad you managed to work through this.
Let me know if you have any other questions.