Support npm >= 1.1.6 (upgrade to fibers 0.6.5) about asyncblock HOT 2 CLOSED

I released a fix for this as 2.0.7.

I'm getting some weird output from the fibers build when running tests (laverdet/node-fibers#60), but everything appears to be working.

from asyncblock.

Could this be a linux vs mac issue? Here's my build output for reference:

bash-3.2$ node --version
v0.6.8
bash-3.2$ npm --version
1.1.0-2
bash-3.2$ sudo npm install [email protected]
npm http GET https://registry.npmjs.org/fibers/0.6.5
npm http 200 https://registry.npmjs.org/fibers/0.6.5
npm http GET https://registry.npmjs.org/fibers/-/fibers-0.6.5.tgz
npm http 200 https://registry.npmjs.org/fibers/-/fibers-0.6.5.tgz

[email protected] install
/Users/jpurcell/projects/testFibers/node_modules/fibers
make clean all

make -C src clean
rm -f fibers.node libcoro.o coroutine.o
rm -f -r *.dSYM
rm -f -r man
make -C src fibers.node
g++ -Wall -Wno-deprecated-declarations
-I/Users/jpurcell/.nave/installed/0.6.8/include
-I/Users/jpurcell/.nave/installed/0.6.8/include/node -g -O3 -m64
-DCORO_SJLJ -fPIC -c -o coroutine.o coroutine.cc
coroutine.cc: In destructor Coroutine::~Coroutine():
coroutine.cc:77: warning: statement has no effect
cc -Wall -Wno-deprecated-declarations
-I/Users/jpurcell/.nave/installed/0.6.8/include
-I/Users/jpurcell/.nave/installed/0.6.8/include/node -g -O3 -m64
-DCORO_SJLJ -fPIC -c -o libcoro.o libcoro/coro.c
g++ -bundle -undefined dynamic_lookup -Wall -Wno-deprecated-declarations
-I/Users/jpurcell/.nave/installed/0.6.8/include
-I/Users/jpurcell/.nave/installed/0.6.8/include/node -g -O3 -m64
-DCORO_SJLJ fibers.cc coroutine.o libcoro.o -o fibers.node -lpthread
./test.sh
already-running.js: pass
bad-context.js: pass
child-process.js: pass
current.js: pass
exec.js: pass
exit.js: pass
fibonacci.js: pass
finish-multiple.js: pass
future.js: pass
illegal-yield.js: pass
pool.js: pass
process-title.js: pass
stack-overflow.js: pass
started.js: pass
unwind.js: pass
[email protected] ./node_modules/fibers
bash-3.2$

On Mon, Mar 19, 2012 at 11:01 PM, scriby <
[email protected]

wrote:

I released a fix for this as 2.0.7.

I'm getting some weird output from the fibers build when running tests (
laverdet/node-fibers#60), but everything
appears to be working.

---

Reply to this email directly or view it on GitHub:
#8 (comment)

from asyncblock.