8000 Bad CPU type in executable macos_odoo_ls_server · Issue #308 · odoo/odoo-ls · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Bad CPU type in executable macos_odoo_ls_server #308

New issue

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

Sign up for GitHub

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

Jump to bottom
Open
Yorften opened this issue Apr 28, 2025 · 1 comment
Open

Bad CPU type in executable macos_odoo_ls_server #308

Yorften opened this issue Apr 28, 2025 · 1 comment
Assignees
@fda-odoo
Labels
packaging Related to packaging

Comments

@Yorften
Copy link
Yorften commented Apr 28, 2025

Your setup
Version: 0.6.2
Operating System: MacOS Ventura (Intel-based iMac)
IDE / Integration:** VS Code – official Odoo Language Server extension

Describe the bug
When running the Odoo Language Server on an Intel-based macOS machine, the bundled macos_odoo_ls_server binary fails to launch with a CPU‐architecture mismatch. The output in the “Odoo Language Server” panel reads:
Error: spawn Unknown system error -86 at ChildProcess.spawn (node:internal/child_process:420:11) at Object.spawn (node:child_process:796:9) at /Users/karizma/.vscode/extensions/odoo.odoo-0.6.2/client/out/main.js:113:32891 at async Dh.createConnection (/Users/karizma/.vscode/extensions/odoo.odoo-0.6.2/client/out/main.js:113:12653) at async Dh.start (/Users/karizma/.vscode/extensions/odoo.odoo-0.6.2/client/out/main.js:113:2940)

macOS reports “bad CPU type in executable” (EF_BADARCH, error code –86), indicating the shipped binary is compiled for ARM64 rather than x86_64.

To Reproduce

  1. On an Intel-based Mac running macOS Ventura, install the Odoo Language Server extension v0.6.2 in VS Code.
  2. Clone or open any Odoo 18.0 codebase folder.
  3. Ensure your Python interpreter is set to a valid Odoo-18.0 virtual environment.
  4. Reload VS Code or open the workspace; the extension will attempt to spawn the odoo-ls server.
  5. Observe the spawn failure and the “Unknown system error –86” in the extension output.

Expected behavior
The Odoo Language Server should launch without any problems

Screenshots
Image

Additional context
I configured odoo-ls with a cloned odoo 18.0 and a python venv.
@fda-odoo fda-odoo added the packaging Related to packaging label Apr 28, 2025
@fda-odoo fda-odoo self-assigned this Apr 28, 2025
@fda-odoo
Copy link
Collaborator

Hello,
Actually we are only packaging on some platforms for each OS.
On macos, we only compile it for ARM64 right now, because it is our development setup.
We still have to setup a full crosscompilation setup for each platform, and we will do that before the official release of course.
Before that, you can stilll compile the code yourself (clone the repository, launch "cargo --build -r", then copy and rename the produce executable (target/release/odoo_ls_server) to your extension installation (something like $HOME/.vscode/extension/odoo/mac_odoo_ls_server).
Unfortunately that's the only way to use the extension for now on this platform/os.
If you need help to build the executable, do not hesitate to ask here, I would be glad to help you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@fda-odoo fda-odoo

Labels
packaging Related to packaging
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@fda-odoo @Yorften
0