npm install email-templates fails #42
Comments
|
+1 getting the same error message on node v0.10.22 |
|
Fixed Check the prerequis https://github.com/TooTallNate/node-gyp I should add g++ on Unix |
|
So all you need is g++ package installed on your system to resolve this? Can we mark as closed? @jfroffice @skeganga |
|
I have g++, doesn't work. On 13 Dec 2013, at 8:03 am, niftylettuce notifications@github.com wrote: So all you need is g++ package installed on your system to resolve this? — |
|
Installs fine for me. Here is log output. https://gist.github.com/niftylettuce/a900699b8d29879f3c91 |
|
@skeganga What version of Node, NPM, and what operating system and version are you on? |
|
$ node --version On 13 December 2013 08:22, niftylettuce notifications@github.com wrote:
|
|
@skeganga have you all the dependencies here? https://github.com/TooTallNate/node-gyp why not just try installing node-gyp in a blank dir to see if node-gyp is the issue? you could also try installing contextify by itself too. mkdir some-dir
cd some-dir
npm init
npm install -S node-gyp
npm install -S contextify |
|
Seems like it might be contextify $ npm install node-gyp - works fine npm http GET https://registry.npmjs.org/contextify
make: Entering directory npm ERR! System Linux 3.11.9-200.fc19.x86_64 On 13 December 2013 08:27, niftylettuce notifications@github.com wrote:
|
|
@skeganga can you manually try using contextify 0.1.5 instead of 0.1.6? i've checked on jsdom and contextify github issues and they both have tons of reported issues like this. |
|
$ npm install contextify@0.1.5 npm http GET https://registry.npmjs.org/contextify/0.1.5
make: Entering directory npm ERR! System Linux 3.11.9-200.fc19.x86_64 On 13 December 2013 08:44, niftylettuce notifications@github.com wrote:
|
|
any luck with your search? I'm not sure if it's a Fedora specific issue or On Thu, Dec 12, 2013 at 4:47 PM, skeganga notifications@github.com wrote:
|
|
try |
|
@skeganga did you see @jfroffice comment? #42 (comment) |
|
$ make -v |
|
Should Contextify be being used anyway? I see a comment in the Contextify issues: "As of node 0.11.7, Contextify has basically been merged into node itself. Can you use the built-in vm module instead?" |
|
In the spirit of diagnosing the issue, this is more-or-less where I'm at: $ npm install contextify # fails I downloaded the source: $ git clone https://github.com/brianmcd/contextify.git Contextify makefile uses node-waf which has been replaced with node-gyp (as far as I can tell) $ npm install -g node-gyp $ make |
Fixed!It is an issue when building on nfs mounts. Can be solved by setting LINK=g++ npm install email-templatesor export LINK=g++
npm install email-templatesFound the sugar here: nodejs/node-gyp#147 (comment) |
|
Great!!!!!! Awesome!!!!!
|
|
@skeganga this didn't help for me, still crashing when installing. The weird thing is that when I do this is environment dependent, running on my MBA it works fine, running on Ubuntu in AWS instance, it fails. |
|
@mderazon not sure, how did you install node on your Ubuntu AWS instance? did you install all dependencies? |
which dependencies do you have in mind ? |
|
that's fine. you said npm install email-templates succeeds, so what is the On Thu, Dec 26, 2013 at 1:24 PM, Michael Derazon
|
|
any error stack ? Could you give version when you execute following command |
|
@niftylettuce installing email-templates fails on first attempt, then on second attempt it succeeds @jfroffice sure here's the output for the rest : |
|
I am running my server with upstart and my startup script is the following : (it runs as # create /etc/init/paas.conf
echo 'start on runlevel [2345]
stop on runlevel [06]
respawn
pre-start script
exec >/dev/kmsg 2>&1
REPO=git@github.com:xxx/yyy
mkdir -p /var/log
mkdir -p /var/www
echo "Fetching app from $REPO"
girror $REPO /var/www # this just fetches a bare repo from $REPO
if [ -f /var/www/package.json ]; then
echo "Installing npm modules"
cd /var/www
npm install
fi
if [ -f /var/www/bower.json ]; then
echo "Installing bower dependencies"
cd /var/www
bower install --allow-root -f
fi
end script
post-stop script
exec >/dev/kmsg 2>&1
echo "stopped"
end script
script
exec >/dev/kmsg 2>&1
export NODE_ENV=production
export port=80
echo "Starting app.js on port 80"
cd /var/www
node app.js
end script' > /etc/init/paas.confbasically, whenever ubuntu detects the process has terminated for any reason, it fetches the code from github, does npm install and and respawns it.
|
|
Seems to be documented error. try to make something like in your script |
IT WORKED :)@jfroffice this did the trick, I will add it to my startup script. Don't exactly know what's the use of this library in Anyway, thanks ! and thank you @niftylettuce 👍 |
|
Anyone have a solution for windows? |
|
@blowsie this issue is closed, maybe it would be a better idea to open a new one, with versions of node, npm, email-templates and the stack trace of the error you're getting (if any) |
|
@blowsie I'd recommend to not use windows at all with Node/programming. Get an Ubuntu Vagrant/VirtualBox image set up and just use that to run your node app. |
|
-1 |
|
@jfroffice why -1? |
|
I think NodeJS power is to work on everything common platform |
|
@jfroffice when developing you should mirror your production environment I'd think -- which means you should use some *nix based platform. otherwise if you dev on windows you may get different results in production when hosted somewhere, usually all hosts/vps are *nix based since that's industry standard. |
|
@niftylettuce Thanks, but I disagree, there are plenty of windows + node environments around. Including cloud based services like azure. |
|
@blowsie I don't support Windows with any of my projects and not many in the Node community do. The standard is to use Vagrant/VirtualBox with an Ubuntu instance if you are on Windows, otherwise you run into constant issues. You need to use Cygbin for instance just to get a *nix like command line... it's not worth it IMO. |
I can't install email-templates via npm
I'm using a prefixed install of node v0.10.22 on fedora x86-64 linux.
verbose npm install output is here: http://www.filedropper.com/out_1
npm-debug.log here: http://www.filedropper.com/npm-debug
terse output below:
npm WARN package.json jobsearch@0.0.0 No description
npm WARN package.json jobsearch@0.0.0 No repository field.
npm WARN package.json jobsearch@0.0.0 No README data
npm WARN package.json crypto@0.0.3 crypto is also the name of a node core module.
npm http GET https://registry.npmjs.org/email-templates
npm http 304 https://registry.npmjs.org/email-templates
npm http GET https://registry.npmjs.org/async/0.1.22
npm http GET https://registry.npmjs.org/underscore/1.3.3
npm http GET https://registry.npmjs.org/ejs/0.8.3
npm http GET https://registry.npmjs.org/juice
npm http 304 https://registry.npmjs.org/underscore/1.3.3
npm http 304 https://registry.npmjs.org/async/0.1.22
npm http 304 https://registry.npmjs.org/juice
npm http 304 https://registry.npmjs.org/ejs/0.8.3
npm http GET https://registry.npmjs.org/cssom
npm http GET https://registry.npmjs.org/superagent
npm http GET https://registry.npmjs.org/batch
npm http GET https://registry.npmjs.org/jsdom
npm http GET https://registry.npmjs.org/commander
npm http GET https://registry.npmjs.org/slick
npm http 304 https://registry.npmjs.org/batch
npm http 304 https://registry.npmjs.org/jsdom
npm http 304 https://registry.npmjs.org/cssom
npm http 304 https://registry.npmjs.org/superagent
npm http 304 https://registry.npmjs.org/commander
npm http 304 https://registry.npmjs.org/slick
npm http GET https://registry.npmjs.org/keypress
npm http GET https://registry.npmjs.org/qs/0.6.5
npm http GET https://registry.npmjs.org/formidable/1.0.9
npm http GET https://registry.npmjs.org/mime/1.2.5
npm http GET https://registry.npmjs.org/methods/0.0.1
npm http GET https://registry.npmjs.org/emitter-component/1.0.0
npm http GET https://registry.npmjs.org/cssstyle
npm http GET https://registry.npmjs.org/htmlparser
npm http GET https://registry.npmjs.org/nwmatcher
npm http GET https://registry.npmjs.org/cookiejar/1.3.0
npm http GET https://registry.npmjs.org/request
npm http GET https://registry.npmjs.org/debug
npm http GET https://registry.npmjs.org/contextify
npm http 304 https://registry.npmjs.org/keypress
npm http 304 https://registry.npmjs.org/qs/0.6.5
npm http 304 https://registry.npmjs.org/methods/0.0.1
npm http 304 https://registry.npmjs.org/formidable/1.0.9
npm http 304 https://registry.npmjs.org/emitter-component/1.0.0
npm http 304 https://registry.npmjs.org/mime/1.2.5
npm http 304 https://registry.npmjs.org/cssstyle
npm http 304 https://registry.npmjs.org/htmlparser
npm http 304 https://registry.npmjs.org/cookiejar/1.3.0
npm http 304 https://registry.npmjs.org/nwmatcher
npm http 304 https://registry.npmjs.org/request
npm http 304 https://registry.npmjs.org/debug
npm http 304 https://registry.npmjs.org/contextify
npm http GET https://registry.npmjs.org/bindings
npm http GET https://registry.npmjs.org/qs
npm http GET https://registry.npmjs.org/json-stringify-safe
npm http GET https://registry.npmjs.org/forever-agent
npm http GET https://registry.npmjs.org/mime
npm http GET https://registry.npmjs.org/node-uuid
npm http GET https://registry.npmjs.org/tough-cookie
npm http GET https://registry.npmjs.org/form-data
npm http GET https://registry.npmjs.org/tunnel-agent
npm http GET https://registry.npmjs.org/oauth-sign
npm http GET https://registry.npmjs.org/http-signature
npm http GET https://registry.npmjs.org/hawk
npm http GET https://registry.npmjs.org/aws-sign2
npm http 304 https://registry.npmjs.org/json-stringify-safe
npm http 304 https://registry.npmjs.org/qs
npm http 304 https://registry.npmjs.org/bindings
npm http 304 https://registry.npmjs.org/forever-agent
npm http 304 https://registry.npmjs.org/mime
make: Entering directory
/mnt/raid/src/web/jobSearch/node_modules/email-templates/node_modules/juice/node_modules/jsdom/node_modules/contextify/build' CXX(target) Release/obj.target/contextify/src/contextify.o SOLINK_MODULE(target) Release/obj.target/contextify.node flock: ./Release/linker.lock: Bad file descriptor make: *** [Release/obj.target/contextify.node] Error 65 make: Leaving directory/mnt/raid/src/web/jobSearch/node_modules/email-templates/node_modules/juice/node_modules/jsdom/node_modules/contextify/build'gyp ERR! build error
gyp ERR! stack Error:
makefailed with exit code: 2gyp ERR! stack at ChildProcess.onExit (/mnt/raid/local/node-v0.10.22-linux-x64/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:267:23)
gyp ERR! stack at ChildProcess.EventEmitter.emit (events.js:98:17)
gyp ERR! stack at Process.ChildProcess._handle.onexit (child_process.js:789:12)
gyp ERR! System Linux 3.11.9-200.fc19.x86_64
gyp ERR! command "node" "/mnt/raid/local/node-v0.10.22-linux-x64/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /mnt/raid/src/web/jobSearch/node_modules/email-templates/node_modules/juice/node_modules/jsdom/node_modules/contextify
gyp ERR! node -v v0.10.22
gyp ERR! node-gyp -v v0.11.0
gyp ERR! not ok
npm http 304 https://registry.npmjs.org/node-uuid
npm http 304 https://registry.npmjs.org/tough-cookie
npm http 304 https://registry.npmjs.org/form-data
npm http 304 https://registry.npmjs.org/tunnel-agent
npm http 304 https://registry.npmjs.org/oauth-sign
npm http 304 https://registry.npmjs.org/hawk
npm http 304 https://registry.npmjs.org/aws-sign2
npm http 304 https://registry.npmjs.org/http-signature
npm http GET https://registry.npmjs.org/combined-stream
npm http GET https://registry.npmjs.org/async
npm http GET https://registry.npmjs.org/assert-plus/0.1.2
npm http GET https://registry.npmjs.org/asn1/0.1.11
npm http GET https://registry.npmjs.org/ctype/0.5.2
npm http GET https://registry.npmjs.org/punycode
npm http GET https://registry.npmjs.org/cryptiles
npm http GET https://registry.npmjs.org/sntp
npm http GET https://registry.npmjs.org/boom
npm http GET https://registry.npmjs.org/hoek
npm ERR! contextify@0.1.6 install:
node-gyp rebuildnpm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the contextify@0.1.6 install script.
npm ERR! This is most likely a problem with the contextify package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-gyp rebuild
npm ERR! You can get their info via:
npm ERR! npm owner ls contextify
npm ERR! There is likely additional logging output above.
npm ERR! System Linux 3.11.9-200.fc19.x86_64
npm ERR! command "/mnt/raid/local/bin/node" "/mnt/raid/local/bin/npm" "install" "email-templates"
npm ERR! cwd /mnt/raid/src/web/jobSearch
npm ERR! node -v v0.10.22
npm ERR! npm -v 1.3.14
npm ERR! code ELIFECYCLE
npm http 304 https://registry.npmjs.org/async
npm http 304 https://registry.npmjs.org/combined-stream
npm http 304 https://registry.npmjs.org/assert-plus/0.1.2
npm http 304 https://registry.npmjs.org/asn1/0.1.11
npm http 304 https://registry.npmjs.org/ctype/0.5.2
npm http GET https://registry.npmjs.org/delayed-stream/0.0.5
npm http 304 https://registry.npmjs.org/punycode
npm http 304 https://registry.npmjs.org/cryptiles
npm http 304 https://registry.npmjs.org/sntp
npm http 304 https://registry.npmjs.org/boom
npm http 304 https://registry.npmjs.org/hoek
npm http 304 https://registry.npmjs.org/delayed-stream/0.0.5
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /mnt/raid/src/web/jobSearch/npm-debug.log
npm ERR! not ok code 0
The text was updated successfully, but these errors were encountered: