You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Cannot install nodegit on linux machines (e.g. travis builds) #853
/usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.20' not found (required by /home/travis/build/runspired/ember-cli-changelog/node_modules/nodegit/build/Release/nodegit.node)
I 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.
@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.
@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:
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?
Reacted by semos, leogdion, Mana Andria, Kate Miháliková, Matt Ralston, meyerbro and Thiago Bitencourt
@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?
Activity
runspired commentedon Jan 6, 2016
Probably a duplicate: #758 (comment)
runspired commentedon Jan 6, 2016
An incorrectly closed PR which assumed this issue was no longer present: #744
tbranyen commentedon Jan 6, 2016
We're still linking our prebuilts to a newer gcc. If you build it from source it should work fine. Try:
runspired commentedon Jan 6, 2016
I 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
masterresults in failed builds for projects consuming another project which has nodegit as a dependency.See: https://travis-ci.org/runspired/ember-hammertime/jobs/100523335
johnhaley81 commentedon Jan 6, 2016
You're getting a
node-gyperror 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+
runspired commentedon Jan 6, 2016
@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.
amackera commentedon Jan 12, 2016
I'm also seeing this error trying to run a project using
nodegitin Elastic Beanstalk.thinkingmedia commentedon Jan 13, 2016
I can confirm this is still an issue with 0.7.0 build.
tbranyen commentedon Jan 13, 2016
@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.
tbranyen commentedon Jan 15, 2016
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:
Pre install libstdc++-4.9-dev linked libraries:
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.
tbranyen commentedon Jan 15, 2016
You can do this in Travis-CI by adding the following to your .travis.yml file:
Install libstdc++ when testing on Travis
hridyeshpant commentedon May 17, 2016
we are also hitting same issue
Is there any solution for centos-release-6-7 OS?
semos commentedon May 31, 2016
@hridyeshpant any solutions on this ?
mikalai-s commentedon Oct 17, 2016
BUILD_ONLY=true npm install nodegitsolved the problem for me on centos7. Thanks to #853 (comment)Added requirement for nodegit to run on Ubuntu 14
heath-guidewire commentedon Apr 21, 2017
Is
BUILD_ONLY=true npm install nodegitthe same asnpm install nodegit --build-from-source?maxkorp commentedon Apr 21, 2017
Not quite, there is a bit more to it that we do with BUILD_ONLY set to true
ChalangRasul commentedon May 2, 2017
So what's the solution for this? I'm trying to run a project on elasticbeanstalk and it's failing with the same issues.
tbranyen commentedon May 2, 2017
@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?
ci(gcc): configured travis to use a newer gcc