Oh yeah, that's true. I remember when we got this working on a beaglebone we just left out -m32 altogether and did -march=arm.
As for my beaglebone I'm crazy and installed Gentoo on it, so this is my cc -v output ;) bone ~ # cc -v Using built-in specs. COLLECT_GCC=/usr/armv7a-unknown-linux-gnueabi/gcc-bin/4.5.3/gcc COLLECT_LTO_WRAPPER=/usr/libexec/gcc/armv7a-unknown-linux-gnueabi/4.5.3/lto-wrapper Target: armv7a-unknown-linux-gnueabi Configured with: /var/tmp/portage/sys-devel/gcc-4.5.3-r2/work/gcc-4.5.3/configure --prefix=/usr --bindir=/usr/armv7a-unknown-linux-gnueabi/gcc-bin/4.5.3 --includedir=/usr/lib/gcc/armv7a-unknown-linux-gnueabi/4.5.3/include --datadir=/usr/share/gcc-data/armv7a-unknown-linux-gnueabi/4.5.3 --mandir=/usr/share/gcc-data/armv7a-unknown-linux-gnueabi/4.5.3/man --infodir=/usr/share/gcc-data/armv7a-unknown-linux-gnueabi/4.5.3/info --with-gxx-include-dir=/usr/lib/gcc/armv7a-unknown-linux-gnueabi/4.5.3/include/g++-v4 --host=armv7a-unknown-linux-gnueabi --build=armv7a-unknown-linux-gnueabi --disable-altivec --disable-fixed-point --without-ppl --without-cloog --disable-lto --enable-nls --without-included-gettext --with-system-zlib --disable-werror --enable-secureplt --disable-multilib --enable-libmudflap --disable-libssp --enable-libgomp --with-python-dir=/share/gcc-data/armv7a-unknown-linux-gnueabi/4.5.3/python --enable-checking=release --disable-libgcj --with-arch=armv7-a --enable-languages=c,c++,fortran --enable-shared --enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu --with-bugurl= http://bugs.gentoo.org/ --with-pkgversion='Gentoo 4.5.3-r2 p1.1, pie-0.4.7' Thread model: posix gcc version 4.5.3 (Gentoo 4.5.3-r2 p1.1, pie-0.4.7) On Wed, May 9, 2012 at 3:26 PM, Jorge <[email protected]> wrote: > On May 9, 2012, at 9:45 PM, Marcel Laverdet wrote: > > > gcc version shouldn't matter. The pthread version of libcoro will run on > anything with POSIX-pthreads, it's a very very robust implementation. > > > > That's not to say that node-fibers will run on everything.. the build > process will need to accomodate that. I got access to a beaglebone and > tried to get the latest version of node running on it but didn't get very > far before moving on to other things. > > but isn't it complaining about the -m32 and the -minline-all-stringops GCC > (i386) options ? > > -- > 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 > -- 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
