Hi Tom,
On Tue, 5 Nov 2024 at 08:44, Tom Rini trini@konsulko.com wrote:
On Tue, Nov 05, 2024 at 08:15:05AM -0700, Simon Glass wrote:
Hi Tom,
On Mon, 4 Nov 2024 at 06:56, Tom Rini trini@konsulko.com wrote:
On Mon, Nov 04, 2024 at 06:39:49AM -0700, Simon Glass wrote:
This doesn't build on arm64 at present, so drop it for now. We only expect to run sandbox tests, so perhaps it isn't needed.
Signed-off-by: Simon Glass sjg@chromium.org
tools/docker/Dockerfile | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-)
What is the build failure? Depending on what other prospects for arm64 build hardware come through I'm hoping to look harder at more build options, not just sandbox (but of course, QEMU shouldn't matter what the host is).
field-initializers -Wnonnull -Woverflow -Wvla -Wpointer-to-int-cast -Wstrict-aliasing -Wvariadic-macros -Wvolatile-register-var -Wpointer-sign -Wmissing-include-dirs -Wmissing-prototypes -Wmissing-declarations -Wformat=2 686.0 checking for aarch64-gcc... /opt/gcc-13.2.0-nolibc/aarch64-linux/bin/aarch64-linux-gcc 686.0 checking for aarch64-objcopy... /opt/gcc-13.2.0-nolibc/aarch64-linux/bin/aarch64-linux-objcopy 686.0 checking for aarch64-strip... /opt/gcc-13.2.0-nolibc/aarch64-linux/bin/aarch64-linux-strip 686.0 checking for aarch64-nm... /opt/gcc-13.2.0-nolibc/aarch64-linux/bin/aarch64-linux-nm 686.0 checking for aarch64-ranlib... /opt/gcc-13.2.0-nolibc/aarch64-linux/bin/aarch64-linux-ranlib 686.0 ./configure: line 32517: /opt/gcc-13.2.0-nolibc/aarch64-linux/bin/aarch64-linux-gcc: No such file or directory 686.1 checking which extra warnings work... 689.6 checking if compiling with clang... yes 689.8 checking for options to compile assembly... 689.8 checking whether -freg-struct-return works... no 690.0 checking for options to get soft-float... no 690.8 configure: error: could not force soft-float
I suspect it is just that the toolchains need fiddling. I'd much rather get something running and iterate on it after that.
That's the toolchain that should be used to build sandbox, so you should figure out what's going on. And I think you missed fiddling with ~/.buildman so that it sets the sandbox toolchain to the right one and not x86_64.
sandbox should be built with the host toolchain, right? The one it is complaining about is the amd64-host aarch64 toolchain, which we don't want or need yet.
The grub part (and the cross toolchains) needs more work, but we don't need it for sandbox, or at least the sandbox tests seem to pass without it. Are you wanting to run qemu on arm64 to boot grub?
I believe I've taken a reasonable stab at a good starting point for this work. Do you agree?
Regards, Simon