| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Probably a duplicate: #758 (comment)
An incorrectly closed PR which assumed this issue was no longer present: #744
We're still linking our prebuilts to a newer gcc. If you build it from source it should work fine. Try:
BUILD_ONLY=true npm install nodegitI was able to get the project directly consuming it to build (both with and without master) by following the travis-addon instructions in the above PR.
However, setting the dependency to master results in failed builds for projects consuming another project which has nodegit as a dependency.
See: https://travis-ci.org/runspired/ember-hammertime/jobs/100523335
You're getting a node-gyp error because that build is still using old gcc.
We might need to make gcc 4.9+ a requirement for nan anyways since for node versions 4+
@johnhaley81 I did, I can make Travis pass for that repo (and that repo only) with each test scenario taking an additional 6-10minutes to run :'(
But a secondary issue arises when that repo is a dependency of another project. It's code will never be executed on Travis, but nodegit must be a dependency. This results in consuming projects also needing to configure Travis specially for a dependency that's unneeded during testing, with ridiculous build times if you do.
I'm also seeing this error trying to run a project using nodegit in Elastic Beanstalk.
I can confirm this is still an issue with 0.7.0 build.
@runspired if you setup your travis env to use the latest gcc 4.9, you shouldn't have to compile anything to make this work and your builds should take hardly any longer.
I received this error myself when installing NodeGit on Ubuntu. So I followed my own advice above and installed both GCC 4.9 and the libstdc++-4.9-dev packages by doing:
sudo add-apt-repository ppa:ubuntu-toolchain-r/test
sudo apt-get update
sudo apt-get install libstdc++-4.9-devPre install libstdc++-4.9-dev linked libraries:
λ ldd node_modules/nodegit/build/Release/nodegit.node
node_modules/nodegit/build/Release/nodegit.node: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.20' not found (required by node_modules/nodegit/build/Release/nodegit.node)
linux-vdso.so.1 => (0x00007fffdabd5000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007f7309f02000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f7309cec000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f7309ace000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f7309709000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f7309403000)
/lib64/ld-linux-x86-64.so.2 (0x00007f730ad03000)Post install libstdc++-4.9-dev linked libraries:
λ ldd node_modules/nodegit/build/Release/nodegit.node
linux-vdso.so.1 => (0x00007ffe26c6a000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007f4d5b9ea000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f4d5b7cc000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f4d5b407000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f4d5b101000)
/lib64/ld-linux-x86-64.so.2 (0x00007f4d5c46a000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f4d5aeeb000)So yes, you'll definitely need to install libstdc++-4.9-dev if it's not working out-of-the-box.
You can do this in Travis-CI by adding the following to your .travis.yml file:
addons:
apt:
sources:
- ubuntu-toolchain-r-test
packages:
- libstdc++-4.9-devwe are also hitting same issue
Error: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.20' not found (required by /data/jenkins/workspace/master/node_modules/nodegit/build/Release/nodegit.node)
Is there any solution for centos-release-6-7 OS?
@hridyeshpant any solutions on this ?
Is there any solution for centos-release-6-7 OS?
BUILD_ONLY=true npm install nodegit solved the problem for me on centos7. Thanks to #853 (comment)
Is BUILD_ONLY=true npm install nodegit the same as npm install nodegit --build-from-source?
Not quite, there is a bit more to it that we do with BUILD_ONLY set to true
So what's the solution for this? I'm trying to run a project on elasticbeanstalk and it's failing with the same issues.
@chalangr12 solution for what? We can't build for every single architecture unfortunately, only popular ones. Can you try and suss out what dependency is causing your failure? Is it glibc?
| Back | FazBrowse Home | New Git URL |