Node.JS On Raspberry Pi

[Geoff Flarity]

FYI, I've created a github page with links to a binary and build instructions for getting Node to run on the Raspberry Pi:

https://github.com/gflarity/node_pi

It takes over 2 hours to build, so go for the binary unless you're paranoid.

Cheers,

Geoff

[Nathan Rajlich]

Thanks! Mine should me coming in on Thursday, so good timing :)

--
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 nod...@googlegroups.com
To unsubscribe from this group, send email to
nodejs+un...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

[TheAlphaNerd]

Awesome!!! Thanks for making the binaries available!

[Jerry Sievert]

after a couple of frustrating hours, i found this. i think you may have saved me a whole lot of time.

thank you!

[Adam Malcontenti-Wilson]

How exactly does the patch work? I didn't think editing the V8's
SConstruct file would do anything in Node 0.8 as I thought it uses gyp
instead.

> --
> 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 nod...@googlegroups.com
> To unsubscribe from this group, send email to
> nodejs+un...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/nodejs?hl=en?hl=en

--
Adam Malcontenti-Wilson

[Paul Tagliamonte]

On Sun, Jul 15, 2012 at 01:01:29PM +1000, Adam Malcontenti-Wilson wrote:
> How exactly does the patch work? I didn't think editing the V8's
> SConstruct file would do anything in Node 0.8 as I thought it uses gyp
> instead.
>
> On Wed, Jul 11, 2012 at 11:13 AM, Geoff Flarity <geoff....@gmail.com> wrote:
> > FYI, I've created a github page with links to a binary and build
> > instructions for getting Node to run on the Raspberry Pi:
> >
> > https://github.com/gflarity/node_pi
> >
> > It takes over 2 hours to build, so go for the binary unless you're paranoid.

What flags did you include? Even though the Pi has a armv6, it does
support the hardfload ABI. Might come in handy.

If you're into trusted binaries, or run the Debian cut, check out the
Debian node package from the kind Raspian folks[1].

It's almost like debian/armhf, but build for the v6, rather then the v7.

If you're ultra-interested, consider contributing :)

HTH,
Paul

[1]: http://archive.raspbian.org/raspbian/pool/main/n/nodejs/

--
.''`. Paul Tagliamonte <pau...@debian.org>
: :' : Proud Debian Developer
`. `'` 4096R / 8F04 9AD8 2C92 066C 7352 D28A 7B58 5B30 807C 2A87
`- http://people.debian.org/~paultag

[Jerry Sievert]

I still had major issues even with node_pi.

I solved them by making some changes in how it is compiled, and moving over to Raspbian.  I have full instructions here:

https://gist.github.com/3119325

I now have a working node binary, working npm (the hardest part), and good hard float.

[Geoff Flarity]

On Saturday, July 14, 2012 11:13:40 PM UTC-4, Paul Tagliamonte wrote:

On Sun, Jul 15, 2012 at 01:01:29PM +1000, Adam Malcontenti-Wilson wrote:
> How exactly does the patch work? I didn't think editing the V8's
> SConstruct file would do anything in Node 0.8 as I thought it uses gyp
> instead.
>
> On Wed, Jul 11, 2012 at 11:13 AM, Geoff Flarity <geoff....@gmail.com> wrote:
> > FYI, I've created a github page with links to a binary and build
> > instructions for getting Node to run on the Raspberry Pi:
> >
> > https://github.com/gflarity/node_pi
> >
> > It takes over 2 hours to build, so go for the binary unless you're paranoid.

What flags did you include? Even though the Pi has a armv6, it does
support the hardfload ABI. Might come in handy.

If you're into trusted binaries, or run the Debian cut, check out the
Debian node package from the kind Raspian folks[1].

It's almost like debian/armhf, but build for the v6, rather then the v7.

If you're ultra-interested, consider contributing :)

I'm glad to hear that there's a Node package for Raspian. As I understand it eventually Raspian will become THE distro for the RPi. At which point this repo I set up won't be necessary. Until then my hope is that this project saves others some time :)

[Geoff Flarity]

The binaries and build instructions work well for me and a few other's who've sent some feedback. Until Raspian is out of testing, please submit issues if you encounter problems.

[Paul Tagliamonte]

On Tue, Jul 17, 2012 at 08:01:45AM -0700, Geoff Flarity wrote:
> On Saturday, July 14, 2012 11:13:40 PM UTC-4, Paul Tagliamonte wrote:
>
> On Sun, Jul 15, 2012 at 01:01:29PM +1000, Adam Malcontenti-Wilson wrote:
> > How exactly does the patch work? I didn't think editing the V8's
> > SConstruct file would do anything in Node 0.8 as I thought it uses gyp
> > instead.
> >
> > On Wed, Jul 11, 2012 at 11:13 AM, Geoff Flarity
> <[1]geoff....@gmail.com> wrote:
> > > FYI, I've created a github page with links to a binary and build
> > > instructions for getting Node to run on the Raspberry Pi:
> > >

> > > [2]https://github.com/gflarity/node_pi

> > >
> > > It takes over 2 hours to build, so go for the binary unless you're
> paranoid.
>
> What flags did you include? Even though the Pi has a armv6, it does
> support the hardfload ABI. Might come in handy.
>
> If you're into trusted binaries, or run the Debian cut, check out the
> Debian node package from the kind Raspian folks[1].
>
> It's almost like debian/armhf, but build for the v6, rather then the v7.
>
> If you're ultra-interested, consider contributing :)
>
> I'm glad to hear that there's a Node package for Raspian. As I understand
> it eventually Raspian will become THE distro for the RPi. At which point
> this repo I set up won't be necessary. Until then my hope is that this
> project saves others some time :)

Yeah! They're really motivated, and there are a few debian-folk
interested in the project (including myself!), as well as a bunch of
raspberry pi foundation folks who would like to see it as the primary
image.

Raspbian basically syncs the Debian archive and rebuilds locally (on a
few beefy ARM build nodes), so if it's in Debian, it'll be in Raspbian!
:)

The chances of it becoming official Debian are slim (since the raspi
stuff is just armhf rebuilt for a minimum of armv6, sorta like if you
were to rebuild a distro that was i686 for the i386), since the
long-term sustainability is shorter then one would expect (keep in mind
Debian releases *roughly* every two years, so how many stable cycles
could one expect this port to live)

Although I'm not very involved with them, I'd be happy to try to answer
questions (or forward the questions) :)

Cheers,
Paul

>
> --
> Job Board: [3]http://jobs.nodejs.org/
> Posting guidelines:
> [4]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 nod...@googlegroups.com
> To unsubscribe from this group, send email to
> nodejs+un...@googlegroups.com
> For more options, visit this group at

> [5]http://groups.google.com/group/nodejs?hl=en?hl=en
>
> References
>
> Visible links
> 1. mailto:geoff....@gmail.com
> 2. https://github.com/gflarity/node_pi
> 3. http://jobs.nodejs.org/
> 4. https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
> 5. http://groups.google.com/group/nodejs?hl=en?hl=en

[Jerry Sievert]

I encountered the same issue as several others: ssl word length was incorrect on the version that was compiled with deps ssl, and wrong version of openssl library in the shared compilation (raspberry pi wheezy release shipped with 0.9.8, while the shared ssl was compiled against 1.0.0).

Once I switched to Raspbian, and changed my compile flags, the issue went away.

I also noticed that I did not actually need the patch.

Raspbian is now an officially released package: http://www.raspberrypi.org/downloads so this could all become a moot point.

[Anand George]

Found  http://elsmorian.com/post/23474168753/node-js-on-raspberry-pi and it was perfect. Only issue was that the original partition was short on space. So had to re-partition and  http://mitchtech.net/easy-gui-install-re-partition-raspberry-pi-on-ubuntu/  was an excellent guide.

--
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 nod...@googlegroups.com
To unsubscribe from this group, send email to
nodejs+un...@googlegroups.com
For more options, visit this group at

http://groups.google.com/group/nodejs?hl=en?hl=en

[Ted Young]

Heyo,

dev_mode is a small utility I've found handy when developing node and rails site. Give it a list of files and directories to watch, and a set of processes to restart, and it will restart everything on a file change. dev_mode pipes all of the process outputs to a single console, with different prompts, which I find helpful.

http://github.com/tedsuo/dev_mode

the config file is somewhat self explanatory: https://github.com/tedsuo/dev_mode/blob/master/example_dev_mode_config.js

I'm sure plenty of people have something like this kicking around, but I thought it would be nice to build a "feature complete" one that was robust. If it's lacking a feature you would like, please open an issue, or create a pull request.

cheers,
Ted

[Mark Hahn]

Did you try node-dev first?  You don't tell it anything.  You just run node and it parses the source code file to find all the require statements and watches the exact files needed. I have used it for a year and it just works.

[Ted Young]

Ah, no, I haven't used node-dev.  But I use dev_mode for a number of non-node projects, so it's a bit different.  

Ted

[Jake Verbaten]

Do you mean node-dev or dev (npm names) ?

[Mark Hahn]

Asking me?  I use node-dev.