-
-
Notifications
You must be signed in to change notification settings - Fork 119
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
Can't build 3.0.0 from source with Node 18 / node-gyp #374
Comments
Python 3.0 is required, node-gyp will automatically try to find it, as it shows on your logs. Could you send me a Dockerfile that reproduces the issue? |
I did some googling and found this electron issue: [Bug]: Native modules that include nan.h fail to build on electron 20 Is that the possible issue? I tried compiling the older node-libcurl 2.3.4 and also ended up with errors related to nan.h:
Are you using any special config or settings or pinned versions of things not mentioned in your current documentation on how to build from source? I'm just using a fresh ubuntu 20.04 AWS instance, with the described prereqs installed and also installed curl-impersonate which I'm attempting to compile with. |
Hi, I figured out the issue, which was my bad: not enough ram and no swap on the instance I was using, leading to unpredictable issues when compiling things. After fixing that, the node-libcurl 3.0.0 compiled fine. BTW, suggest to update/remove the reference to python 2.7 on the main readme file. |
references to python 2.7 were removed from the readme. |
OS: Ubuntu 20.04
I see in your documentation it states python2.7 is required for install, but I can't seem to get the latest node-gyp to use it?
I do have it installed as /usr/bin/python2.7, and have tried to force node-gyp to use it via:
export PYTHON=/usr/bin/python2.7
creating a .npmrc file with python = "/usr/bin/python2.7"
export npm_config_python=/usr/bin/python2.7
Despite all these attempts, I still see in the failed build log:
which leads to the error:
Is the problem with using python3.8? Or is there another issue? Thanks
The text was updated successfully, but these errors were encountered: