'module' object has no attribute 'script_main' #363

tj · 2013-12-07T00:21:23Z

all the addons are exploding for some reason:

> [email protected] install /home/ubuntu/projects/api/node_modules/bcrypt
> node-gyp rebuild

Traceback (most recent call last):
  File "/usr/local/lib/node_modules/npm/node_modules/node-gyp/gyp/gyp_main.py", line 18, in <module>
    sys.exit(gyp.script_main())
AttributeError: 'module' object has no attribute 'script_main'
gyp ERR! configure error 
gyp ERR! stack Error: `gyp` failed with exit code: 1
gyp ERR! stack     at ChildProcess.onCpExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:337:16)
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.0-12-generic
gyp ERR! command "node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /home/ubuntu/projects/api/node_modules/bcrypt
gyp ERR! node -v v0.10.22
gyp ERR! node-gyp -v v0.12.1
gyp ERR! not ok 
npm ERR! [email protected] install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the [email protected] install script.
npm ERR! This is most likely a problem with the bcrypt 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:

version info:

[email protected]  /usr/local/lib/node_modules/node-gyp
[email protected]
python 2.7.5+

The text was updated successfully, but these errors were encountered:

TooTallNate · 2013-12-07T01:14:55Z

Hmmm, I haven't seen this. Seems like a borked gyp install somehow. Perhaps try re-installing?

rex · 2013-12-08T01:47:02Z

I can confirm that this is a valid error, and we've tried reinstalling multiple times. Here is our log, running on an Amazon cloud instance:

[root@tools ds]# npm install bcrypt
npm WARN package.json [email protected] No repository field.
info trying registry request attempt 1 at 19:10:26
http GET https://registry.npmjs.org/bcrypt/0.7.4
http 304 https://registry.npmjs.org/bcrypt/0.7.4
info trying registry request attempt 1 at 19:10:27
http GET https://registry.npmjs.org/bindings/1.0.0
http 304 https://registry.npmjs.org/bindings/1.0.0

> [email protected] install /some/folder/node_modules/bcrypt
> node-gyp rebuild

Traceback (most recent call last):
  File "/usr/lib/node_modules/npm/node_modules/node-gyp/gyp/gyp_main.py", line 18, in <module>
    sys.exit(gyp.script_main())
AttributeError: 'module' object has no attribute 'script_main'
gyp ERR! configure error
gyp ERR! stack Error: `gyp` failed with exit code: 1
gyp ERR! stack     at ChildProcess.onCpExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:337:16)
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.4.62-53.42.amzn1.x86_64
gyp ERR! command "node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /some/folder/node_modules/bcrypt
gyp ERR! node -v v0.10.21
gyp ERR! node-gyp -v v0.12.1
gyp ERR! not ok
npm ERR! [email protected] install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] install script.
npm ERR! This is most likely a problem with the bcrypt 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 bcrypt
npm ERR! There is likely additional logging output above.

npm ERR! System Linux 3.4.62-53.42.amzn1.x86_64
npm ERR! command "node" "/usr/bin/npm" "install" "bcrypt"
npm ERR! cwd /some/folder
npm ERR! node -v v0.10.21
npm ERR! npm -v 1.3.15
npm ERR! code ELIFECYCLE
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR!     /some/folder/npm-debug.log
npm ERR! not ok code 0

Any ideas? :-/

tj · 2013-12-08T19:14:26Z

probably just a funky package manager install, I'll try from source or sth tomorrow

TooTallNate · 2013-12-08T19:15:16Z

@visionmedia Is this using the debian nodejs package or something?

rex · 2013-12-09T07:58:33Z

@TooTallNate I'm sorry to keep intruding, but I just wanted to point out that the error I posted was generated by a server using Yum's EPEL package manager on a RedHat-based Amazon image, installed using yum install nodejs. Attempts to use the npm version of node-gyp were fruitless, as I believe that the yum-installed node-gyp is used by default. It is weird, though, because our other servers haven't had any issues with it. To be honest, we're not utilizing dependency version locking nearly as well as we should be (npm shrinkwrap et al), so this could very easily be a breaking change in the API of any one of those dependencies.

That last part is purely speculation, of course, and not very helpful, but I wanted to provide as much feedback as possible.

Edit: I am not sure how much it helps, if at all, but I noticed something weird when running npm -g list:

npm ERR! invalid: [email protected] /usr/lib/node_modules/inherits@2
npm ERR! not ok code 0

Subsequent attempts to npm -g update were not helpful. Though now that I'm thinking about it, I am not sure when last we cleared the npm cache. I'm going to try that and see what happens.

Edit 2: Nope, npm cache clean didn't help. Even ran npm -g install inherits and it didn't fix the dependency bug. I am now completely in agreement with @visionmedia on this one, it seems to be a dependency bug somewhere. @TooTallNate if you need more info about the machine that created this error or anything else, please let me know so I can help get this resolved. :)

Edit 3: For what it's worth, the server in question is running Python version 2.6.8.

dready92 · 2013-12-09T10:14:15Z

Hello,

I got the exact same error trying to install libxmljs 0.8.1, on node 0.10.22 and python 2.7 on ubuntu 13.10.

~/.npm/libxmljs/0.8.1/package$ make
node-gyp configure
gyp info it worked if it ends with ok
gyp info using [email protected]
gyp info using [email protected] | linux | x64
gyp info spawn python
gyp info spawn args [ '/home/mbailly/Documents/perso/node-0.10.22/lib/node_modules/node-gyp/gyp/gyp_main.py',
gyp info spawn args   'binding.gyp',
gyp info spawn args   '-f',
gyp info spawn args   'make',
gyp info spawn args   '-I',
gyp info spawn args   '/home/mbailly/.npm/libxmljs/0.8.1/package/build/config.gypi',
gyp info spawn args   '-I',
gyp info spawn args   '/home/mbailly/Documents/perso/node-0.10.22/lib/node_modules/node-gyp/addon.gypi',
gyp info spawn args   '-I',
gyp info spawn args   '/home/mbailly/.node-gyp/0.10.22/common.gypi',
gyp info spawn args   '-Dlibrary=shared_library',
gyp info spawn args   '-Dvisibility=default',
gyp info spawn args   '-Dnode_root_dir=/home/mbailly/.node-gyp/0.10.22',
gyp info spawn args   '-Dmodule_root_dir=/home/mbailly/.npm/libxmljs/0.8.1/package',
gyp info spawn args   '--depth=.',
gyp info spawn args   '--generator-output',
gyp info spawn args   'build',
gyp info spawn args   '-Goutput_dir=.' ]
Traceback (most recent call last):
  File "/home/mbailly/Documents/perso/node-0.10.22/lib/node_modules/node-gyp/gyp/gyp_main.py", line 18, in <module>
    sys.exit(gyp.script_main())
AttributeError: 'module' object has no attribute 'script_main'
gyp ERR! configure error 
gyp ERR! stack Error: `gyp` failed with exit code: 1
gyp ERR! stack     at ChildProcess.onCpExit (/home/mbailly/Documents/perso/node-0.10.22/lib/node_modules/node-gyp/lib/configure.js:337:16)
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.0-13-generic
gyp ERR! command "node" "/home/mbailly/Documents/perso/node/bin/node-gyp" "configure"
gyp ERR! cwd /home/mbailly/.npm/libxmljs/0.8.1/package
gyp ERR! node -v v0.10.22
gyp ERR! node-gyp -v v0.12.1
gyp ERR! not ok 
make: *** [build] Erreur 1

Please help !

tj · 2013-12-09T17:00:40Z

yeah the package manager ones seem pretty borked

tj · 2013-12-09T17:08:34Z

yup re-install worked for me, so I guess just don't ever use the package managers haha

laithshadeed · 2013-12-14T15:20:51Z

For me it got fixed by replacing python2.7 by python2.6. As per https://code.google.com/p/gyp/source/browse/trunk/DEPS#19 , it seems that gyp depends on python 2.6

On Ubuntu Saucy:
sudo add-apt-repository ppa:fkrull/deadsnakes
sudo apt-get update
sudo apt-get install python2.6
sudo update-alternatives --install /usr/bin/python python /usr/bin/python2.6 20
sudo update-alternatives --install /usr/bin/python python /usr/bin/python2.7 10

you can switch between 2.6 & 2.7 using:
sudo update-alternatives --config python

Btw I installed node using ppa:chris-lea/node.js

I hope this helps somebody.

Lujaw · 2013-12-25T05:30:27Z

@laithshadeed Thanks, it solved the issue for me..

scottkellie · 2014-01-03T14:07:30Z

@laithshadeed Also repaired my build on Linux mint 16 :) Thanks was driving me crazy!

springmeyer · 2014-01-14T02:51:07Z

Also just hit this on windows: in my case it was because I had a globally installed gyp version which was conflicting with the one inside node-gyp. I found my global install with python -c 'import gyp; print gyp.__file__' and removing it fixed the problem.

matzoe · 2014-01-15T08:46:04Z

@springmeyer same to me. I just removed gyp to solve this problem.

walidsynclio · 2014-01-17T14:57:15Z

I have installed node using sudo apt-get install nodejs
suso apt-get install libexpat1-dev
sudo npm install node-expat

Same Issue

root@abul-VirtualBox:~/node-xmpp-bosh# sudo npm install node-expat
npm WARN package.json [email protected] 'repositories' (plural) Not supported.
npm WARN package.json Please pick one as the 'repository' field
npm WARN package.json [email protected] 'repositories' (plural) Not supported.
npm WARN package.json Please pick one as the 'repository' field
npm WARN package.json [email protected] 'repositories' (plural) Not supported.
npm WARN package.json Please pick one as the 'repository' field
npm http GET https://registry.npmjs.org/node-expat
npm http 304 https://registry.npmjs.org/node-expat

> [email protected] install /root/node-xmpp-bosh/node_modules/node-expat
> node-gyp rebuild

Traceback (most recent call last):
  File "/usr/lib/node_modules/npm/node_modules/node-gyp/gyp/gyp_main.py", line 18, in <module>
    sys.exit(gyp.script_main())
AttributeError: 'module' object has no attribute 'script_main'
gyp ERR! configure error 
gyp ERR! stack Error: `gyp` failed with exit code: 1
gyp ERR! stack     at ChildProcess.onCpExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:337:16)
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.5.0-17-generic
gyp ERR! command "node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /root/node-xmpp-bosh/node_modules/node-expat
gyp ERR! node -v v0.10.24
gyp ERR! node-gyp -v v0.12.1
gyp ERR! not ok 
npm ERR! [email protected] install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the [email protected] install script.
npm ERR! This is most likely a problem with the node-expat 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 node-expat
npm ERR! There is likely additional logging output above.

npm ERR! System Linux 3.5.0-17-generic
npm ERR! command "/usr/bin/node" "/usr/bin/npm" "install" "node-expat"
npm ERR! cwd /root/node-xmpp-bosh
npm ERR! node -v v0.10.24
npm ERR! npm -v 1.3.21
npm ERR! code ELIFECYCLE
npm ERR! 
npm ERR! Additional logging details can be found in:
npm ERR!     /root/node-xmpp-bosh/npm-debug.log
npm ERR! not ok code 0

lloydwatkin · 2014-01-17T15:53:25Z

Using node-gyp@0.11.X on a fresh ubuntu 13.10 install works just fine (at least for node-expat).

tellnes · 2014-01-20T21:03:20Z

I'm seeing the same error. Downgrading to Python 2.6.x fixed it. @laithshadeed Thanks.

loque1 · 2014-01-23T10:58:46Z

This might occur on Ubuntu based systems if you have installed gyp i.e. sudo apt-get install gyp
Try removing it then trying npm install again

kbjr · 2014-01-23T19:04:26Z

I was originally getting the error above, but changed to python 2.6 as suggested, and now I'm getting this different error:

$ npm install
npm WARN package.json [email protected] No repository field.
npm http GET https://registry.npmjs.org/bcrypt/0.7.3
npm http 304 https://registry.npmjs.org/bcrypt/0.7.3
npm http GET https://registry.npmjs.org/bindings/1.0.0
npm http 304 https://registry.npmjs.org/bindings/1.0.0

> [email protected] install /home/james/Projects/Greatvines/cube/node_modules/bcrypt
> node-gyp rebuild

make: Entering directory `/home/james/Projects/Greatvines/cube/node_modules/bcrypt/build'
  CXX(target) Release/obj.target/bcrypt_lib/src/blowfish.o
  CXX(target) Release/obj.target/bcrypt_lib/src/bcrypt.o
  CXX(target) Release/obj.target/bcrypt_lib/src/bcrypt_node.o
../src/bcrypt_node.cc: In function ‘v8::Handle<v8::Value> {anonymous}::GenerateSalt(const v8::Arguments&)’:
../src/bcrypt_node.cc:257:74: error: invalid conversion from ‘void (*)(uv_work_t*) {aka void (*)(uv_work_s*)}’ to ‘uv_after_work_cb {aka void (*)(uv_work_s*, int)}’ [-fpermissive]
     uv_queue_work(uv_default_loop(), req, GenSaltAsync, GenSaltAsyncAfter);
                                                                          ^
In file included from /home/james/.node-gyp/0.10.24/src/node.h:61:0,
                 from ../src/bcrypt_node.cc:31:
/home/james/.node-gyp/0.10.24/deps/uv/include/uv.h:1432:15: error:   initializing argument 4 of ‘int uv_queue_work(uv_loop_t*, uv_work_t*, uv_work_cb, uv_after_work_cb)’ [-fpermissive]
 UV_EXTERN int uv_queue_work(uv_loop_t* loop, uv_work_t* req,
               ^
../src/bcrypt_node.cc: In function ‘v8::Handle<v8::Value> {anonymous}::Encrypt(const v8::Arguments&)’:
../src/bcrypt_node.cc:337:74: error: invalid conversion from ‘void (*)(uv_work_t*) {aka void (*)(uv_work_s*)}’ to ‘uv_after_work_cb {aka void (*)(uv_work_s*, int)}’ [-fpermissive]
     uv_queue_work(uv_default_loop(), req, EncryptAsync, EncryptAsyncAfter);
                                                                          ^
In file included from /home/james/.node-gyp/0.10.24/src/node.h:61:0,
                 from ../src/bcrypt_node.cc:31:
/home/james/.node-gyp/0.10.24/deps/uv/include/uv.h:1432:15: error:   initializing argument 4 of ‘int uv_queue_work(uv_loop_t*, uv_work_t*, uv_work_cb, uv_after_work_cb)’ [-fpermissive]
 UV_EXTERN int uv_queue_work(uv_loop_t* loop, uv_work_t* req,
               ^
../src/bcrypt_node.cc: In function ‘v8::Handle<v8::Value> {anonymous}::Compare(const v8::Arguments&)’:
../src/bcrypt_node.cc:431:74: error: invalid conversion from ‘void (*)(uv_work_t*) {aka void (*)(uv_work_s*)}’ to ‘uv_after_work_cb {aka void (*)(uv_work_s*, int)}’ [-fpermissive]
     uv_queue_work(uv_default_loop(), req, CompareAsync, CompareAsyncAfter);
                                                                          ^
In file included from /home/james/.node-gyp/0.10.24/src/node.h:61:0,
                 from ../src/bcrypt_node.cc:31:
/home/james/.node-gyp/0.10.24/deps/uv/include/uv.h:1432:15: error:   initializing argument 4 of ‘int uv_queue_work(uv_loop_t*, uv_work_t*, uv_work_cb, uv_after_work_cb)’ [-fpermissive]
 UV_EXTERN int uv_queue_work(uv_loop_t* loop, uv_work_t* req,
               ^
make: *** [Release/obj.target/bcrypt_lib/src/bcrypt_node.o] Error 1
make: Leaving directory `/home/james/Projects/Greatvines/cube/node_modules/bcrypt/build'
gyp ERR! build error 
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/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.0-15-generic
gyp ERR! command "node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /home/james/Projects/Greatvines/cube/node_modules/bcrypt
gyp ERR! node -v v0.10.24
gyp ERR! node-gyp -v v0.12.1
gyp ERR! not ok 
npm ERR! [email protected] install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the [email protected] install script.
npm ERR! This is most likely a problem with the bcrypt 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 bcrypt
npm ERR! There is likely additional logging output above.

npm ERR! System Linux 3.11.0-15-generic
npm ERR! command "/usr/bin/node" "/usr/bin/npm" "install"
npm ERR! cwd /home/james/Projects/Greatvines/cube
npm ERR! node -v v0.10.24
npm ERR! npm -v 1.3.21
npm ERR! code ELIFECYCLE
npm ERR! 
npm ERR! Additional logging details can be found in:
npm ERR!     /home/james/Projects/Greatvines/cube/npm-debug.log
npm ERR! not ok code 0

rex · 2014-01-24T10:39:16Z

Just wanted to leave specific instructions here for myself and any other lost souls that aren't sure how to fix this.

The credit for this fix goes to @springmeyer. The server I've tested this on is Centos 6.5 x64.

Find the locally installed gyp python module that is causing problems

$ python -c 'import gyp; print gyp.__file__'

/usr/lib/python2.6/site-packages/gyp/__init__.pyc

Move or rename the folder so that python can't find it
2) $ mv /usr/lib/python2.6/site-packages/gyp /usr/lib/python2.6/site-packages/gyp_backup

Ensure that python can't find it
3) $ python -c 'import gyp; print gyp.__file__'

Traceback (most recent call last):
  File "<string>", line 1, in <module>
ImportError: No module named gyp

Good! Now try reinstalling!
4) $ npm install

npm http GET https://registry.npmjs.org/hiredis/-/hiredis-0.1.16.tgz
npm http GET https://registry.npmjs.org/redis/-/redis-0.10.0.tgz
npm http 200 https://registry.npmjs.org/hiredis/-/hiredis-0.1.16.tgz
npm http 200 https://registry.npmjs.org/redis/-/redis-0.10.0.tgz
npm http GET https://registry.npmjs.org/bindings/-/bindings-1.1.1.tgz
npm http 200 https://registry.npmjs.org/bindings/-/bindings-1.1.1.tgz

> [email protected] install /srv/www/prex.io/node_modules/hiredis
> node-gyp rebuild

make: Entering directory `/srv/www/prex.io/node_modules/hiredis/build'
  CC(target) Release/obj.target/hiredis/deps/hiredis/hiredis.o
  CC(target) Release/obj.target/hiredis/deps/hiredis/net.o
  CC(target) Release/obj.target/hiredis/deps/hiredis/sds.o
  CC(target) Release/obj.target/hiredis/deps/hiredis/async.o
  AR(target) Release/obj.target/deps/hiredis.a
  COPY Release/hiredis.a
  CXX(target) Release/obj.target/hiredis/src/hiredis.o
  CXX(target) Release/obj.target/hiredis/src/reader.o
  SOLINK_MODULE(target) Release/obj.target/hiredis.node
  SOLINK_MODULE(target) Release/obj.target/hiredis.node: Finished
  COPY Release/hiredis.node
make: Leaving directory `/srv/www/prex.io/node_modules/hiredis/build'
[email protected] node_modules/hiredis
��� [email protected]

hapees · 2014-06-10T20:41:37Z

on Fedora 20:
yum remove gyp
did the job - thank you

d0b1010r · 2015-04-16T10:05:40Z

Just had the same issue on an Amazon Elastic Beanstalk Instance (64bit Amazon Linux 2014.03 v1.1.0 running Node.js). Had installed globally via sudo yum install nodejs npm --enablerepo=epel as I needed bunyan to view logs. This borked up my deployments with the same error (AttributeError: 'module' object has no attribute 'script_main').

Solved by running sudo yum remove gyp.noarch. Thanks guys!

Beforehands, I tried to remove node via sudo yum remove nodejs npm --enablerepo=epel but this did not remove the gyp installation which affected the build.

Jbudone · 2015-05-02T21:15:15Z

Same problem on Amazon EC2, fixed w/ sudo npm -g install node-gyp

darkoverlordofdata · 2015-05-04T16:11:55Z

This worked on Mint 17, also. Thanks!!! I tried upgrading npm, node, switching py versions. It just shuffled the problem around. I thought I was going nuts. This fixed it:

sudo apt-get remove gyp

LogeshEswar · 2015-09-08T09:34:30Z

while running codebox I got an following error Module did not self-register the i used the code node-gyp rebuild. Now its showing this error.

gyp: binding.gyp not found (cwd: /home/logesh/code/megam/workspace/codebox) while trying to load binding.gyp
gyp ERR! configure error
gyp ERR! stack Error: gyp failed with exit code: 1
gyp ERR! stack at ChildProcess.onCpExit (/usr/share/node-gyp/lib/configure.js:344:16)
gyp ERR! stack at ChildProcess.EventEmitter.emit (events.js:98:17)
gyp ERR! stack at Process.ChildProcess._handle.onexit (child_process.js:797:12)
gyp ERR! System Linux 3.19.0-15-generic
gyp ERR! command "nodejs" "/usr/bin/node-gyp" "rebuild"
gyp ERR! cwd /home/logesh/code/megam/workspace/codebox
gyp ERR! node -v v0.10.25
gyp ERR! node-gyp -v v0.12.2
gyp ERR! not ok
logesh@logesh-Aspire-E1-431:/code/megam/workspace/codebox$ node -v
v0.12.4
logesh@logesh-Aspire-E1-431:/code/megam/workspace/codebox$ npm -v
1.4.21

tj closed this as completed Dec 9, 2013

franckuser16 mentioned this issue Dec 15, 2013

Ubuntu saucy, node-gyp rebuild error ? brianmcd/contextify#92

Closed

sprijk mentioned this issue Dec 22, 2013

npm install fails on nodejs v0.10.24 JustinTulloss/zeromq.node#264

Closed

diunko mentioned this issue Dec 24, 2013

node-gyp build broken on fedora 20 cocaine/cocaine-framework-nodejs#14

Closed

andrewrk mentioned this issue Jan 3, 2014

Problem with installing andrewrk/groovebasin#139

Closed

adam-s mentioned this issue Jan 4, 2014

Installation of [email protected] fails on OSX 10.9 (node v0.11.8) brianmcd/contextify#91

Closed

springmeyer mentioned this issue Jan 14, 2014

AttributeError: 'module' object has no attribute 'script_main' #370

Closed

ratpik mentioned this issue Jan 16, 2014

Rebuild issue on Ubuntu #383

Closed

lloydwatkin mentioned this issue Jan 17, 2014

NO able to install node-expat xmppo/node-expat#84

Closed

deadprogram mentioned this issue Jan 26, 2014

Unable to install module hybridgroup/cylon-digispark#1

Closed

Koromori mentioned this issue Feb 1, 2014

Symbol segfault_handler_native_module not found ddopson/node-segfault-handler#9

Closed

kkoopa mentioned this issue Jun 11, 2014

"Error: Module did not self-register" running first example of main github page (Node 0.11.13) Automattic/node-canvas#433

Closed

baudehlo mentioned this issue Jun 18, 2014

Installation errors haraka/Haraka#607

Closed

stonith mentioned this issue Jun 21, 2014

Error: Cannot find module './ber/index' hipchat/hubot-hipchat#177

Closed

solo999 mentioned this issue Jun 25, 2014

Error when deploy meteor 0.8.2 on centos with kadira 2.4.4 package installed meteorhacks/kadira#7

Closed

arunoda mentioned this issue Jun 26, 2014

Meteor Installation Issue on Linux meteor/meteor#2249

Closed

flannelhead mentioned this issue Jul 4, 2014

Error installing Atom on Fedora 20 64b atom/atom#2824

Closed

TooTallNate mentioned this issue Jul 16, 2014

node-gyp rebuild error (as part of PouchDB) Level/leveldown#86

Closed

kevinsawicki mentioned this issue Jul 22, 2014

Issue during atom build with pathwatcher atom/node-pathwatcher#37

Closed

kynan mentioned this issue Aug 31, 2014

Npm fails installation in (ubuntu 13.10) taarifa/TaarifaWaterpoints#148

Closed

lloydwatkin mentioned this issue Sep 2, 2014

Build problem on Debian xmppo/node-stringprep#60

Closed

kevinsawicki mentioned this issue Sep 11, 2014

Unable to build Atom on Fedora 19; script/build fails. atom/atom#2731

Closed

meetmagdalene mentioned this issue Sep 18, 2014

Still problems installing with node-gyp hipchat/hubot-hipchat#197

Closed

am11 mentioned this issue Oct 14, 2014

npm ERR! Failed at the [email protected] install script. sass/node-sass#428

Closed

zdne mentioned this issue Nov 25, 2014

npm install fails on 64bit openSuse apiaryio/protagonist#15

Closed

MiniGod mentioned this issue Jan 21, 2015

Make Python prefer bundled files nwjs/nw-gyp#58

Closed

sandhose mentioned this issue Mar 18, 2015

Impossible de builder le front zestedesavoir/zds-site#2443

Closed

krishnasrinivas mentioned this issue Jun 14, 2015

Install issues on Ubuntu 14.04 butlerx/wetty#19

Closed

This was referenced Jun 18, 2015

npm install error bitpay/insight#631

Closed

npm install error gyp rebuild bitpay/insight-api#324

Closed

madmod mentioned this issue Sep 1, 2015

Issues with Harmony homebridge/homebridge#131

Closed

This was referenced Jan 16, 2016

gyp WARN install got an error hughsk/atom-npm-install#18

Closed

Installation error atom/node-oniguruma#47

Open

Fail when installing from NPM atom/node-oniguruma#44

Open

artemgrygor mentioned this issue Mar 10, 2016

Implement own screenshot generator using node-webshot deweyapp/dewey-server#6

Merged

watilde mentioned this issue Apr 7, 2016

Ubuntuで、npm install onigurumaする際にエラーが出る watilde/npm#10

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

'module' object has no attribute 'script_main' #363

'module' object has no attribute 'script_main' #363

tj commented Dec 7, 2013

TooTallNate commented Dec 7, 2013

rex commented Dec 8, 2013

tj commented Dec 8, 2013

TooTallNate commented Dec 8, 2013

rex commented Dec 9, 2013

dready92 commented Dec 9, 2013

tj commented Dec 9, 2013

tj commented Dec 9, 2013

laithshadeed commented Dec 14, 2013

Lujaw commented Dec 25, 2013

scottkellie commented Jan 3, 2014

springmeyer commented Jan 14, 2014

matzoe commented Jan 15, 2014

walidsynclio commented Jan 17, 2014

lloydwatkin commented Jan 17, 2014

tellnes commented Jan 20, 2014

loque1 commented Jan 23, 2014

kbjr commented Jan 23, 2014

rex commented Jan 24, 2014

hapees commented Jun 10, 2014

d0b1010r commented Apr 16, 2015

Jbudone commented May 2, 2015

darkoverlordofdata commented May 4, 2015

LogeshEswar commented Sep 8, 2015

'module' object has no attribute 'script_main' #363

'module' object has no attribute 'script_main' #363

Comments

tj commented Dec 7, 2013

TooTallNate commented Dec 7, 2013

rex commented Dec 8, 2013

tj commented Dec 8, 2013

TooTallNate commented Dec 8, 2013

rex commented Dec 9, 2013

dready92 commented Dec 9, 2013

tj commented Dec 9, 2013

tj commented Dec 9, 2013

laithshadeed commented Dec 14, 2013

Lujaw commented Dec 25, 2013

scottkellie commented Jan 3, 2014

springmeyer commented Jan 14, 2014

matzoe commented Jan 15, 2014

walidsynclio commented Jan 17, 2014

lloydwatkin commented Jan 17, 2014

tellnes commented Jan 20, 2014

loque1 commented Jan 23, 2014

kbjr commented Jan 23, 2014

rex commented Jan 24, 2014

hapees commented Jun 10, 2014

d0b1010r commented Apr 16, 2015

Jbudone commented May 2, 2015

darkoverlordofdata commented May 4, 2015

LogeshEswar commented Sep 8, 2015