-
Notifications
You must be signed in to change notification settings - Fork 21
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
Invalid glibc versions. #167
Comments
what OS are you using? the point of having the node version bundled with the pypi package is that the user shouldn't have to worry about installing it themselves. i see nodejs as an implementation detail that shouldn't be exposed to the user, so hopefully i can find a solution that doesn't require allowing the user to specify a globally installed node |
I am on an ancient os. Centos 7.5
…On Mon, Mar 18, 2024, 1:12 PM DetachHead ***@***.***> wrote:
what OS are you using?
the point of having the node version bundled with the pypi package is that
the user shouldn't have to worry about installing it themselves. i see
nodejs as an implementation detail that shouldn't be exposed to the user,
so hopefully i can find a solution that doesn't require allowing the user
to specify a globally installed node
—
Reply to this email directly, view it on GitHub
<#167 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAA5ISDLIZHJ7WB7XCU2LR3YY4OBTAVCNFSM6AAAAABE3YI3LOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMBUGQ4TAMZXGE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
looks like that's the issue. basedpyright comes with node 18 but i think your centOS version is too old for that. https://stackoverflow.com/a/72038045 since both centOS and node 16 are EOL i was originally going to close this issue, but then i realized upstream pyright supports node 14 so i should probably try to match that. can you install the version from #204 and see if that fixes it?
you may need to pin |
https://pypi.org/project/nodejs-wheel/ supports a much older glibc version and can confirm it works on rhel7 (similar to centos7). Would it be possible to switch to (or optionally use) that instead? |
thanks for the suggestion, we can give it a go. the one we currently use looks abandoned so i was already keeping an eye out for another solution anyway |
Wider support for older glibc Fixes DetachHead#167
Wider support for older glibc Fixes DetachHead#167
Wider support for older glibc Fixes DetachHead#167
Wider support for older glibc Fixes #167
Wider support for older glibc Fixes DetachHead#167
I am getting invalid glibc versions with the build in version of node. I would like to use my own version of node that is installed on my machine.
The text was updated successfully, but these errors were encountered: