Skip to content
This repository has been archived by the owner on Dec 15, 2022. It is now read-only.

Issue during atom build with pathwatcher #37

Closed
Ablu opened this issue Jul 22, 2014 · 12 comments
Closed

Issue during atom build with pathwatcher #37

Ablu opened this issue Jul 22, 2014 · 12 comments

Comments

@Ablu
Copy link

Ablu commented Jul 22, 2014

Hi,

trying to build latest master of atom fails with an issue with pathwatcher.

I do not understand it. But maybe you do? :)

If you need more info let me know what you need:

ablu@localhost: ~/atom (master)$ script/build
Node: v0.10.29
npm: v1.4.13
Installing build modules...
Installing apm...
Installing modules ✗
> atom@0.117.0 preinstall /home/ablu/atom
> node -e 'process.exit(0)'


> pathwatcher@1.5.0 install /home/ablu/atom/node_modules/pathwatcher
> node-gyp rebuild


> git-utils@1.6.0 install /home/ablu/atom/node_modules/git-utils
> node-gyp rebuild


Traceback (most recent call last):
  File "/home/ablu/atom/apm/node_modules/atom-package-manager/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 (/home/ablu/atom/apm/node_modules/atom-package-manager/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:797:12)
gyp ERR! System Linux 3.15.4-200.fc20.x86_64
gyp ERR! command "node" "/home/ablu/atom/apm/node_modules/atom-package-manager/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /home/ablu/atom/node_modules/pathwatcher
gyp ERR! node -v v0.10.26
gyp ERR! node-gyp -v v0.12.2
gyp ERR! not ok
npm ERR! pathwatcher@1.5.0 install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the pathwatcher@1.5.0 install script.
npm ERR! This is most likely a problem with the pathwatcher 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 pathwatcher
npm ERR! There is likely additional logging output above.

npm ERR! System Linux 3.15.4-200.fc20.x86_64
npm ERR! command "/home/ablu/atom/apm/node_modules/atom-package-manager/bin/node" "/home/ablu/atom/apm/node_modules/atom-package-manager/node_modules/npm/bin/npm-cli.js" "--globalconfig" "/home/ablu/atom/apm/node_modules/atom-package-manager/.apmrc" "--userconfig" "/home/ablu/.atom/.apmrc" "install" "--target=0.11.10" "--arch=x64" "--quiet"
npm ERR! cwd /home/ablu/atom
npm ERR! node -v v0.10.26
npm ERR! npm -v 1.4.4
npm ERR! code ELIFECYCLE
Traceback (most recent call last):
  File "/home/ablu/atom/apm/node_modules/atom-package-manager/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 (/home/ablu/atom/apm/node_modules/atom-package-manager/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:797:12)
gyp ERR! System Linux 3.15.4-200.fc20.x86_64
gyp ERR! command "node" "/home/ablu/atom/apm/node_modules/atom-package-manager/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /home/ablu/atom/node_modules/git-utils
gyp ERR! node -v v0.10.26
gyp ERR! node-gyp -v v0.12.2
gyp ERR! not ok
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR!     /home/ablu/atom/npm-debug.log
npm ERR! not ok code 0

Regards,
Ablu

@kevinsawicki
Copy link
Contributor

What version of python are you using? The build does not work with python 3.

@Ablu
Copy link
Author

Ablu commented Jul 22, 2014

I put python 2.7.5 first in path:

ablu@localhost: ~$ python --version
Python 2.7.5

@kevinsawicki
Copy link
Contributor

Sorry, it looks like python 2.6 is required on Linux, can you try with that version?

@Ablu
Copy link
Author

Ablu commented Jul 22, 2014

Need to compile that. Though 2.6 is no longer available for recent fedora versions. You should definitely at least support 2.7 (better 3). But I will test it anyway.

@kevinsawicki
Copy link
Contributor

It isn't this library that requires Python 2.6, it is the native module build system that ships with node, node-gyp.

@Ablu
Copy link
Author

Ablu commented Jul 22, 2014

Hm. Why was I able to build atom then before with the same version of fedora (so also 2.7)?

@kevinsawicki
Copy link
Contributor

Not sure, maybe this isn't a Python 2.6 problem, the stack trace just looked an awful lot like nodejs/node-gyp#363 which mentions python 2.6 being needed or removing the OS install of gyp.

@Ablu
Copy link
Author

Ablu commented Jul 22, 2014

I cannot easily build python 2.6 due to missing dependencies. Also that version of python is now about 4 years outdated. Also I built atom before on this system (and not using python 2.6). So i doubt that this should be the issue (and if so it was introduced later).

@kevinsawicki
Copy link
Contributor

Does your system have gyp installed?

@Ablu
Copy link
Author

Ablu commented Jul 22, 2014

Yes. It is the fedora gyp from the system repository. Currently checking out wether that makes issues.

Version: 0.1-0.11.1617svn.fc20
npm: 1.3.6-5.fc20

That info is also listed in my very first message at the bottom of the log

@Ablu
Copy link
Author

Ablu commented Jul 22, 2014

Fixed it by replacing my system gyp with the npm one (though the npm one had some issues to install and also installed to /lib even on 64bit). But at least it works and i garbaged my nice root a bit more :P

Thanks a lot for your help!

Regards,
Erik

@Ablu Ablu closed this as completed Jul 22, 2014
@kevinsawicki
Copy link
Contributor

Sure thing, glad to hear things are working now.

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

No branches or pull requests

2 participants