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

Describe another failure case for installing node versions from source on mac arm64 machines #2653

Merged
merged 1 commit into from
Nov 19, 2021

Conversation

igrayson
Copy link
Contributor

Describe another failure case for installing node versions from source on mac arm64 machines.

It seems to be related to nodejs/node#39313 (which describes a similar issue).

…rom source on mac arm64 machines.

It seems to be related to nodejs/node#39313 (which describes a similar issue).
@igrayson igrayson changed the title Update README.md Describe another failure case for installing node versions from source on mac arm64 machines Nov 15, 2021
@ljharb
Copy link
Member

ljharb commented Nov 15, 2021

This change doesn’t explain how one can solve it nor where one can look to track a solution.

@igrayson
Copy link
Contributor Author

igrayson commented Nov 19, 2021

That's correct, it doesn't.

The other 'Some issues you may encounter' above this in the README also do not track a solution.

And the "solution" immediately below this in the README also applies to this issue.

Copy link
Member

@ljharb ljharb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fair enough

@ljharb ljharb merged commit e9b2693 into nvm-sh:master Nov 19, 2021
@lukelafountaine
Copy link
Contributor

FWIW, this comment is misleading. The "solution" that follows this new line in the README does not apply to the addition found in this PR. This comment in the related issue mentions that problem described does not appear with arm64 but does appear with x64. So trying to install with using the x64 architecture actually induces the problem described in this PR. I just spent several hours trying and retrying variations the solution mentioned here, but I found the line added in this PR unhelpful because it led me to believe that the following lines would help me, when they really didn't.

I was experiencing what is described in this PR, (after nvm successfully compiles some versions, npm may later fail to install packages with an incorrect data check error). This was caused by what's described in this issue.

For any others that come across this, the workaround that I ended up using to successfully install an older version of Node (Node 12.22.1) was pretty much stolen from this commit in pkg-fetch. I changed this line to the following:

ADDITIONAL_PARAMETERS='--shared-zlib'

After that, I could npm i without issues.

@ljharb
Copy link
Member

ljharb commented Nov 30, 2021

@lukelafountaine i'd be happy to accept PRs with further improvements.

@convenient
Copy link

A third kind of error that may or may not be worth documenting?

      # ERR! sharp Prebuilt libvips binaries are not yet available for darwin-arm64v8
      # info sharp Attempting to build from source via node-gyp but this may fail due to the above error
      # info sharp Please see https://sharp.pixelplumbing.com/page/install for required dependencies

To avoid this i'm thinking to compile with rosetta

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

Successfully merging this pull request may close these issues.

4 participants