Skip to content
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

Installation error: neon.o: No such file or directory #29

Open
teddyknox opened this issue Oct 15, 2021 · 2 comments
Open

Installation error: neon.o: No such file or directory #29

teddyknox opened this issue Oct 15, 2021 · 2 comments

Comments

@teddyknox
Copy link

Getting this when I run npm install -g @graphprotocol/indexer-cli:

npm ERR! warning: ar: /usr/local/lib/node_modules/@graphprotocol/indexer-cli/node_modules/@graphprotocol/cost-model/native/target/debug/build/neon-sys-3b6678701d556f27/out/native/build/Debug/obj.target/neon/src/neon.o: No such file or directory                                                          npm ERR!                                                                                                                                               npm ERR! error: failed to run custom build command for `neon-sys v0.5.3`                                                                               npm ERR!                                                                                                                                               
npm ERR! Caused by:                                                                                                                                    
npm ERR!   process didn't exit successfully: `/usr/local/lib/node_modules/@graphprotocol/indexer-cli/node_modules/@graphprotocol/cost-model/native/target/debug/build/neon-sys-ecacff10f410d9d8/build-script-build` (exit status: 1)                                                                          
npm ERR!   --- stdout                                                                                                                                  
npm ERR!   cargo:node_arch=x64                                                                                                                         
npm ERR!   TARGET = Some("x86_64-apple-darwin")                                                                                                        
npm ERR!   HOST = Some("x86_64-apple-darwin")                                                                                                          
npm ERR!   AR_x86_64-apple-darwin = None                                   
npm ERR!   AR_x86_64_apple_darwin = None                                                                                                               
npm ERR!   HOST_AR = None                                                                                                                              
npm ERR!   AR = None                                                                                                                                   
npm ERR!   running: "ar" "cq" "/usr/local/lib/node_modules/@graphprotocol/indexer-cli/node_modules/@graphprotocol/cost-model/native/target/debug/build/neon-sys-3b6678701d556f27/out/libneon.a" "/usr/local/lib/node_modules/@graphprotocol/indexer-cli/node_modules/@graphprotocol/cost-model/native/target/debug/build/neon-sys-3b6678701d556f27/out/native/build/Debug/obj.target/neon/src/neon.o"                                                                
npm ERR!   cargo:warning=ar: /usr/local/lib/node_modules/@graphprotocol/indexer-cli/node_modules/@graphprotocol/cost-model/native/target/debug/build/neon-sys-3b6678701d556f27/out/native/build/Debug/obj.target/neon/src/neon.o: No such file or directory                                                   npm ERR!   exit status: 1

Any idea what's wrong?

@That3Percent
Copy link
Contributor

I do not offhand know what this is (I rarely use npm/JS/neon) but was able to find a similar issue in neon-bindings.

The fix was to run npm install --global --save neon-cli. So, try that and see if it fixes it.

@chriswessels
Copy link
Member

chriswessels commented Feb 18, 2022

@teddyknox Make sure that your rust toolchain is set to the right architecture. I had issues like this when my default rust toolchain was x86_64 on an M1 machine. See graphprotocol/indexer#363

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants