Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG]: #1177

Closed
favkiet opened this issue Oct 28, 2023 · 1 comment
Closed

[BUG]: #1177

favkiet opened this issue Oct 28, 2023 · 1 comment
Labels
bug Something isn't working mojo Issues that are related to mojo mojo-repo Tag all issues with this label mojo-tooling Tag for all issues related to repl, lldb, lsp, vscode extension.

Comments

@favkiet
Copy link

favkiet commented Oct 28, 2023

Bug description

Hello, when I ready to run mojo on notebook in VSCode, I got an error:
Failed to start the Kernel.
OSError: dlopen(/Users//.modular/pkg/packages.modular.com_mojo/lib/libMojoJupyter.dylib, 0x0006): tried: '/Users//.modular/pkg/packages.modular.com_mojo/lib/libMojoJupyter.dylib' (mach-o file, but is an incompatible architecture (have 'arm64', need 'x86_64')), '/System/Volumes/Preboot/Cryptexes/OS/Users//.modular/pkg/packages.modular.com_mojo/lib/libMojoJupyter.dylib' (no such file), '/Users//.modular/pkg/packages.modular.com_mojo/lib/libMojoJupyter.dylib' (mach-o file, but is an incompatible architecture (have 'arm64', need 'x86_64')).
View Jupyter log for further details.
I don't know how can fix that. I could run file mojo in Terminal smoothly but in JupyterNotebook with VSCode. Please, support to me. Thank you for everyone !!!

Steps to reproduce

  • Include relevant code snippet or link to code that did not work as expected.
  • If applicable, add screenshots to help explain the problem.
  • If using the Playground, name the pre-existing notebook that failed and the steps that led to failure.
  • Include anything else that might help us debug the issue.

System information

- What OS did you do install Mojo on ?
- Provide version information for Mojo by pasting the output of `mojo -v`
- Provide Modular CLI version by pasting the output of `modular -v`
@favkiet favkiet added bug Something isn't working mojo Issues that are related to mojo labels Oct 28, 2023
@ematejska ematejska added the mojo-tooling Tag for all issues related to repl, lldb, lsp, vscode extension. label Oct 29, 2023
@River707
Copy link
Contributor

River707 commented Nov 7, 2023

Thanks for filing! Please see #1121 and #1078 (comment) for some related information, but this is generally an indication that either:

  • on an m1 line mac, part of the mac system is running rosetta (running x86_64 instead of arm64)
  • you're on an intel variant Mac, these are currently unsupported by the Mojo install

@River707 River707 closed this as completed Nov 7, 2023
@ematejska ematejska added the mojo-repo Tag all issues with this label label May 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working mojo Issues that are related to mojo mojo-repo Tag all issues with this label mojo-tooling Tag for all issues related to repl, lldb, lsp, vscode extension.
Projects
None yet
Development

No branches or pull requests

3 participants