ARM64 image builds, but file is nowhere to be found?

[JohannesNeu]

Hi,
I ran opnsense tools "make arm DEVICE=ARM64 |& tee makearmcompile.log" on an ec2 instance and it seems to work after freebsd patched a gdb bug, yay!

The logs show that everything should be fine and I should be able to find the image file at: "/usr/obj/usr/tools/config/22.1/OpenSSL:aarch64/efiboot.img", but when I go there, then there is no file :-(

Any ideas what may cause this? I could not find any meaningful errors or warnings in the attached log
makearmcompile.log
.

[fichtner]

That’s not the image. The image is available in the corresponding images dir with appropriate name…

[JohannesNeu]

Thanks for the hint! I shut down the ec2 instance, but I am cross compiling right now. I check once it is done and close the ticket if it worked :-)

[fichtner]

I can fix the display issue a little, but that's about it :)

[JohannesNeu]

I got it working and ran into another error, but I think this one is definitely not due to the build tools :-D

Thanks for the advice and help! The target is shown as IMAGEDIR in the build process and I assume you can change it using IMAGEDIR= as an option just as DEVICE.

I was able to build it and think we might remove the blacklisting for icinga2.
If we want to make it easier we might add something like echo "the files are here: " $IMAGEDIR to the end?

[fichtner]

IMAGESDIR can't be set, but it's very well documented in our 2-step build tutorial: https://github.com/opnsense/tools#tldr