Skip to content

[Apple M1] Process failed to start #59

Open

Description

@arthurbailao

I'm getting the following error:

E903: Process failed to start: Unknown system error -86: "/Users/arthurbailao/.local/share/nvim/lazy/nvim-ghost.nvim/nvim-ghost-binary"

Executing the binary directly, I got this:

exec: Failed to execute process './nvim-ghost-binary': Bad CPU type in executable.

Using a Apple M3 Pro.

Activity

  1. subnut commented on Feb 25, 2024

    @subnut
    Owner

    Sorry. You could use the plugin in this way until the issue is resolved -
    https://github.com/subnut/nvim-ghost.nvim?tab=readme-ov-file#other-operating-systems

    The binary being executed is built by GitHub Action runners, which run on Intel. It seems, as of now there are no ARM-based GitHub runners unfortunately.

    EDIT: Apparently there's macos-14 runner in beta, and it runs on M1.

  2. added
    help wantedExtra attention is needed
    bugSomething isn't working
    needs designWe haven't thought yet how we'd go about fixing this issue
    and removed
    help wantedExtra attention is needed
    on Feb 25, 2024
  3. arthurbailao commented on Feb 29, 2024

    @arthurbailao
    Author

    I can try to send a PR adding this runner to the CI matrix. What do you think?

    EDIT: You suggestion worked!

  4. changed the title [-]Process failed to start[/-] [+][Apple M1] Process failed to start[/+] on May 8, 2024
  5. added this to the v0.6 milestone on Jun 6, 2024
  6. galfonso99 commented on Mar 6, 2025

    @galfonso99

    Sorry for posting on an old issue. I want to share that I experience this exact same problem on an Intel Macbook. Feel free to ask me any following questions if needed. I wonder if this extension has ever worked on Mac Os using neovim since that is not a common combination

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingneeds designWe haven't thought yet how we'd go about fixing this issue

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions