You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I believe in linux the following also invokes the image with a qemu setting
docker run --rm -it --platform linux/arm64 ghcr.io/eic/jug_dev:master-nightly
ROOT version
------------------------------------------------------------------
| Welcome to ROOT 6.28/04 https://root.cern |
| (c) 1995-2022, The ROOT Team; conception: R. Brun, F. Rademakers |
| Built for linuxx8664gcc on May 08 2023, 02:44:07 |
| From tags/v6-28-04@v6-28-04 |
| With g++ (Debian 12.2.0-14) 12.2.0 |
| Try '.help'/'.?', '.demo', '.license', '.credits', '.quit'/'.q' |
------------------------------------------------------------------
Installation method
spack
Operating system
Docker container on M1 Mac, inside uname -a = Linux 7163f573db33 5.15.49-linuxkit-pr #1 SMP PREEMPT Thu May 25 07:27:39 UTC 2023 x86_64 GNU/Linux
Additional context
No response
The text was updated successfully, but these errors were encountered:
The same happens for various other combinations of host and target architectures with qemu. The filename of the emulator doesn't even always include qemu (it's /usr/libexec/qemu-binfmt/aarch64-binfmt-P when emulating aarch64 on x64_64, for example)...
Check duplicate issues.
Description
Using a docker container on M1, but not optimized for M1, thisroot.sh extracts the shell name as qemu-x86_64, and consequently produces
Reason:
/proc/$$/cmdline
producesand
cut -d '' -f1
picks up the emulator, not the shell.Reproducer
I don't know where to find a lighter image, this one isn't too bad at <10 GB. On a Silicon Mac:
I believe in linux the following also invokes the image with a qemu setting
ROOT version
Installation method
spack
Operating system
Docker container on M1 Mac, inside uname -a = Linux 7163f573db33 5.15.49-linuxkit-pr #1 SMP PREEMPT Thu May 25 07:27:39 UTC 2023 x86_64 GNU/Linux
Additional context
No response
The text was updated successfully, but these errors were encountered: