moving to node v6
incanus opened this issue · 5 comments
@springmeyer, what's the latest on this? I had a note to ping you about it in a while, but I don't remember the status. Maybe that you've got things building on v6 now, and I wanted to update this script for that?
I'm 80% of the way there locally. I hit some bugs in apple's clang symlinks with my version of XCode:
$ ls -l /usr/bin/clang++
lrwxr-xr-x 1 root admin 5 Nov 4 23:13 /usr/bin/clang++ -> clang
Basically clang++
should be pointing to clang++ somewhere
. Anyway, that held me up - I'll get back to it today.
Ok, no hurry, just a ping. Keep me updated here?
Currently blocker is this odd one:
$ npm install eio
Mar 22 23:56:19 doozer.local node[89277] <Error>: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
_RegisterApplication(), FAILED TO establish the default connection to the WindowServer, _CGSDefaultConnection() is NULL.
npm http GET https://registry.npmjs.org/eio
npm http 304 https://registry.npmjs.org/eio
npm ERR! cb() never called!
npm ERR!
npm not ok
worked around the eio thing by installing from github.
now hitting:
defaults write $plist SUFeedURL $appcast
fatal: cannot describe '86d1bc4e6876725fe65df4e2e52bdd941fdb479d'
sweet, I see now that is expected for a non tagged branch. So, we've arrived. First working run through on the build machine now complete with node v6. Next up is to turn back on the auto-builds (I've commented the crontab for now, until I get the node v6 stuff merged into master). closing.