Anybody got metamucil? I got problems with Fibers.. ;-)
Charlie Fullerton
I needed to install "fibers".. I ran the curl and it worked.
When I ran the "npm install fibers" I got a bunch of err's...
What does "failed with 2" mean?
n...@1.0.106 /usr/lib/node_modules/npm
It worked
root@beaglebone:/var/lib/cloud9# npm install fibers
> fib...@0.5.1 install /var/lib/cloud9/node_modules/fibers
> make clean all
make -C src clean
make[1]: Entering directory `/var/lib/cloud9/node_modules/fibers/src'
rm -f fibers.node libcoro.o coroutine.so
rm -f -r *.dSYM
make[1]: Leaving directory `/var/lib/cloud9/node_modules/fibers/src'
rm -f -r man
make -C src coroutine.so
make[1]: Entering directory `/var/lib/cloud9/node_modules/fibers/src'
cc -Wall -Wno-deprecated-declarations -I/usr/include
-I/usr/include/node -g -O3 -minline-all-stringops -m32 -DCORO_UCONTEXT
-fPIC -c -o libcoro.o libcoro/coro.c
cc1: error: unrecognized command line option "-minline-all-stringops"
cc1: error: unrecognized command line option "-m32"
make[1]: *** [libcoro.o] Error 1
make[1]: Leaving directory `/var/lib/cloud9/node_modules/fibers/src'
make: *** [/var/lib/cloud9/node_modules/fibers/src/coroutine.so] Error 2
npm ERR! error installing fib...@0.5.1 Error: fib...@0.5.1 install:
`make clean all`
npm ERR! error installing fib...@0.5.1 `sh "-c" "make clean all"` failed
with 2
npm ERR! error installing fib...@0.5.1 at ChildProcess.<anonymous>
(/usr/lib/node_modules/npm/lib/utils/exec.js:49:20)
npm ERR! error installing fib...@0.5.1 at ChildProcess.emit
(events.js:67:17)
npm ERR! error installing fib...@0.5.1 at ChildProcess.onexit
(child_process.js:192:12)
npm ERR! fib...@0.5.1 install: `make clean all`
npm ERR! `sh "-c" "make clean all"` failed with 2
npm ERR!
npm ERR! Failed at the fib...@0.5.1 install script.
npm ERR! This is most likely a problem with the fibers package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! make clean all
npm ERR! You can get their info via:
npm ERR! npm owner ls fibers
npm ERR! There is likely additional logging output above.
npm ERR!
npm ERR! System Linux 3.1.0+
npm ERR! command "node" "/usr/bin/npm" "install" "fibers"
npm ERR! cwd /var/lib/cloud9
npm ERR! node -v v0.4.12
npm ERR! npm -v 1.0.106
npm ERR! code ELIFECYCLE
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /var/lib/cloud9/npm-debug.log
npm not ok
Koen Kooi
Op 12 feb. 2012, om 03:32 heeft Charlie Fullerton het volgende geschreven:
> Playing around with Cloud9 and when I tried to run schmux.js it told me I needed to install "fibers".. I ran the curl and it worked.
> When I ran the "npm install fibers" I got a bunch of err's...
'fibers' are optional and currently don't work with the nodejs 0.4.x release we use. Cloud9 doesn't work with the nodejs 0.6.x releases that work with 'fibers'
regards,
Koen
> --
> To join: http://beagleboard.org/discuss
> To unsubscribe from this group, send email to:
> beagleboard...@googlegroups.com
> Frequently asked questions: http://beagleboard.org/faq
Andy Hare
I've been running cloud9 and node0.6.6 under Debian on a beaglebone and
spent some time getting fibers to compile. If you get the code from
github laverdet/node-fibers it will compile in arm version if you
'export HOSTTYPE=arm' first. Why the standard environment will not allow
compilation I don't know, I had to do the export before it would work.
npm install seems to get an older version of the code.
Hope this helps.
--
Andy Hare