With my RPi I used the node that came with Arch. I wasn't able to get 0.8 on it after simple build script modifications and I haven't had the time to figure it out.
AJ ONeal On Tue, Jun 26, 2012 at 5:34 PM, Tim Caswell <t...@creationix.com> wrote: > I also have a pi, but I mostly use it for luvit development. I can test > things if needed. > On Jun 26, 2012 2:32 PM, "AJ ONeal" <coola...@gmail.com> wrote: > >> Hey Nate, that sounds great! >> >> If you'd like some wonderfully failing test cases, send me an e-mail when >> you get your Pis. >> >> AJ ONeal >> >> On Tue, Jun 26, 2012 at 1:01 PM, Nathan Rajlich >> <nat...@tootallnate.net>wrote: >> >>> I'm awaiting 2 Raspberri Pi's to come in the mail, and once they get >>> here I was planning on giving ARM some attention (the build process >>> specifically needs work that I'm aware of). >>> >>> On Tue, Jun 26, 2012 at 10:56 AM, AJ ONeal <coola...@gmail.com> wrote: >>> >>>> What needs to happen for ARM to get a little attention? >>>> >>>> Every time there's a new version of node I have to go in and modify >>>> config files specifically for ARM and it seems that nodejs just doesn't run >>>> very well on it. >>>> >>>> I brought up before that I have a test case where it reads in mp3 and >>>> m4a metadata from 40,000 files and set's a timeout on each one and some of >>>> the timeouts don't get called. I've seen other funky things. And maybe it's >>>> all the fault of v8. I dunno. For some reason I'm crazy enough to just keep >>>> finding workarounds or expecting that in the next patch release there will >>>> be fixes... >>>> >>>> Can I offer a RaspberryPi or PandaBoard up on a global IP and set it up >>>> with a CI or something - or at least to run the test cases that are >>>> currently in tests/ (and add new ones that I should have already added and >>>> pull requested). >>>> >>>> AJ ONeal >>>> >>> >>> >>
