-
Notifications
You must be signed in to change notification settings - Fork 11
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
Error: cpu-features Command failed when installing db-migrate #16
Comments
The important part is the last line:
As far as M1 support goes, that's still an upstream cpu_features issue, so whenever they add support for that platform, this addon will have it. |
Alternatively, you can try out the patch here and let me know if it compiles successfully for you on your M1 (make sure you check out this repository directly as it seems the version you're currently using is still relying on cmake). |
who is "they"? and support for what specifically? I definitely don't want to just see this error and have that kind of output every time I run yarn and just ignore it. But this link above also seems like a bad nightmare. Hack. I'm not using cpu-features directly, an npm package I use is, so I'm not sure what you're saying here. What exactly are you asking me to do with that patch and how? |
They = upstream = the maintainers of https://github.com/google/cpu_features
Apple Silicon CPUs
You're complaining to the wrong person. You should be contacting the yarn developers as they would generally be the ones involved with showing/hiding optional dependency installation output.
I was thinking you might possibly be interested in resolving the non-fatal error, even if you're not using it directly, by helping to test a patch that could potentially fix the error. That would require fetching/cloning the repo, applying a patch, and building locally to see if the error then is gone. I do not have Apple Silicon-based hardware to test with. However, one other user with an Apple M1 has now confirmed the patch to be working, so at this point it's less vital for someone to test the patch. For now the error will be resolved once I land the changes and whatever dependency that is using |
thank you! |
Wtf? I get this when I run
yarn
and it tries to install thenode-db-migrate
package now all of a sudden.I'm on a M1 Mac
OSX: Ventura Version 13.4.1
package.json
"db-migrate": "^0.11.12",
"db-migrate-pg": "^1.2.2",
The text was updated successfully, but these errors were encountered: