Error: Cannot find module '../build/default/bufferutil' #25

Closed
samccone opened this Issue Feb 21, 2012 · 8 comments

Comments

Projects
None yet
2 participants

Getting this error after building

node.js:201
throw e; // process.nextTick error, or 'error' event on first tick
^
Error: Cannot find module '../build/default/bufferutil'
at Function._resolveFilename (module.js:332:11)
at Function._load (module.js:279:25)
at Module.require (module.js:354:17)
at require (module.js:370:17)
at Object. (..../savant-demo/node_modules/ws/lib/BufferUtil.js:14:20)

I clearly have the files ... but I am not sure what is going on

http://i.imgur.com/zq8Cx.png

Contributor

einaros commented Feb 21, 2012

Which node version and platform?

Is there a bufferutil* within ws/build/default?

node v v0.6.11
osx 10.7.3

this is the file structure that i have ... so no build folder ... only a Release folder ....

within it there is bufferutil.node

http://i.imgur.com/zq8Cx.png

here is the build stack

node-waf configure build
Checking for program g++ or c++ : /usr/bin/g++
Checking for program cpp : /usr/bin/cpp
Checking for program ar : /usr/bin/ar
Checking for program ranlib : /usr/bin/ranlib
Checking for g++ : ok
Checking for node path : not found
Checking for node prefix : ok /usr/local
'configure' finished successfully (0.054s)
Waf: Entering directory /......./node_modules/ws/build' [1/4] cxx: src/validation.cc -> build/Release/src/validation_1.o [2/4] cxx: src/bufferutil.cc -> build/Release/src/bufferutil_2.o [3/4] cxx_link: build/Release/src/validation_1.o -> build/Release/validation.node [4/4] cxx_link: build/Release/src/bufferutil_2.o -> build/Release/bufferutil.node Waf: Leaving directory/....../node_modules/ws/build'
'build' finished successfully (0.519s)
npm http GET https://registry.npmjs.org/commander/0.5.0
npm http GET https://registry.npmjs.org/options
npm http 304 https://registry.npmjs.org/options
npm http 304 https://registry.npmjs.org/commander/0.5.0
ws@0.4.6 ./node_modules/ws

Contributor

einaros commented Feb 21, 2012

Ok, thank you -- I'm looking into it now.

Contributor

einaros commented Feb 21, 2012

In the mean time, 0.6.10 does work. I've yet to figure out exactly what fails with 0.6.11.

ok great thanks man

Contributor

einaros commented Feb 21, 2012

Right, this is the reason: nodejs/node-v0.x-archive@4672872

The prebuilt OSX package now targets ia32 (rather than mostly x64 in previous releases). The immediate fix is to compile node from source from now on. Other than that I'll have to update my build scripts to figure out which architecture node was built for, although that's not an optimal (or straight forward) solution either.

beast mode achieved :)

einaros closed this in 81ea80a Feb 21, 2012

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment