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
As discussed on emscripten-core/emscripten#21989 (comment) I am creating an issue related to emsdk install tot failing on docker running in Mac M2 under arch aarch64 (uname -m). Interestingly it works on x86_64 (via shell.cloud.google.com).
I believe I am on the very latest emsdk (4205979 today 2024-05-29) and releases are pulled against 61b6a2eb which is from 2024-05-29 (today). Am I doint anything wrong?
root@c72f63f99f92:/ffmpeg-wasm/modules/emsdk# git status
HEAD detached at 4205979
nothing to commit, working tree clean
root@c72f63f99f92:/ffmpeg-wasm/modules/emsdk# emsdk install tot
Fetching latest changes to the branch/tag 'main' for '/ffmpeg-wasm/modules/emsdk/releases'...
refs/heads/main
Updating e43446a5..61b6a2eb
Fast-forward
DEPS | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
Successfully updated and checked out branch/tag 'main' on repository '/ffmpeg-wasm/modules/emsdk/releases'
Current repository version: "Wed, 29 May 2024 21:12:22 +0000 61b6a2eba1dc0392a1309a2cd5dbfa82113dfd41"
error: failed to find build of any recent emsdk revision
The text was updated successfully, but these errors were encountered:
I am not sure what it is or how to do that. Can you please take it from here instead, I am sure this will be even faster to resolve on your side. If you do not have access to aarch64 platform, docker --platform linux/arm64 should be helpful.
As discussed on emscripten-core/emscripten#21989 (comment) I am creating an issue related to
emsdk install tot
failing on docker running in Mac M2 under arch aarch64 (uname -m
). Interestingly it works on x86_64 (via shell.cloud.google.com).I believe I am on the very latest emsdk (4205979 today 2024-05-29) and releases are pulled against 61b6a2eb which is from 2024-05-29 (today). Am I doint anything wrong?
The text was updated successfully, but these errors were encountered: