Thx Marcel
The distro: Angstrom v2012.01-core - Kernel 3.2.5+
cc -v
root@beaglebone:~# cc -v
Using built-in specs.
COLLECT_GCC=cc
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/arm-angstrom-linux-gnueabi/4.5.4/lto-wrapper
Target: arm-angstrom-linux-gnueabi
Configured with:
/OE/tentacle/build/tmp-angstrom_2010_x-eglibc/work-shared/gcc-4.5-r45+svnr181733/gcc-4_5-branch/configure
--build=x86_64-linux --host=arm-angstrom-linux-gnueabi
--target=arm-angstrom-linux-gnueabi --prefix=/usr --exec_prefix=/usr
--bindir=/usr/bin --sbindir=/usr/sbin --libexecdir=/usr/libexec
--datadir=/usr/share --sysconfdir=/etc --sharedstatedir=/com
--localstatedir=/var --libdir=/usr/lib --includedir=/usr/include
--oldincludedir=/usr/include --infodir=/usr/share/info
--mandir=/usr/share/man --disable-silent-rules
--disable-dependency-tracking
--with-libtool-sysroot=/OE/tentacle/build/tmp-angstrom_2010_x-eglibc/sysroots/beagleboard
--with-gnu-ld --enable-shared --enable-languages=c,c++
--enable-threads=posix --disable-multilib --enable-c99
--enable-long-long --enable-symvers=gnu --enable-libstdcxx-pch
--program-prefix=arm-angstrom-linux-gnueabi- --enable-target-optspace
--enable-lto --enable-libssp --disable-bootstrap --disable-libgomp
--disable-libmudflap --with-linker-hash-style=gnu --with-ppl=no
--with-cloog=no --enable-cheaders=c_global
--with-local-prefix=/OE/tentacle/build/tmp-angstrom_2010_x-eglibc/sysroots/beagleboard/usr
--with-gxx-include-dir=/usr/include/c++/ --enable-nls --enable-__cxa_atexit
Thread model: posix
gcc version 4.5.4 20111126 (prerelease) (GCC)
Paul
At 08:29 PM 5/9/2012, you wrote:
@Marcel Cool! @Paul what does `cc -v` give you ?
On May 9, 2012, at 9:18 PM, Marcel Laverdet wrote:
> libcoro runs fine on ARM, but you do need to use the
pthread_cond_wait version by passing -DCORO_PTHREAD. There is a
check for this in the Makefile (and new gyp file) but there hasn't
been strong testing there.
>
> On Wed, May 9, 2012 at 12:57 PM, Jorge <[email protected]> wrote:
> On May 9, 2012, at 5:35 PM, Paul Tanner wrote:
>
> > Thx Jorge
> >
> > Evidently I was wrong to go ahead and install npm in the usual
way. There must be a separate version or switch option for
installation on ARM.
> >
> > More searching needed. There are several working node modules
(eg http) in the distribution. The question is how were they installed?
> >
> > Paul
>
> Hi Paul,
>
> I think libcoro can't run on an ARM, but you should better ask
Marcel Laverdet (https://github.com/laverdet/node-fibers), or
perhaps Marc Lehmann (http://software.schmorp.de/pkg/libcoro.html)
>
> > 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
>
>
> The built-in modules come prebuilt with node so there's no need
to "make" them.
>
> Could you try to install threads_a_gogo
<https://github.com/xk/node-threads-a-gogo/> and tell me how it goes ?
>
> npm install threads_a_gogo
>
> And what this gives:
>
> node
./node_modules/threads_a_gogo/test/test01_loop_as_fast_as_possible.js 1
>
> ?
> --
> Jorge.
> github.com/xk/
> @jorgechamorro
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
Paul Tanner - Virtual Technologies - http://www.virtual-techno.com
Tel: +44 1494 581979 Mob: +44 7973 223239 mailto:[email protected]
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
