I'm trying to use babashka to automate a graalvm native build during development but I am getting this error.

"Warning: Ignoring server-mode native-image argument --no-server.\nError: Darwin native toolchain (x86_64) implies native-image target architecture class jdk.vm.ci.amd64.AMD64 but configured native-image target architecture is class jdk.vm.ci.aarch64.AArch64.\nError: To prevent native-toolchain checking provide command-line option -H:-CheckToolchain\ncom.oracle.svm.core.util.UserError$UserException: Darwin native toolchain (x86_64) implies native-image target architecture class jdk.vm.ci.amd64.AMD64 but configured native-image target architecture is class jdk.vm.ci.aarch64.AArch64.\nTo prevent native-toolchain checking provide command-line option -H:-CheckToolchain\n\tat com.oracle.svm.core.util.UserError.abort(UserError.java:138)\n\tat com.oracle.svm.hosted.c.codegen.CCompilerInvoker.addSkipCheckingInfo(CCompilerInvoker.java:104)\n\tat com.oracle.svm.hosted.c.codegen.CCompilerInvoker.verifyCompiler(CCompilerInvoker.java:95)\n\tat com.oracle.svm.hosted.NativeImageGenerator.setupNativeImage(NativeImageGenerator.java:884)\n\tat com.oracle.svm.hosted.NativeImageGenerator.doRun(NativeImageGenerator.java:555)\n\tat com.oracle.svm.hosted.NativeImageGenerator.run(NativeImageGenerator.java:515)\n\tat com.oracle.svm.hosted.NativeImageGeneratorRunner.buildImage(NativeImageGeneratorRunner.java:407)\n\tat com.oracle.svm.hosted.NativeImageGeneratorRunner.build(NativeImageGeneratorRunner.java:585)\n\tat com.oracle.svm.hosted.NativeImageGeneratorRunner.main(NativeImageGeneratorRunner.java:128)\n\tat com.oracle.svm.hosted.NativeImageGeneratorRunner$JDK9Plus.main(NativeImageGeneratorRunner.java:615)\nError: Image build request failed with exit status 1\n"}

Is there something funny with how this happens with Babashka or is it something on my end?

When I run the same shell command it works. Hence a little confused.

I see some error about mixing aarch64 and amd64

Yea I see that as well. I was thinking that somehow Babashka is confusing it by being the one that invokes the command. I'm basically finding where graalvm native image is installed on the dev machine and then calling it with the commands. We have a lot of build steps and this is probably the trickiest to automate on local machine.

I am on an M1 Mac if that clarifies anything

@grounded_sage Would a m1 binary of bb help?

no idea

if you go here: https://cirrus-ci.com/task/5967226598588416 and then to artifacts / binaries, you should be able to download a bb binary I just got this working 1 minute ago!