Re: Is anyone working on a node.js port?
On 26 November 2010 02:10, Jasper Lievisse Adriaanse jas...@humppa.nl wrote: On Thu, Nov 25, 2010 at 09:25:01AM +0100, David Coppa wrote: On Thu, Nov 25, 2010 at 12:15 AM, Hugo Osvaldo Barrera h...@osvaldobarrera.com.ar wrote: LIB_DEPENDS= ? ?devel/libev \ ? ? ? ? ? ? ? ?devel/libexecinfo Is this working fine with libev-4.01? ciao, david Yes, I've attached the updated port with proper DEPENDS. Could someone please have a look at the deps/v8 stuff which doesn't honor CFLAGS? Is there something else I have to do to get this compiling on 4.8 i386? I untarred it into my ports tree and when I try a 'make' it fails with: Broken dependency: empty directory (DEPENDS devel/libev) *** Error code 1 Stop in /usr/ports/mystuff/devel/node (line 1765 of /usr/ports/infrastructure/mk/bsd.port.mk). *** Error code 1 Stop in /usr/ports/mystuff/devel/node (line 2116 of /usr/ports/infrastructure/mk/bsd.port.mk). Cheers, Mark -- Cheers, Jasper Stay Hungry. Stay Foolish.
Re: Is anyone working on a node.js port?
On Thu, Dec 09, 2010 at 10:10:27AM +1100, mark hellewell wrote: On 26 November 2010 02:10, Jasper Lievisse Adriaanse jas...@humppa.nl wrote: On Thu, Nov 25, 2010 at 09:25:01AM +0100, David Coppa wrote: On Thu, Nov 25, 2010 at 12:15 AM, Hugo Osvaldo Barrera h...@osvaldobarrera.com.ar wrote: LIB_DEPENDS= ? ?devel/libev \ ? ? ? ? ? ? ? ?devel/libexecinfo Is this working fine with libev-4.01? ciao, david Yes, I've attached the updated port with proper DEPENDS. Could someone please have a look at the deps/v8 stuff which doesn't honor CFLAGS? Is there something else I have to do to get this compiling on 4.8 i386? I untarred it into my ports tree and when I try a 'make' it fails with: You'll need a -current tree and system. That's where development happens, not on -release. Broken dependency: empty directory (DEPENDS devel/libev) *** Error code 1 Stop in /usr/ports/mystuff/devel/node (line 1765 of /usr/ports/infrastructure/mk/bsd.port.mk). *** Error code 1 Stop in /usr/ports/mystuff/devel/node (line 2116 of /usr/ports/infrastructure/mk/bsd.port.mk). Cheers, Mark -- Cheers, Jasper Stay Hungry. Stay Foolish. -- Cheers, Jasper Capable, generous men do not create victims, they nurture them.
Re: Is anyone working on a node.js port?
On 9 December 2010 11:15, Jasper Lievisse Adriaanse jas...@humppa.nl wrote: You'll need a -current tree and system. That's where development happens, not on -release. I was afraid that might be the case Thanks anyway, Mark -- Cheers, Jasper Capable, generous men do not create victims, they nurture them.
Re: Is anyone working on a node.js port?
On Thu, Nov 25, 2010 at 12:15 AM, Hugo Osvaldo Barrera h...@osvaldobarrera.com.ar wrote: LIB_DEPENDS= devel/libev \ devel/libexecinfo Is this working fine with libev-4.01? ciao, david
Re: Is anyone working on a node.js port?
On Thu, Nov 25, 2010 at 09:25:01AM +0100, David Coppa wrote: On Thu, Nov 25, 2010 at 12:15 AM, Hugo Osvaldo Barrera h...@osvaldobarrera.com.ar wrote: LIB_DEPENDS= ? ?devel/libev \ ? ? ? ? ? ? ? ?devel/libexecinfo Is this working fine with libev-4.01? ciao, david Yes, I've attached the updated port with proper DEPENDS. Could someone please have a look at the deps/v8 stuff which doesn't honor CFLAGS? -- Cheers, Jasper Stay Hungry. Stay Foolish. node.tgz Description: application/tar-gz
Re: Is anyone working on a node.js port?
On 23/11/10 15:10, Jasper Lievisse Adriaanse wrote: On Tue, Nov 23, 2010 at 10:22:54AM -0500, Jeremy Chase wrote: If no-one is working on a node.js port I'll start working on it. -- Jeremy Chase http://twitter.com/jeremychase Yes, I have attached my WIP which seems to fail on amd64 for Landry@, but works for me. Also, the scons part of the build system doesn't honor CFLAGS, and I've disabled SSL support untill I've added .pc files for OpenSSL, or someone whacked the configure script into taking the right CFLAGS/LDFLAGS for OpenSSL. This is great! I was just reading about node.js about two days ago, and looking forward to trying it out. Builds and runs (at least a simple http hello world) fine on 4.8-current amd64. Good work! :-) -- Hugo Osvaldo Barrera
Re: Is anyone working on a node.js port?
On 24/11/10 20:12, Hugo Osvaldo Barrera wrote: On 23/11/10 15:10, Jasper Lievisse Adriaanse wrote: On Tue, Nov 23, 2010 at 10:22:54AM -0500, Jeremy Chase wrote: If no-one is working on a node.js port I'll start working on it. -- Jeremy Chase http://twitter.com/jeremychase Yes, I have attached my WIP which seems to fail on amd64 for Landry@, but works for me. Also, the scons part of the build system doesn't honor CFLAGS, and I've disabled SSL support untill I've added .pc files for OpenSSL, or someone whacked the configure script into taking the right CFLAGS/LDFLAGS for OpenSSL. This is great! I was just reading about node.js about two days ago, and looking forward to trying it out. Builds and runs (at least a simple http hello world) fine on 4.8-current amd64. Good work! :-) Forgot to mention; I did have to modify Makefile, since I got an error saying old style depends. Sorry, since all the depencencies took so long to build, I kinda forgot by the time I had installed it. LIB_DEPENDS=devel/libev \ devel/libexecinfo -- Hugo Osvaldo Barrera
Is anyone working on a node.js port?
If no-one is working on a node.js port I'll start working on it. -- Jeremy Chase http://twitter.com/jeremychase
Re: Is anyone working on a node.js port?
On Tue, Nov 23, 2010 at 9:22 AM, Jeremy Chase jeremych...@gmail.com wrote: If no-one is working on a node.js port I'll start working on it. -- Jeremy Chase http://twitter.com/jeremychase What's that?
Re: Is anyone working on a node.js port?
On Tue, Nov 23, 2010 at 10:22:54AM -0500, Jeremy Chase wrote: If no-one is working on a node.js port I'll start working on it. -- Jeremy Chase http://twitter.com/jeremychase Yes, I have attached my WIP which seems to fail on amd64 for Landry@, but works for me. Also, the scons part of the build system doesn't honor CFLAGS, and I've disabled SSL support untill I've added .pc files for OpenSSL, or someone whacked the configure script into taking the right CFLAGS/LDFLAGS for OpenSSL. -- Cheers, Jasper Stay Hungry. Stay Foolish. node.tgz Description: application/tar-gz
Re: Is anyone working on a node.js port?
http://nodejs.org/ http://debuggable.com/posts/understanding-node-js:4bd98440-45e4-4a9a-8ef7-0f7ecbdd56cb On Tue, Nov 23, 2010 at 11:11 AM, Abel Abraham Camarillo Ojeda acam...@verlet.org wrote: On Tue, Nov 23, 2010 at 9:22 AM, Jeremy Chase jeremych...@gmail.com wrote: If no-one is working on a node.js port I'll start working on it. -- Jeremy Chase http://twitter.com/jeremychase What's that?
