Repository navigation
Conversation
|
This is useful information if the build does fail, although with latest Node 0.12 or 4.1 it should download the prebuilt binary that we publish. |
|
It doesn't though, see the log for the latest build I did: I'm not sure why this happens but it makes builds take forever because it has to recompile every time. |
|
Can you give us your platform (nix/osx?), arch, and node/npm versions? |
|
Sure, this occurs on Travis CI when testing against node 0.10, 0.11 and 0.12, npm 1.4.28. I believe they are using Ubuntu 12.04 in Docker containers. On 4.0 and 4.1 with npm 2.14, it fails with the following, no matter what I tried: |
|
By the way, why not use bluebird's promisify and bluebird's promises rather than |
|
@coaxial someone tried to use Bluebird in the past, but it broke wayyyy too much stuff. I don't remember the specifics, but you can crawl through the history log for the revert. We do not support 0.10 for precompiled builds, which means it will compile in those cases. Node 0.12 and Node 4.1 on Travis should not be compiling, can you verify this and/or show us where that's not the case? |
|
This might no longer be needed after #761 |
|
We're having a similar issue. Travis fails to install the precompiled binary and eventually dies during build on v0.12. When installing nodegit from master ( |
|
@contolini installing nodegit from the |
|
I think we finally git rid of the glibc requirement correct? If so this can just be closed |
|
Yeah, we can close this one down. You don't need that anymore to build. If that changes for any reason we can open this back up. Thanks @coaxial |
|
@johnhaley81 this is still an issue |
|
Reopening due to #853 |
|
I've since added instructions that are easier and don't require rebuilding the module (prebuilt works fine), so closing this. |
If one is using Travis CI to build a project that depends on nodegit, the build will fail because it can't compile.
These steps will keep this from happening and will let nodegit compile happily.