On Fri, Apr 19, 2013 at 10:11 PM, Jeffrey Chimene <[email protected]> wrote: > On 04/19/2013 12:57 PM, Ben Noordhuis wrote: >> On Fri, Apr 19, 2013 at 7:54 PM, Jeff Chimene <[email protected]> wrote: >>> Hi, >>> >>> I'm interested in porting nodejs to IA64, specifically OpenVMS. >>> Would nodejs owners be interested in integrating the resulting patches >>> (assuming the patches meet the qualifications described in the contributing >>> guidelines). >>> I realize this question also has to be asked of Google w/r/t/ V8, libUV as >>> well as other, TBD parts of the kit. >>> >>> Cheers, >>> jec >> Are you backed by a company or is this a personal project? > It's a personal project, in the sense that I'm not paid to do this. > I/We have access to/support of HP VMS engineering. The sourceforge > project is vms-ports. It's been underway for some time. I expect that > this will be done using HP's Porting Center. > >> I ask >> because your first task would be to port V8 (and get it accepted >> upstream + maintain it) and that's a massive undertaking, something >> that is unlikely to succeed when it's just a side project. > Agreed. The project does have a robust way of managing patches [*]. > However, it would be best to try to get upstream to accept them. I will > reach out to Google to see if they are interested. > > * > via logical name search lists >> V8 is essentially a JS to machine code compiler so you'd have to write >> a backend that speaks IA64. Have a look at the code in e.g. >> deps/v8/src/x64/ to get a taste of what that involves. > So there's something there to look at. >> Libuv is relatively trivial in comparison, that's probably no more >> than a few days of work. Patches are welcome. > Good. >> Node.js itself should require only minimal changes; nearly all >> platform-specific code lives in libuv. > I got that impression. It looks like it's been aggressive about platform > independence. To wit, I came across an interesting reference w/r/t/ > excluding fork(); which will help w/ the VMS port. > >> FWIW, I'm working on a port of node.js to Mozilla's SpiderMonkey >> engine with the express goal of supporting a wider range of >> architectures and operating systems. >> >> I'm primarily targeting SPARC, POWER and IA64 and the operating >> systems that run on them; AIX, HP-UX, Linux. Maybe OpenVMS should be >> on that list, too. I hadn't considered it until now. > I'm willing to help move that forward. I'm starting w/IA64, although > Alpha should also be on that list. I really don't see a reason to try VAX. >> If or when the project will be released is anybody's guess, however. >> I'm working on it in my off hours right now and those are rare. > Please consider my offer to help. > > Thank-you for your response! > > Cheers, > jec
Thanks. :-) I'll ping you when I have something that's stable enough to boot into a REPL. I'm still working out the basic infrastructure, like how to recreate the node's Buffer class with SpiderMonkey's API. -- -- 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.
