It looks like the Synology DS213+ (PPC) is a Freescale e500 class chip. http://forum.synology.com/wiki/index.php/What_kind_of_CPU_does_my_NAS_have
We've discovered there are issues with this chip and our assumptions in the code for PowerPC. See issues https://github.com/andrewlow/v8ppc/issues/99 and https://github.com/andrewlow/v8ppc/issues/100. We do intend to address this, but it's not a key platform for our team. You've also apparently hit some compiler limitations - this will require some hacking the .gyp / .gypi files that are used to generate the makefiles. You can learn a bit about GYP here https://code.google.com/p/gyp/ -- or just grep around for the offending flag and remove it.(that might get you past the immediate issue). There is some hope. In issue #99 I show how to build a 'simulated' version of the code (with performance implications!) which might get you limping until we get around to really supporting the e500. If you're more keen - issue #100 has a fair bit of detail and links to a starting point to make the right fixes. On Fri, Jan 10, 2014 at 4:36 PM, Alexander Post <[email protected]>wrote: > Hi Andrew, > > I tried to compile your node.js port on a Synology DS213+ (PPC). There is > currently only GCC 4.3 available for this system and I get the following > error: > > make -C out BUILDTYPE=Release V=1 > > make[1]: Entering directory `/volume1/public/node/out' > > cc '-D_DARWIN_USE_64_BIT_INODE=1' '-D_LARGEFILE_SOURCE' > '-D_FILE_OFFSET_BITS=64' '-D_GNU_SOURCE' '-DHAVE_CONFIG_H' > '-DCARES_STATICLIB' -I../deps/cares/include -I../deps/cares/src > -I../deps/cares/config/linux -Wall -Wextra -Wno-unused-parameter -pthread > -m32 -g --std=gnu89 -pedantic -Wall -Wextra -Wno-unused-parameter -O2 > -fno-strict-aliasing -fno-tree-sink -MMD -MF > /volume1/public/node/out/Release/.deps//volume1/public/node/out/Release/obj.target/cares/deps/cares/src/ares_cancel.o.d.raw > -c -o > /volume1/public/node/out/Release/obj.target/cares/deps/cares/src/ares_cancel.o > ../deps/cares/src/ares_cancel.c > > cc1: error: unrecognized command line option "-fno-tree-sink" > > make[1]: *** > [/volume1/public/node/out/Release/obj.target/cares/deps/cares/src/ares_cancel.o] > Error 1 > > make[1]: Leaving directory `/volume1/public/node/out' > > make: *** [node] Error 2 > > > I'm not very familiar with linux and I would be happy if you could help me. > > > Thanks > > > Alex > > > > > > Am Dienstag, 3. September 2013 20:41:53 UTC+2 schrieb Andrew Low: > >> Hi folks, allow me to introduce myself. I'm Andrew Low and I work for >> IBM. I've been building runtime technology for almost 20 years, over that >> time I've built Smalltalk VMs (http://en.wikipedia.org/wiki/IBM_VisualAge), >> Java VMs (http://en.wikipedia.org/wiki/IBM_J9), and I'm now working on >> JavaScript runtimes (and this means Node.js too!) >> >> Since early this year I've been leading a small team porting V8 to >> PowerPC. If you're keen to follow along all of our work it up on GitHub >> https://github.com/andrewlow/v8ppc >> >> As most of you are aware, Node.js relies on V8 for it's javascript >> runtime. This has been a barrier to bringing Node.js to platforms that >> don't (yet) have a V8 port. Now that the V8 port to PowerPC is fairly >> feature complete, we're able to bring Node.js up on Power Linux. You can >> check the code out here: https://github.com/andrewlow/node - >> specifically the branch "v0.10.16-release-ppc" >> >> We're planning on giving all of this code back to the community - it's >> all there on GitHub now and licensed in the same manner as the original >> project. So far there are only a handful of changes to the Node.js code. >> >> There is also a public Jenkins continuous integration server building >> binaries: http://v8ppc.osuosl.org:8080/ >> >> Limitations: For now it's only 32bit (but the binaries will of course run >> just fine on 64bit systems). We're also stuck on the 0.10.x branch of Node >> for the time being. We will be working towards removing these limitations. >> > -- > -- > 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 > > --- > You received this message because you are subscribed to a topic in the > Google Groups "nodejs" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/nodejs/ivGMr-C_m1Y/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > -- -- 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 --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
