gifsicle-bin: Error: autoreconf -ivf

Hi,

I’m using the version 5.3.0 of NPM and getting following error after npm install.

× Error: autoreconf -ivf && ./configure --disable-gifview --disable-gifdiff --prefix=“xxx\node_modules\gifsicle\vendor” --bindir= “xxx\node_modules\gifsicle\vendor” && make install Command failed: autoreconf -ivf ‘autoreconf’ is not recognized as an internal or external command, operable program or batch file.
at ChildProcess.exithandler (child_process.js:211:12)
at emitTwo (events.js:106:13)
at ChildProcess.emit (events.js:192:7)
at maybeClose (internal/child_process.js:890:16)
at Socket.<anonymous> (internal/child_process.js:334:11)
at emitOne (events.js:96:13)
at Socket.emit (events.js:189:7)
at Pipe._handle.close [as _onclose] (net.js:501:12)

About this issue

Original URL
State: open
Created 7 years ago
Reactions: 8
Comments: 16

Most upvoted comments

How about on Windows??

+38

KeithCowan on Dec 5, 2018

The update to 4.0.1 broke installation on Alpine Linux.

Output:
⚠ spawn /root/node_modules/gifsicle/vendor/gifsicle ENOENT
  ⚠ gifsicle pre-build test failed
  ℹ compiling from source
  ✖ Error: Command failed: /bin/sh -c autoreconf -ivf
/bin/sh: autoreconf: not found

(4.0.0 installs fine)

+15

mojavelinux on Jun 18, 2019

Linux: sudo apt-get install libtool automake autoconf nasm OS X: brew install libtool automake autoconf nasm

+10

nwaweru on Feb 22, 2018

How about on Windows??

I’ve the same problem

zzroche on Feb 12, 2019

Linux: sudo apt-get install libtool automake autoconf nasm

In Alpine, apk add libtool automake autoconf nasm is not sufficient as it leads to configure: error: no acceptable C compiler found in $PATH. apk add build-base helped me with this problem, but that for itself says OK: 271 MiB in 52 packages. It really forces staged builds.

lukas-lansky on May 4, 2019

I have the same on Win

wenjq2018 on Jan 25, 2021

Not sure if that will help future users on Windows, but for me, the issue was that I was behind a corporate proxy. Disabling it solved the issue and the pre-build test passed successfully.

hugop95 on Jan 25, 2021

Where should I add this lines ? I have the same error

In the hosts file.

EmanueleCiriachi on Jul 6, 2020

I’m on Windows. As per this comment, adding the following entries to the hosts file temporarily solved the problem for me:

2.74.223.119 github.com 192.30.253.119 gist.github.com 54.169.195.247 api.github.com 185.199.111.153 assets-cdn.github.com 151.101.76.133 raw.githubusercontent.com 151.101.76.133 gist.githubusercontent.com 151.101.76.133 cloud.githubusercontent.com 151.101.76.133 camo.githubusercontent.com 151.101.76.133 avatars0.githubusercontent.com 151.101.76.133 avatars1.githubusercontent.com 151.101.76.133 avatars2.githubusercontent.com 151.101.76.133 avatars3.githubusercontent.com 151.101.76.133 avatars4.githubusercontent.com 151.101.76.133 avatars5.githubusercontent.com 151.101.76.133 avatars6.githubusercontent.com 151.101.76.133 avatars7.githubusercontent.com 151.101.76.133 avatars8.githubusercontent.com

EmanueleCiriachi on Jul 3, 2020

Linux: sudo apt-get install libtool automake autoconf nasm OS X: brew install libtool automake autoconf nasm

fixed my problem.

Pines-Cheng on Jun 28, 2020