Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SyntaxError: In src/server/server.coffee, reserved word "static" on line 5 #12

Closed
ldolse opened this issue Apr 26, 2012 · 7 comments
Closed

Comments

@ldolse
Copy link

ldolse commented Apr 26, 2012

Hi, trying to install groovebasin on Puppy Linux, I built node and npm from scratch on the system. Getting the error in the issue title when I try to install. I'm not sure if this is a legitimate bug or if I'm missing some key dependency.

Complete install log:

npm http GET https://registry.npmjs.org/groovebasin
npm http 304 https://registry.npmjs.org/groovebasin
npm http GET https://registry.npmjs.org/node-static
npm http GET https://registry.npmjs.org/coffee-script
npm http GET https://registry.npmjs.org/socket.io
npm http GET https://registry.npmjs.org/handlebars
npm http GET https://registry.npmjs.org/lastfm
npm http GET https://registry.npmjs.org/formidable
npm http GET https://registry.npmjs.org/mkdirp
npm http GET https://registry.npmjs.org/node.extend
npm http GET https://registry.npmjs.org/stylus
npm http 304 https://registry.npmjs.org/lastfm
npm http 304 https://registry.npmjs.org/node-static
npm http 304 https://registry.npmjs.org/coffee-script
npm http 304 https://registry.npmjs.org/socket.io
npm http 304 https://registry.npmjs.org/handlebars
npm http 304 https://registry.npmjs.org/formidable
npm http 304 https://registry.npmjs.org/mkdirp
npm http 304 https://registry.npmjs.org/node.extend
npm http 304 https://registry.npmjs.org/stylus
npm http GET https://registry.npmjs.org/uglify-js
npm http GET https://registry.npmjs.org/optimist
npm http GET https://registry.npmjs.org/underscore
npm http GET https://registry.npmjs.org/policyfile/0.0.4
npm http GET https://registry.npmjs.org/redis/0.6.7
npm http GET https://registry.npmjs.org/socket.io-client/0.9.6
npm http GET https://registry.npmjs.org/cssom
npm http GET https://registry.npmjs.org/debug
npm http 304 https://registry.npmjs.org/redis/0.6.7
npm http 304 https://registry.npmjs.org/policyfile/0.0.4
npm http 304 https://registry.npmjs.org/underscore
npm http 304 https://registry.npmjs.org/socket.io-client/0.9.6
npm http 304 https://registry.npmjs.org/debug
npm http 304 https://registry.npmjs.org/cssom
npm http GET https://registry.npmjs.org/uglify-js/1.2.5
npm http GET https://registry.npmjs.org/ws
npm http GET https://registry.npmjs.org/xmlhttprequest/1.2.2
npm http GET https://registry.npmjs.org/active-x-obfuscator/0.0.1
npm http 304 https://registry.npmjs.org/ws
npm http 304 https://registry.npmjs.org/uglify-js/1.2.5
npm http 304 https://registry.npmjs.org/active-x-obfuscator/0.0.1
npm http 304 https://registry.npmjs.org/uglify-js
npm http 304 https://registry.npmjs.org/xmlhttprequest/1.2.2
npm http GET https://registry.npmjs.org/zeparser/0.0.5

> ws@0.4.13 preinstall /root/node_modules/groovebasin/node_modules/socket.io/node_modules/socket.io-client/node_modules/ws
> make

node-waf configure build
Checking for program g++ or c++          : /usr/bin/g++ 
Checking for program cpp                 : /usr/bin/cpp 
Checking for program ar                  : /usr/bin/ar 
Checking for program ranlib              : /usr/bin/ranlib 
Checking for g++                         : ok  
Checking for node path                   : ok /usr/bin/node 
Checking for node prefix                 : ok /usr 
'configure' finished successfully (0.031s)
Waf: Entering directory `/root/node_modules/groovebasin/node_modules/socket.io/node_modules/socket.io-client/node_modules/ws/build'
[1/4] cxx: src/validation.cc -> build/Release/src/validation_1.o
[2/4] cxx: src/bufferutil.cc -> build/Release/src/bufferutil_2.o
[3/4] cxx_link: build/Release/src/validation_1.o -> build/Release/validation.node
[4/4] cxx_link: build/Release/src/bufferutil_2.o -> build/Release/bufferutil.node
Waf: Leaving directory `/root/node_modules/groovebasin/node_modules/socket.io/node_modules/socket.io-client/node_modules/ws/build'
'build' finished successfully (0.566s)
npm http GET https://registry.npmjs.org/commander
npm http GET https://registry.npmjs.org/options
npm http 304 https://registry.npmjs.org/zeparser/0.0.5
npm http 304 https://registry.npmjs.org/options
npm http 304 https://registry.npmjs.org/commander
npm http 304 https://registry.npmjs.org/optimist
npm http GET https://registry.npmjs.org/wordwrap
npm http 304 https://registry.npmjs.org/wordwrap

> groovebasin@0.0.5 install /root/node_modules/groovebasin
> make

mkdir -p lib
node_modules/coffee-script/bin/coffee -p -c src/shared/mpd.coffee >lib/mpd.js.tmp
mv lib/mpd.js{.tmp,}
node_modules/coffee-script/bin/coffee -p -c src/server/mpdconf.coffee >lib/mpdconf.js.tmp
mv lib/mpdconf.js{.tmp,}
node_modules/coffee-script/bin/coffee -p -c src/server/plugin.coffee >lib/plugin.js.tmp
mv lib/plugin.js{.tmp,}
mkdir -p lib/plugins
node_modules/coffee-script/bin/coffee -p -c src/server/plugins/chat.coffee >lib/plugins/chat.js.tmp
mv lib/plugins/chat.js{.tmp,}
node_modules/coffee-script/bin/coffee -p -c src/server/plugins/download.coffee >lib/plugins/download.js.tmp
mv lib/plugins/download.js{.tmp,}
node_modules/coffee-script/bin/coffee -p -c src/server/plugins/dynamicmode.coffee >lib/plugins/dynamicmode.js.tmp
mv lib/plugins/dynamicmode.js{.tmp,}
node_modules/coffee-script/bin/coffee -p -c src/server/plugins/lastfm.coffee >lib/plugins/lastfm.js.tmp
mv lib/plugins/lastfm.js{.tmp,}
node_modules/coffee-script/bin/coffee -p -c src/server/plugins/stream.coffee >lib/plugins/stream.js.tmp
mv lib/plugins/stream.js{.tmp,}
node_modules/coffee-script/bin/coffee -p -c src/server/plugins/upload.coffee >lib/plugins/upload.js.tmp
mv lib/plugins/upload.js{.tmp,}
node_modules/coffee-script/bin/coffee -p -c src/server/server.coffee >server.js.tmp
SyntaxError: In src/server/server.coffee, reserved word "static" on line 5
    at SyntaxError (unknown source)
    at Lexer.error (/root/node_modules/groovebasin/node_modules/coffee-script/lib/coffee-script/lexer.js:686:13)
    at Lexer.identifierToken (/root/node_modules/groovebasin/node_modules/coffee-script/lib/coffee-script/lexer.js:88:16)
    at Lexer.tokenize (/root/node_modules/groovebasin/node_modules/coffee-script/lib/coffee-script/lexer.js:35:19)
    at Object.compile (/root/node_modules/groovebasin/node_modules/coffee-script/lib/coffee-script/coffee-script.js:43:32)
    at /root/node_modules/groovebasin/node_modules/coffee-script/lib/coffee-script/command.js:182:33
    at /root/node_modules/groovebasin/node_modules/coffee-script/lib/coffee-script/command.js:152:18
    at [object Object].<anonymous> (fs.js:123:5)
    at [object Object].emit (events.js:64:17)
    at Object.oncomplete (fs.js:1181:12)
make: *** [server.js] Error 1

npm ERR! groovebasin@0.0.5 install: `make`
npm ERR! `sh "-c" "make"` failed with 2
npm ERR! 
npm ERR! Failed at the groovebasin@0.0.5 install script.
npm ERR! This is most likely a problem with the groovebasin package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     make
npm ERR! You can get their info via:
npm ERR!     npm owner ls groovebasin
npm ERR! There is likely additional logging output above.
npm ERR! 
npm ERR! System Linux 2.6.39
npm ERR! command "node" "/usr/bin/npm" "install" "groovebasin"
npm ERR! cwd /root
npm ERR! node -v v0.6.15
npm ERR! npm -v 1.1.18
npm ERR! code ELIFECYCLE
npm ERR! message groovebasin@0.0.5 install: `make`
npm ERR! message `sh "-c" "make"` failed with 2
npm ERR! errno {}
npm ERR! 
npm ERR! Additional logging details can be found in:
npm ERR!     /root/npm-debug.log
npm not ok
@thejoshwolfe
Copy link
Collaborator

It looks like ce76984 fixed this issue. Try pulling and giving it another go.

@ldolse
Copy link
Author

ldolse commented Apr 27, 2012

I suspected that change may have fixed it - sorry I'm not well versed in node/npm - what's the process for installing the latest from Git?

edit - nevermind, figured out the instructions from this other issue comment:
#11 (comment)

I now have it running, though getting the 'subscribe' error mentioned in that discussion. Are the changes in your mpd git branch being migrated into the main mpd branch, and/or will those messages be muted a bit in a future release for users of the stable mpd release?

@thejoshwolfe
Copy link
Collaborator

Ok. This is like the 4th time people have run into the "subscribe" error. We need to make the readme clearer.

@superjoe30 The readme currently points to git://github.com/superjoe30/mpd.git, but I've been using git://git.musicpd.org/master/mpd.git with no problems. Why are we pointing at your fork instead of the original branch?

Also, I'm putting notes in the readme now that alert people that we depend on new features of mpd.

@andrewrk
Copy link
Owner

There used to be an error in the master of git://git.musicpd.org/master/mpd.git but there isn't one now. You can compile from either.

I should just release another version of groovebasin which will solve the "static" problem.

@andrewrk
Copy link
Owner

I released package version 0.0.6, should solve this problem.

@ldolse
Copy link
Author

ldolse commented Apr 27, 2012

Thanks! The readme was indeed a bit unclear about a few of these points. The issue is the first line says it depends on the version from source (now clearer by stating .17.x), but then the second line (Line 53) states that certain features are only available if you compile from source - implying that .16.x should still work, just without all features. And aside from having to click 'ok' to get past the subscribe error it did seem to work fine with .16.x. I didn't get a chance to beat on it that much just yet, but the first impressions have been great.

@thejoshwolfe
Copy link
Collaborator

Thanks for the feedback. I'm pretty sure we don't support interfacing with mpd 0.16. If it seems to work a little, it's a coincidence. I've updated the readme again in light of your suggestions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants