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

No ARM support (linux arm OR Mac M1/M2) #23

Closed
mariogarridopt opened this issue Dec 19, 2022 · 1 comment
Closed

No ARM support (linux arm OR Mac M1/M2) #23

mariogarridopt opened this issue Dec 19, 2022 · 1 comment

Comments

@mariogarridopt
Copy link
Contributor

mariogarridopt commented Dec 19, 2022

The project won't work on any ARM CPUs.

npm ERR! gyp: name 'mpg123_cpu' is not defined while evaluating condition 'mpg123_cpu=="arm_nofpu"' in deps/mpg123/mpg123.gyp while loading dependencies of binding.gyp while trying to load binding.gyp
npm ERR! gyp ERR! configure error 
npm ERR! gyp ERR! stack Error: `gyp` failed with exit code: 1
npm ERR! gyp ERR! stack     at ChildProcess.onCpExit (/.nvm/versions/node/v19.1.0/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:284:16)
npm ERR! gyp ERR! stack     at ChildProcess.emit (node:events:513:28)
npm ERR! gyp ERR! stack     at ChildProcess._handle.onexit (node:internal/child_process:293:12)
npm ERR! gyp ERR! System Darwin 22.1.0
npm ERR! gyp ERR! command "/.nvm/versions/node/v19.1.0/bin/node" "/.nvm/versions/node/v19.1.0/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
npm ERR! gyp ERR! cwd /.nvm/versions/node/v19.1.0/lib/node_modules/lofi-cli/node_modules/speaker
npm ERR! gyp ERR! node -v v19.1.0
npm ERR! gyp ERR! node-gyp -v v9.1.0
npm ERR! gyp ERR! not ok
@mariogarridopt mariogarridopt changed the title gyp wont work with ARM CPUs No ARM support (linux arm OR Mac M1/M2) Jan 27, 2023
@mariogarridopt
Copy link
Contributor Author

mariogarridopt commented Jan 27, 2023

Looks like the problem is related with the speaker package: https://github.com/TooTallNate/node-speaker
The package is no longer maintained, there are a bunch of issues and PR on the repo trying to fix this.

At the moment the only solution is to move away from speaker.
Or we can keep it broken until speaker decides to update.

"speaker": "^0.5.1",

-> node-speaker thread <-

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant