I think I'm at the limit of my investigative powers in this area, but if anybody else has an inkling of what the difference between these two mechanisms might be, that could be useful.
Npm gifsicle download#
Running the missing aclocal-1.14 command in that path still fails, but for whatever reason this is not executed when I download manually. Even though I only have automake and aclocal version 1.11.1.
Npm gifsicle install#
configure -disable-gifview -disable-gifdiff -prefix="" -bindir="" & make install There does not appear to be any aclocal version checking happening and compilation is completed successfully.
When I download the source manually to a local path, extract it, and run the exact same command. configure does execute the /missing aclocal-1.14 command and fail. In my testing, when gifsicle is download and compiled via the bin-build package, the. CentOS 6.5 is stuck at automake/aclocal version 1.11.1, while gifsicle appears to require 1.14 in order to build from source. Npm ERR! Additional logging details can be found in:Īutomake and autoconf are installed on the box, they are just not the required versions. Npm ERR! command "/usr/share/node/bin/node" "/usr/share/node/bin/npm" "install" ERR! cwd /home/vagrant Npm ERR! There is likely additional logging output above. Npm ERR! Tell the author that this fails on your system:
Npm ERR! This is most likely a problem with the gifsicle package, Npm ERR! Failed at the postinstall script. (/home/vagrant/node_modules/gifsicle/node_modules/bin-build/node_modules/download/node_modules/decompress/node_modules/tar/lib/extract.js:57:8)Īt /home/vagrant/node_modules/gifsicle/node_modules/bin-build/node_modules/download/node_modules/decompress/node_modules/tar/node_modules/fstream/lib/dir-writer.js:39:8 (/home/vagrant/node_modules/gifsicle/node_modules/bin-build/node_modules/download/node_modules/decompress/node_modules/tar/lib/parse.js:47:8)Īt BlockStream._emitChunk (/home/vagrant/node_modules/gifsicle/node_modules/bin-build/node_modules/download/node_modules/decompress/node_modules/tar/node_modules/block-stream/block-stream.js:145:10)Īt BlockStream.resume (/home/vagrant/node_modules/gifsicle/node_modules/bin-build/node_modules/download/node_modules/decompress/node_modules/tar/node_modules/block-stream/block-stream.js:58:15)Īt (/home/vagrant/node_modules/gifsicle/node_modules/bin-build/node_modules/download/node_modules/decompress/node_modules/tar/node_modules/fstream/lib/reader.js:255:34)Īt DirWriter. Throw er // Unhandled stream error in pipe.Īt Extract.Parse._startEntry (/home/vagrant/node_modules/gifsicle/node_modules/bin-build/node_modules/download/node_modules/decompress/node_modules/tar/lib/parse.js:145:13)Īt Extract.Parse._process (/home/vagrant/node_modules/gifsicle/node_modules/bin-build/node_modules/download/node_modules/decompress/node_modules/tar/lib/parse.js:127:12)Īt BlockStream. ⚠ pre-build test failed, compiling from source. The Command failed just write some ips for hosts, then npm install will be worked.Npm install was working for me last Friday, but it no longer postinstall /home/vagrant/node_modules/gifsicle Then, try npm cache clean -fand ipconfig/flushdns.Īs long as can ping with github domains, the problem will be solved. That is best way to connect with github and other domains. COPY ‼ getaddrinfo ENOENT Īs in above two lines, the problem is can't connect with.
Npm gifsicle windows#
As predicted, there is someone got the same errors.īe unexpected, It's not a problem with windows or autoconf. So, the best way is go to the gifsicle issues. The problem appeared when installing gifsicle, The Hexo-all-minifier used it too.
There is still has the errors with npm install. I never tried to installed cygwin.Īnyway, i installed successfully. So, i tried installing cygwin, And that is difficult for me. In the beginning, i thought the problem is my windows can't run autoconf. The error logs with npm install: COPY ‼ getaddrinfo ENOENT In a long time, i'm used to Hexo-all-minifier to optimization blog.
0 kommentar(er)
