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

build failure due to gyp action race condition? #153

Closed
springmeyer opened this issue Jun 19, 2013 · 4 comments
Closed

build failure due to gyp action race condition? #153

springmeyer opened this issue Jun 19, 2013 · 4 comments

Comments

@springmeyer
Copy link
Contributor

> sqlite3@2.1.10 install /Volumes/Flex/build-2013-06-19-191053/tilemill/node_modules/sqlite3
> node-gyp rebuild

.....snip.....

make: *** No rule to make target `Release/obj.target/sqlite3/deps/sqlite-autoconf-3071700/sqlite3.o', needed by `Release/sqlite3.a'.  Stop.
make: *** Waiting for unfinished jobs....
  ACTION binding_gyp_action_before_build_target_unpack_sqlite_dep deps/sqlite-autoconf-3071700/sqlite3.c
springmeyer pushed a commit that referenced this issue Jun 20, 2013
@pward123
Copy link

Getting this same error. I updated my package reference to

    "sqlite3": "git://github.com/developmentseed/node-sqlite3#945df53",

and cleared nodes cache, but still getting the error

@pward123
Copy link

A little more information. It looks like there's a problem with the tar.gz module. When I force 2.1.7, everything works. As soon as I move to 2.1.8, I start getting:

make: *** No rule to make target `Release/obj.target/sqlite3/deps/sqlite-autoconf-3071700/sqlite3.o', needed by `Release/sqlite3.a'.  Stop.
make: *** Waiting for unfinished jobs....
  ACTION binding_gyp_action_before_build_target_unpack_sqlite_dep deps/sqlite-autoconf-3071700/sqlite3.c

module.js:340
    throw err;
          ^
Error: Cannot find module '/Users/pward/Documents/DiemTech/sequelize/node_modules/sqlite3/node_modules/.bin/targz'

@Mithgol
Copy link
Contributor

Mithgol commented Jun 29, 2013

Well, failing tar.gz might be related to #151.

@springmeyer
Copy link
Contributor Author

finally fixed in bdf3391 and should work without problems in v2.1.11

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