-
Notifications
You must be signed in to change notification settings - Fork 99
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
npm install fails with Ubuntu 18.04, lldb 6.0 #355
Comments
That seems like a new one (although I think I saw the (I'm also not sure about having |
I'm confused actually, you got the error when trying to build with |
$ node -v Before I realised what was going on (fall back to Debug), I thought it was a Debug/Release inconsistency. |
Node.js v8.x is not supported anymore (but that shouldn't be the reason it's not working, we just dropped support a month ago). I'll try your patch later, but I'm reluctant on merging it without understanding what's going on first. |
If you revert the patch, clear the workspace and run |
I just realized our README doesn't reflect that, even though our release notes does, sorry about that. |
Yes, still fails:
Note that this is the newest node version available on Ubuntu LTS - 20 isn't out until later this month. If you're not able to support this version of node, maybe note the last release that does for us poor LTS users? Which is it, and I'll try a build of that? |
Thank you for confirming the issue persists. I have a few ideas of what might be.
Node.js v8/x is EOL (it has been since December). We try to keep up with Node.js release schedule as much as possible. Maintaining llnode is hard (it requires reverse-engineering V8), and we have very few contributors, so we don't have the resources to support EOL Node.js versions. I think the default Node.js version you can install via llnode 2.2.0 was the last version with support for v8.x. That doesn't mean llnode 3.1.0 will not work with v8.x, but we don't have test coverage for it. |
Just FYI v2.2.0 also has the same issue |
Your "guide" link didn't point anywhere, but I can confirm that the official v12.16.1 tarball for node builds OK. I don't know if it's worth making this be a change to README in which case I can work up a PR? |
I was able to reproduce it on a docker container using the Node.js, npm and node-gyp version provided by Canonical. Both npm and node-gyp are somewhat outdated (more so than they should be on Node.js v8.10) when installed via the Canonical repo, I think the issue is because of outdated node-gyp, but the whole toolchain here is outdated (EOL). Using Node.js v8.10.0 installed via |
Just for clarification, I wasn't suggesting the patch be applied; just that it's what I needed. |
My bad, wanted to point out to this guide: https://github.com/nodesource/distributions/blob/master/README.md
I don't think it's worth since we don't have other instructions on how to install Node.js and I think that's out of scope for our README. We might be able to do something to keep our preinstall scripts more resilient though, so I'd like to keep this issue open for now. |
The reason I suggested a README update is because you do have a "Pre-requisite" section that does mention the package installer but says nothing at all about nod version or source. Maybe it's obvious to most people that the vendor-provided Node installation can't work, but it wasn't to me. |
Fixes: nodejs#355 Signed-off-by: Matheus Marchini <mmarchini@netflix.com>
That's not a limitation of llnode by the way, there are other packages which will not work because the package distributed by Ubuntu is not official. It's also not limited to Node.js, I've had problems with many other runtimes when installing from the Ubuntu repository instead of via the official installation channel provided by each project. I agree with you, that's not something new users are supposed to know (and ideally it shouldn't be an issue in the first place). We've updated our README to reflect which Node.js version are supported (v10+) and I have a PR to make the installation process more deterministic and robust (from what I've tested it fixes this issue). |
fails "npm install" (w or without --debug):
I had to use this diff:
The text was updated successfully, but these errors were encountered: