Repository navigation
llnode failed to install #396
Copy link
Copy link
Closed
Description
Hi,
I'm getting this error below, Any help appreciated:
`matchapug@MRPUG:/mnt/c/Windows/system32$ npm install -g llnode
> llnode@3.2.0 preinstall /home/matchapug/.nvm/versions/node/v14.18.1/lib/node_modules/llnode
> node scripts/configure.js
Build dir is: /home/matchapug/.nvm/versions/node/v14.18.1/lib/node_modules/llnode
Looking for lldb executable...
Found lldb executable /usr/bin/lldb
Reading lldb version...
Installing llnode for /usr/bin/lldb, lldb version 10.0
Looking for llvm-config for lldb 10.0...
Using llvm-config in /usr/bin/llvm-config
Looking for headers for lldb 10.0...
Could not find the headers, will download them later
Looking for shared libraries for lldb 10.0...
From ldd: /usr/bin/lldb loads /lib/x86_64-linux-gnu/liblldb-10.so.1
Found liblldb-10.so in /lib/x86_64-linux-gnu
Cloning lldb release_100 into /home/matchapug/.nvm/versions/node/v14.18.1/lib/node_modules/llnode/lldb-10.0
Cloning into '/home/matchapug/.nvm/versions/node/v14.18.1/lib/node_modules/llnode/lldb-10.0'...
warning: Could not find remote branch release_100 to clone.
fatal: Remote branch release_100 not found in upstream origin
child_process.js:830
throw err;
^
Error: Command failed: git clone --depth 1 --branch release_100 https://github.com/llvm-mirror/lldb.git /home/matchapug/.nvm/versions/node/v14.18.1/lib/node_modules/llnode/lldb-10.0
at checkExecSyncError (child_process.js:790:11)
at Object.execFileSync (child_process.js:827:15)
at Object.cloneHeaders (/home/matchapug/.nvm/versions/node/v14.18.1/lib/node_modules/llnode/scripts/lldb.js:47:19)
at configureInstallation (/home/matchapug/.nvm/versions/node/v14.18.1/lib/node_modules/llnode/scripts/configure.js:89:25)
at main (/home/matchapug/.nvm/versions/node/v14.18.1/lib/node_modules/llnode/scripts/configure.js:12:34)
at Object.<anonymous> (/home/matchapug/.nvm/versions/node/v14.18.1/lib/node_modules/llnode/scripts/configure.js:20:1)
at Module._compile (internal/modules/cjs/loader.js:1085:14)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10)
at Module.load (internal/modules/cjs/loader.js:950:32)
at Function.Module._load (internal/modules/cjs/loader.js:790:12) {
status: 128,
signal: null,
output: [ null, null, null ],
pid: 304,
stdout: null,
stderr: null
}
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! llnode@3.2.0 preinstall: `node scripts/configure.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the llnode@3.2.0 preinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/matchapug/.npm/_logs/2021-11-09T03_01_36_875Z-debug.log`
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels
Activity
No9 commentedon Nov 9, 2021
Same as #350
As far as I can tell the fix is available here #389
It's just waiting for CI to be sorted.
PugDeveloper commentedon Nov 11, 2021
Ah I see, Thank you. Not sure if I'm manually installing this correct. Do I just follow the below step?:
Cause I did the below and its not working (minus the && sign)
No9 commentedon Nov 11, 2021
Yes that's the command
it's hard to see what's going on without the error message but note it runs in system folders so it should be ran as root
PugDeveloper commentedon Nov 12, 2021
When I run the npm now I get this error:
No9 commentedon Nov 14, 2021
This line looks very suspicious
npm ERR! fatal: cannot change to 'https://github.com/llvm/llvm-project.git': No such file or directoryCan you confirm that
/usr/local/lib/llnode/lldb-10.0has been generated and the code is checked out into it.The output of the command
ls -R /usr/local/lib/llnode/lldb-10.0will confirm itPugDeveloper commentedon Nov 16, 2021
I see it seem like there isn't a 11db-10.0 folder within the llnode. Would you happen to know why? Kind of new to this so bit confusing.
Thanks for the help so far!
No9 commentedon Nov 16, 2021
It's likely not working due to permissions but I can't say for sure.
You might be able to work around this by checking it out and build it from your home directory
Just ran this on my local machine as a single command and it worked fine.
Heres a breakdown of what's going on.
cd ~git clone --branch use-llvm-project-monorepo https://github.com/trxcllnt/llnode.gitcd llnodenpm install --global --unsafe-perm --no-audit --no-fundIf that doesn't work it may be better waiting for the PR to land
PugDeveloper commentedon Nov 19, 2021
Ah I see, still doesn't work, Seem like would nee to wait for PR. Anyone knows when that will happen?
Beretta1979 commentedon Jan 11, 2022
Installing the liblldb-dev package on ubuntu fixed this for me. This package contains the needed lldb header. No need for the git clone during the installation anymore ... Would the llnode not be simpler by just specifying this package as a needed prerequisite?
jaenster commentedon Jun 9, 2022
This did it for me, thanks
No9 commentedon Sep 17, 2022
OK we now have support for LLDB 8 to 14 and Node 14,16,18 so I'm closing this.
We are still getting the headers from github so please follow/comment on #382 if that is an issue.
antontsvil commentedon Oct 21, 2023
Commenting this in case anybody ran into this issue like I did currently, but if you're seeing the
sparse-checkouterror then it may be due to your version of git. Check to make sure yourgit --versionis 2.26 or higher.If you're on Ubuntu like I am, you'll need to add the PPA for newer versions of git
Once I updated my git, this issue dissappeared 😃