Node v0.5.0 (unstable)

287 views
Skip to first unread message

Ryan Dahl

unread,
Jul 5, 2011, 10:25:20 PM7/5/11
to nodejs
2011.07.05, Version 0.5.0 (unstable)

* New non-default libuv backend to support IOCP on Windows. Use
--use-uv to enable.

* deprecate http.cat

* docs improved.

* add child_process.fork

* add fs.utimes() and fs.futimes() support (Ben Noordhuis)

* add process.uptime() (Tom Huges)

* add path.relative (Tony Huang)

* add os.getNetworkInterfaces()

* add remoteAddress and remotePort for client TCP connections (Brian White)

* add secureOptions flag, setting ciphers, SSL_OP_CRYPTOPRO_TLSEXT_BUG
to TLS (Theo Schlossnagle)

* add process.arch (Nathan Rajlich)

* add reading/writing of floats and doubles from/to buffers (Brian White)

* Allow script to be read from stdin

* #477 add Buffer::fill method to do memset (Konstantin Käfer)

* #573 Diffie-Hellman support to crypto module (Håvard Stranden)

* #695 add 'hex' encoding to buffer (isaacs)

* #851 Update how REPLServer uses contexts (Ben Weaver)

* #853 add fs.lchow, fs.lchmod, fs.fchmod, fs.fchown (isaacs)

* #889 Allow to remove all EventEmitter listeners at once (Felix Geisendörfer)

* #926 OpenSSL NPN support (Fedor Indutny)

* #955 Change ^C handling in REPL (isaacs)

* #979 add support for Unix Domain Sockets to HTTP (Mark Cavage)

* #1173 #1170 add AMD, asynchronous module definition (isaacs)

* DTrace probes: support X-Forwarded-For (Dave Pacheco)

Download: http://nodejs.org/dist/node-v0.5.0.tar.gz

Website: http://nodejs.org/docs/v0.5.0/

Documentation: http://nodejs.org/docs/v0.5.0/api/

arunoda.s...@gmail.com

unread,
Jul 5, 2011, 10:33:54 PM7/5/11
to nod...@googlegroups.com
here node is coming to Windows - ready for the massive explosion. :)

--
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



--
Arunoda Susiripala
http://arunoda.com
http://twitter.com/arunoda

Christian Sanz

unread,
Jul 5, 2011, 10:49:37 PM7/5/11
to nod...@googlegroups.com
this is pretty cool.  I haven't used windows in years, but I'm tempted to try it out on a vm. 

Chris Sanz
CTO/Co-founder

Geekli.st
@csanz


Matt

unread,
Jul 5, 2011, 11:11:46 PM7/5/11
to nod...@googlegroups.com
So who is gonna publish an unofficial node.exe then? :-)

Ryan Dahl

unread,
Jul 5, 2011, 11:21:14 PM7/5/11
to nod...@googlegroups.com
On Tue, Jul 5, 2011 at 8:11 PM, Matt <hel...@gmail.com> wrote:
> So who is gonna publish an unofficial node.exe then? :-)

Starting with v0.5.1 (next week) we will be releasing official node.exe builds.

Bert Belder

unread,
Jul 5, 2011, 11:22:21 PM7/5/11
to nodejs
On Jul 6, 5:11 am, Matt <hel...@gmail.com> wrote:
> So who is gonna publish an unofficial node.exe then? :-)

We will - don't worry. Right now the port is far from done, there are
loose ends everywhere.

Nathan Rajlich

unread,
Jul 6, 2011, 12:58:10 AM7/6/11
to nod...@googlegroups.com
Is there gonna be a git tag created for this unstable release?


--

arunoda.s...@gmail.com

unread,
Jul 6, 2011, 2:48:48 AM7/6/11
to nod...@googlegroups.com
Does NPM works with these node releases?

--

Kennyz

unread,
Jul 6, 2011, 12:50:55 PM7/6/11
to nodejs

node 0.5.0 failed compiling on rhel 5 or centos 5
I wonder if you have known the question:

/usr/bin/g++ default/src/node_main_5.o default/src/node_5.o default/
src/node_buffer_5.o default/src/node_javascript_5.o default/src/
node_extensions_5.o default/src/node_http_parser_5.o default/src/
node_constants_5.o default/src/node_events_5.o default/src/
node_file_5.o default/src/node_script_5.o default/src/node_os_5.o
default/src/node_dtrace_5.o default/src/node_string_5.o default/src/
timer_wrap_5.o default/src/tcp_wrap_5.o default/src/cares_wrap_5.o
default/src/node_cares_5.o default/src/node_net_5.o default/src/
node_signal_watcher_5.o default/src/node_stat_watcher_5.o default/src/
node_io_watcher_5.o default/src/node_stdio_5.o default/src/
node_child_process_5.o default/src/node_timer_5.o default/src/
platform_linux_5.o default/src/node_crypto_5.o default/deps/
http_parser/http_parser_3.o -o /home/www/downloads/node-v0.5.0/build/
default/node -pthread -m32 -rdynamic /home/www/downloads/node-v0.5.0/
build/default/libv8.a /home/www/downloads/node-v0.5.0/build/default/
deps/uv/uv.a -L/usr/lib -L/usr/local/lib -L/opt/local/lib -L/usr/sfw/
lib -Wl,-Bdynamic -lrt -lssl -lcrypto -ldl -lutil
/home/www/downloads/node-v0.5.0/build/default/deps/uv/uv.a(ev.o): In
function `evpipe_init':
/home/www/downloads/node-v0.5.0/build/default/deps/uv/ev/ev.c:1296:
undefined reference to `eventfd'
/home/www/downloads/node-v0.5.0/build/default/deps/uv/ev/ev.c:1298:
undefined reference to `eventfd'
/home/www/downloads/node-v0.5.0/build/default/deps/uv/uv.a(ev.o): In
function `ev_signal_start':
/home/www/downloads/node-v0.5.0/build/default/deps/uv/ev/ev.c:2878:
undefined reference to `signalfd'
/home/www/downloads/node-v0.5.0/build/default/deps/uv/ev/ev.c:2880:
undefined reference to `signalfd'
/home/www/downloads/node-v0.5.0/build/default/deps/uv/ev/ev.c:2901:
undefined reference to `signalfd'
/home/www/downloads/node-v0.5.0/build/default/deps/uv/uv.a(ev.o): In
function `ev_signal_stop':
/home/www/downloads/node-v0.5.0/build/default/deps/uv/ev/ev.c:2965:
undefined reference to `signalfd'
/home/www/downloads/node-v0.5.0/build/default/deps/uv/uv.a(eio.o): In
function `eio__sync_file_range':
/home/www/downloads/node-v0.5.0/build/default/deps/uv/eio/eio.c:923:
undefined reference to `sync_file_range'
collect2: ld returned 1 exit status
Waf: Leaving directory `/home/www/downloads/node-v0.5.0/build'
Build failed: -> task failed (err #1):
{task: cxx_link
node_main_5.o,node_5.o,node_buffer_5.o,node_javascript_5.o,node_extensions_5.o,node_http_parser_5.o,node_constants_5.o,node_events_5.o,node_file_5.o,node_script_5.o,node_os_5.o,node_dtrace_5.o,node_string_5.o,timer_wrap_5.o,tcp_wrap_5.o,cares_wrap_5.o,node_cares_5.o,node_net_5.o,node_signal_watcher_5.o,node_stat_watcher_5.o,node_io_watcher_5.o,node_stdio_5.o,node_child_process_5.o,node_timer_5.o,platform_linux_5.o,node_crypto_5.o,http_parser_3.o
-> node}

Ben Noordhuis

unread,
Jul 6, 2011, 1:01:41 PM7/6/11
to nod...@googlegroups.com

Your kernel or glibc is probably too old. Can you post the output of
`uname -a`, `g++ -v` and `yum list glibc`?

Isaac Schlueter

unread,
Jul 6, 2011, 1:08:21 PM7/6/11
to nod...@googlegroups.com
npm will certainly work with any 0.4 release, and should mostly work
with 0.5 releases. However, unstable branch is unstable, so things
might break.

Ryan Dahl

unread,
Jul 6, 2011, 1:34:49 PM7/6/11
to nod...@googlegroups.com

Kennyz

unread,
Jul 6, 2011, 2:02:48 PM7/6/11
to nodejs

I checked node source code, found the requirement: glibc >= 2.7
but there is not problem in node 0.4.9 (libev/libeio)
you know I hardly upgrade my glibc on my servers.


Linux 211125.tosssless.com 2.6.18-238.12.1.el5.028stab091.1 #1 SMP Wed
Jun 1 13:20:25 MSD 2011 i686 i686 i386 GNU/Linux
gcc version 4.1.2 20080704 (Red Hat 4.1.2-50)
glibc.i686
2.5-58.el5_6.4 installed




On Jul 7, 1:01 am, Ben Noordhuis <i...@bnoordhuis.nl> wrote:

Kennyz

unread,
Jul 6, 2011, 2:16:05 PM7/6/11
to nodejs

so what can I do? if you have plan to fix this in these days?

On Jul 7, 1:34 am, Ryan Dahl <r...@tinyclouds.org> wrote:
> > node_main_5.o,node_5.o,node_buffer_5.o,node_javascript_5.o,node_extensions_ 5.o,node_http_parser_5.o,node_constants_5.o,node_events_5.o,node_file_5.o,n ode_script_5.o,node_os_5.o,node_dtrace_5.o,node_string_5.o,timer_wrap_5.o,t cp_wrap_5.o,cares_wrap_5.o,node_cares_5.o,node_net_5.o,node_signal_watcher_ 5.o,node_stat_watcher_5.o,node_io_watcher_5.o,node_stdio_5.o,node_child_pro cess_5.o,node_timer_5.o,platform_linux_5.o,node_crypto_5.o,http_parser_3.o
> > -> node}
>
> https://github.com/joyent/node/blob/2dfed9f69aaa39617f8d559365aa72e05...https://github.com/joyent/node/blob/2dfed9f69aaa39617f8d559365aa72e05...

Ben Noordhuis

unread,
Jul 6, 2011, 2:55:54 PM7/6/11
to nod...@googlegroups.com
On Wed, Jul 6, 2011 at 20:16, Kennyz <kunf...@gmail.com> wrote:
> so what can I do? if you have plan to fix this in these days?

Can you try the attached patch?

0001-Detect-availability-of-newish-linux-syscalls-by-kern.patch

Shigeki Ohtsu

unread,
Jul 6, 2011, 8:43:18 PM7/6/11
to nod...@googlegroups.com
Ben,

With your patch, the node v.0.5.0 can nicely be built on my CentOS 5.5
(kernel-2.6.18) and
it's working fine!

Thanks.

Kennyz

unread,
Jul 7, 2011, 12:45:23 AM7/7/11
to nodejs

It works! thank you very much

On Jul 7, 2:55 am, Ben Noordhuis <i...@bnoordhuis.nl> wrote:
> On Wed, Jul 6, 2011 at 20:16, Kennyz <kunfi...@gmail.com> wrote:
> > so what can I do? if you have plan to fix this in these days?
>
> Can you try the attached patch?
>
>  0001-Detect-availability-of-newish-linux-syscalls-by-kern.patch
> 3KViewDownload
Reply all
Reply to author
Forward
0 new messages