Open Rinzwind opened 1 year ago
Small thing I forgot to mention, the comment in #compatibleVm
says “an image able to run the image”, that was probably intended to be “a VM able to run the image”:
Hi,
Thank you for the report!
pharo.version
file aside the image. In most cases, it won't be used.In which circumstances did you get a problem?
ps: I just fixed the comment
Ah I see: the zip files from our Jenkins server don’t include a ‘pharo.version’ file, I will add one to avoid the problem (it was reported by a colleague who had just received a new Mac).
Is it ok to close the issue?
Would it be possible to remove the dependency on Rosetta? If not, maybe the error “Bad CPU type in executable” can be handled and resignaled with a clarification that “you may need to install Rosetta 2”?
Pharo Launcher seems to depend on having Rosetta 2 installed on Apple Silicon Macs. The URLs returned by
#compatibleVmUrls
all refer to Intel-only executables. When one of these is used as the command in#imageVersionCommandWithPreferences:
, the call ofposix_spawnp
in OSSUnixSubprocess fails with errorEBADARCH
(“Error: posix_spawn(), code: 86, description: Bad CPU type in executable”) if one does not have Rosetta 2 installed (it’s not installed by default, it can be installed through the shell commandsoftwareupdate --install-rosetta
). This is not a big issue but it’s something to be aware of and it would be good to remove the dependency if possible.