Open tamasgal opened 2 years ago
I currently don't have an M1 machine so I cannot really debug and test this.
@tamasgal I am probably also running in an ARM compatibility problem. Have you found some solutions for your case=
I guess the default compile options for the sysimage are leading to incorrect behaviour when run on ARM. (I am running on Ampere Altra). My error is however completely different:
exec /usr/local/julia/bin/julia: exec format error
nevertheless, maybe you have some tips what to try for getting sysimages on ARM to work
Sorry I don't have any hint. I gave up after a while and did not use sysimages on my M1.
Actually with Julia 1.8 and 1.9-rc* I am very happy with the load times (for development, prototyping and high-level analysis) and for HPC I don't need M1 sysimages anyways.
@KristofferC do you have some general tips about which compile flags to use for compiling sysimages which are arm friendly?
I am running Julia 1.6.2 (x64 mode with Rosetta 2) and having problems with
PackageCompiler.jl
.I get warnings like
attempting to link with file built for macOS-x86_64
and when using the generatedsysimage.so
, it tries to loadsysimage.so.dylib
which is not present. I don't know why it puts.dylib
at the end (which would be the standard library file extension on macOS).Btw. it was working fine a few days ago and I have no idea what happened or when it eventually broke...
Here is how I build and use the sysimage (which still works nicely on the CI using Linux on x86):
I then changed the name of the system image from
sysimage.so
tosysimage.dylib
which got rid of the file-naming issue, but then I get awrong architecture
message since it attempts to build formacOS-arm64
and link withmacOS-x86_64
:I am a bit puzzled why this worked before and not now, so asking for help. Maybe someone has a hint how to deal with this arch-issue
;)
I still cannot use
Julia 1.7 for ARM (M-series)
since a few crucial packages are not available due to missing binary dependencies (e.g.HDF5.jl
)