Error when running npm install -g truffle

[junxiaogwu2024]

Error when running npm install -g truffle

[junxiaogwu2024]

Ah, that worked, even though I still have this error.

Try 'libtool --help' for more information.
libtool: error: unrecognised option: '-static'
make: *** [Release/leveldb.a] Error 1
gyp ERR! build error
gyp ERR! stack Error: make failed with exit code: 2
gyp ERR! stack at ChildProcess.onExit (/Users/junxiao/.nvm/versions/node/v16.20.2/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:194:23)
gyp ERR! stack at ChildProcess.emit (node:events:513:28)
gyp ERR! stack at Process.ChildProcess._handle.onexit (node:internal/child_process:293:12)
gyp ERR! System Darwin 22.6.0
gyp ERR! command "/Users/junxiao/.nvm/versions/node/v16.20.2/bin/node" "/Users/junxiao/.nvm/versions/node/v16.20.2/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /Users/junxiao/.nvm/versions/node/v16.20.2/lib/node_modules/truffle/node_modules/leveldown
gyp ERR! node -v v16.20.2
gyp ERR! node-gyp -v v5.1.1
gyp ERR! not ok

The truffle command worked.

truffle
Truffle v5.11.3 - a development framework for Ethereum

Usage: truffle [options]

[snwlprdgthb]

Hello @junxiaogwu2024 !

What is your current version of node ?
You can switch versions with nmv, error may go away with a later/earlier version.
And I'm just wondering if this same error logs occurs when installing truffle locally without the -g flag ?

[junxiaogwu2024]

Hi @snwlprdgthb,

The npm is version 10.0.0. let me try with a different version of npm to give a try.

Thanks,

[snwlprdgthb]

@junxiaogwu2024

I meant node version, not npm
Thanks

[junxiaogwu2024]

Ah, sorry, the node version is v18.17.1.

Cheers,

[junxiaogwu2024]

I tried with a lower version, 16.20.1, but got the same error. I wonder if anything else I could try.
Cheers.

[snwlprdgthb]

@junxiaogwu2024

I got it. Try downgrading npm to version 6, it should work for you.

npm install -g npm@6

[gnidan]

Glad to see this is [mostly] sorted out... I think we can probably close this? That one error message seems like one that we can ignore.

Please open a new issue if you run into further problems. Thanks for reporting this!