Floobits / atom-term3

Open Terminal tabs in Atom. Fork of Term package
Other
88 stars 17 forks source link

Installing failed #43

Open dadex opened 8 years ago

dadex commented 8 years ago

here is the output

ptyw.js@0.3.7 install C:\Users\Weiwei\AppData\Local\Temp\apm-install-dir-116222-12908-114irv3\node_modules\term3\node_modules\ptyw.js node-gyp rebuild

C:\Users\Weiwei\AppData\Local\Temp\apm-install-dir-116222-12908-114irv3\node_modules\term3\node_modules\ptyw.js>if not defined npm_config_node_gyp (node "C:\Users\Weiwei\AppData\Local\atom\app-1.6.0\resources\app\apm\node_modules\npm\bin\node-gyp-bin....\node_modules\node-gyp\bin\node-gyp.js" rebuild ) else (node rebuild ) �ڴ˽��򷽰���һ������һ����Ŀ����Ҫ���ò������ɣ������ӡ�/m�����ء� MSBUILD : error MSB3428: δ�ܼ��� Visual C++ ������VCBuild.exe����Ҫ���������⣬1) ��װ .NET Framework 2.0 SDK��2) ��װ Microsoft Visual Studio 2005���� 3) ��������������װ��������λ�ã��뽫��λ�����ӵ�ϵͳ·���С� [C:\Users\Weiwei\AppData\Local\Temp\apm-install-dir-116222-12908-114irv3\node_modules\term3\node_modules\ptyw.js\build\binding.sln] MSBUILD : error MSB3428: δ�ܼ��� Visual C++ ������VCBuild.exe����Ҫ���������⣬1) ��װ .NET Framework 2.0 SDK��2) ��װ Microsoft Visual Studio 2005���� 3) ��������������װ��������λ�ã��뽫��λ�����ӵ�ϵͳ·���С� [C:\Users\Weiwei\AppData\Local\Temp\apm-install-dir-116222-12908-114irv3\node_modules\term3\node_modules\ptyw.js\build\binding.sln]

npm WARN deprecated react-tools@0.11.2: react-tools is deprecated. For more information, visit https://fb.me/react-tools-deprecated npm WARN deprecated graceful-fs@2.0.3: graceful-fs version 3 and before will fail on newer node releases. Please update to graceful-fs@^4.0.0 as soon as possible. npm ERR! Windows_NT 6.2.9200 npm ERR! argv "C:\Users\Weiwei\AppData\Local\atom\app-1.6.0\resources\app\apm\bin\node.exe" "C:\Users\Weiwei\AppData\Local\atom\app-1.6.0\resources\app\apm\node_modules\npm\bin\npm-cli.js" "--globalconfig" "C:\Users\Weiwei.atom.apm.apmrc" "--userconfig" "C:\Users\Weiwei.atom.apmrc" "install" "C:\Users\Weiwei\AppData\Local\Temp\d-116222-12908-mgejb7\package.tgz" "--target=0.34.5" "--arch=ia32" npm ERR! node v0.10.40 npm ERR! npm v2.13.3 npm ERR! code ELIFECYCLE

npm ERR! ptyw.js@0.3.7 install: node-gyp rebuild npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the ptyw.js@0.3.7 install script 'node-gyp rebuild'. npm ERR! This is most likely a problem with the ptyw.js 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 ptyw.js npm ERR! There is likely additional logging output above.

sompylasar commented 8 years ago

+1


> ptyw.js@0.3.8 install C:\Users\user\AppData\Local\Temp\apm-install-dir-116412-6448-1gmvkxp\node_modules\term3\node_modules\ptyw.js
> node-gyp rebuild

C:\Users\user\AppData\Local\Temp\apm-install-dir-116412-6448-1gmvkxp\node_modules\term3\node_modules\ptyw.js>if not defined npm_config_node_gyp (node "C:\Users\user\AppData\Local\atom\app-1.7.3\resources\app\apm\node_modules\npm\bin\node-gyp-bin\\..\..\node_modules\node-gyp\bin\node-gyp.js" rebuild )  else (node  rebuild ) 

npm WARN deprecated react-tools@0.11.2: react-tools is deprecated. For more information, visit https://fb.me/react-tools-deprecated
npm WARN deprecated graceful-fs@2.0.3: graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to graceful-fs@^4.0.0 as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.
npm ERR! Windows_NT 6.1.7601
npm ERR! argv "C:\\Users\\user\\AppData\\Local\\atom\\app-1.7.3\\resources\\app\\apm\\bin\\node.exe" "C:\\Users\\user\\AppData\\Local\\atom\\app-1.7.3\\resources\\app\\apm\\node_modules\\npm\\bin\\npm-cli.js" "--globalconfig" "C:\\Users\\user\\.atom\\.apm\\.apmrc" "--userconfig" "C:\\Users\\user\\.atom\\.apmrc" "install" "C:\\Users\\user\\AppData\\Local\\Temp\\d-116412-6448-2zmcf\\package.tgz" "--target=0.36.8" "--arch=ia32"
npm ERR! node v0.10.40
npm ERR! npm  v2.13.3
npm ERR! code ELIFECYCLE

npm ERR! ptyw.js@0.3.8 install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the ptyw.js@0.3.8 install script 'node-gyp rebuild'.
npm ERR! This is most likely a problem with the ptyw.js 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 ptyw.js
npm ERR! There is likely additional logging output above.
Temmermans commented 8 years ago

Same issue here. node-gyp rebuild fails. +1

ggreer commented 8 years ago

This is super frustrating for me, as I can't reproduce it on any system. I've tried my Mac, my Ubuntu laptop, my Windows machine, and even other people's macs. None of them have had any issues installing the plugin.

orionlee commented 7 years ago

I ran into similar problems. Here is how I believe I got it working:

  1. Install MS components needed for build: I used windows-build-tools
    1. Download and install .Net Framework 4.5 (needed for windows 7 machine)
    2. install windows build tools npm install --global windows-build-tools
    3. In my case, I also ran into an issue windows-build-tools#12, which I fixed by letting the install (WindowsBuildTools_Run.exe) finished, and did the following
npm config set msvs_version 2015
npm config set python "%USERPROFILE%\.windows-build-tools\python27\python.exe"
  1. After step 1 was completed, I still ran into __pfnDliNotifyHook2 redefinition error during compilation. It is fixed by upgrading npm with npm install -g npm . See: https://github.com/Microsoft/nodejs-guidelines/blob/master/windows-environment.md#compiling-native-addon-modules
  2. ptwy.js could finally be built successfully, and thus atom-term3.
pjgoodall commented 7 years ago

Atom documentation suggests this procedure: windows build tools

"It will install Windows Build Tools by Felix Rieseberg without needing a separate Node.js installation [...] Both installations are conflict-free, meaning that they do not mess with existing installations of Visual Studio, C++ Build Tools, or Python. If you see anything that indiciates otherwise, please file a bug"