Cannot install sharp on ARM64 Odroid Ubuntu
See original GitHub issueHi ,
I’ve been trying to install sharp on Ubuntu 16.04 Xenial installed on an Odroid but am not able to get the dependency libvips installed on it. Which obviously is causing installation of sharp to fail.
I’m running node v7.9.x and npm is v4.2.0.
Here is the output when I try to install sharp “sudo npm install sharp”
sharp@0.17.3 install /home/pankaj/node_modules/sharp node-gyp rebuild
ERROR: Download of https://dl.bintray.com/lovell/sharp/libvips-8.4.2-linux-arm64.tar.gz failed: Response code 404 (Not Found)
gyp: Call to ‘LDD_VERSION=“ldd (Ubuntu GLIBC 2.23-0ubuntu3) 2.23
Copyright © 2016 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Written by Roland McGrath and Ulrich Drepper.” node -e "require(’./binding’).download_vips()"’ returned exit status 1 while in binding.gyp. 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/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:308:16)
gyp ERR! stack at emitTwo (events.js:106:13)
gyp ERR! stack at ChildProcess.emit (events.js:194:7)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:215:12)
gyp ERR! System Linux 3.14.29
gyp ERR! command “/usr/bin/nodejs” “/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js” “rebuild”
gyp ERR! cwd /home/pankaj/node_modules/sharp
gyp ERR! node -v v7.9.0
gyp ERR! node-gyp -v v3.5.0
gyp ERR! not ok
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.1.1: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:“linux”,“arch”:“arm64”})
npm WARN enoent ENOENT: no such file or directory, open ‘/home/pankaj/package.json’
npm WARN pankaj No description
npm WARN pankaj No repository field.
npm WARN pankaj No README data
npm WARN pankaj No license field.
npm ERR! Linux 3.14.29
npm ERR! argv “/usr/bin/nodejs” “/usr/bin/npm” “install” “sharp”
npm ERR! node v7.9.0
npm ERR! npm v4.2.0
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! sharp@0.17.3 install: node-gyp rebuild
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the sharp@0.17.3 install script ‘node-gyp rebuild’.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the sharp 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 information on how to open an issue for this project with:
npm ERR! npm bugs sharp
npm ERR! Or if that isn’t available, you can get their info via:
npm ERR! npm owner ls sharp
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request: npm ERR! /home/pankaj/.npm/_logs/2017-04-17T08_03_38_451Z-debug.log
I followed the steps
Added repository: sudo add-apt-repository -y ppa:lovell/trusty-backport-vips
gpg: keyring /tmp/tmp33esnaad/secring.gpg' created gpg: keyring /tmp/tmp33esnaad/pubring.gpg’ created
gpg: requesting key 21794330 from hkp server keyserver.ubuntu.com
gpg: /tmp/tmp33esnaad/trustdb.gpg: trustdb created
gpg: key 21794330: public key “Launchpad PPA for Lovell Fuller” imported
gpg: Total number processed: 1
gpg: imported: 1 (RSA: 1)
OK
then did - sudo apt-get update Here I get the following error in output:
Hit:1 http://deb.odroid.in/c2 xenial InRelease
Ign:2 http://ppa.launchpad.net/lovell/trusty-backport-vips/ubuntu xenial InRelease
Ign:3 http://ppa.launchpad.net/lovell/trusty-backport-vips/ubuntu xenial Release
Ign:4 http://ppa.launchpad.net/lovell/trusty-backport-vips/ubuntu xenial/main arm64 Packages
Ign:5 http://ppa.launchpad.net/lovell/trusty-backport-vips/ubuntu xenial/main armhf Packages
Ign:6 http://ppa.launchpad.net/lovell/trusty-backport-vips/ubuntu xenial/main all Packages
Hit:7 https://deb.nodesource.com/node_7.x xenial InRelease
Ign:8 http://ppa.launchpad.net/lovell/trusty-backport-vips/ubuntu xenial/main Translation-en_US
Ign:9 http://ppa.launchpad.net/lovell/trusty-backport-vips/ubuntu xenial/main Translation-en
Ign:10 http://ppa.launchpad.net/lovell/trusty-backport-vips/ubuntu xenial/main Translation-ru
Ign:4 http://ppa.launchpad.net/lovell/trusty-backport-vips/ubuntu xenial/main arm64 Packages
Ign:5 http://ppa.launchpad.net/lovell/trusty-backport-vips/ubuntu xenial/main armhf Packages
Ign:6 http://ppa.launchpad.net/lovell/trusty-backport-vips/ubuntu xenial/main all Packages
Ign:8 http://ppa.launchpad.net/lovell/trusty-backport-vips/ubuntu xenial/main Translation-en_US
Ign:9 http://ppa.launchpad.net/lovell/trusty-backport-vips/ubuntu xenial/main Translation-en
Ign:10 http://ppa.launchpad.net/lovell/trusty-backport-vips/ubuntu xenial/main Translation-ru
Ign:4 http://ppa.launchpad.net/lovell/trusty-backport-vips/ubuntu xenial/main arm64 Packages
Ign:5 http://ppa.launchpad.net/lovell/trusty-backport-vips/ubuntu xenial/main armhf Packages
Ign:6 http://ppa.launchpad.net/lovell/trusty-backport-vips/ubuntu xenial/main all Packages
Ign:8 http://ppa.launchpad.net/lovell/trusty-backport-vips/ubuntu xenial/main Translation-en_US
Ign:9 http://ppa.launchpad.net/lovell/trusty-backport-vips/ubuntu xenial/main Translation-en
Ign:10 http://ppa.launchpad.net/lovell/trusty-backport-vips/ubuntu xenial/main Translation-ru
Ign:4 http://ppa.launchpad.net/lovell/trusty-backport-vips/ubuntu xenial/main arm64 Packages
Ign:5 http://ppa.launchpad.net/lovell/trusty-backport-vips/ubuntu xenial/main armhf Packages
Ign:6 http://ppa.launchpad.net/lovell/trusty-backport-vips/ubuntu xenial/main all Packages
Ign:8 http://ppa.launchpad.net/lovell/trusty-backport-vips/ubuntu xenial/main Translation-en_US
Ign:9 http://ppa.launchpad.net/lovell/trusty-backport-vips/ubuntu xenial/main Translation-en
Ign:10 http://ppa.launchpad.net/lovell/trusty-backport-vips/ubuntu xenial/main Translation-ru
Ign:4 http://ppa.launchpad.net/lovell/trusty-backport-vips/ubuntu xenial/main arm64 Packages
Ign:5 http://ppa.launchpad.net/lovell/trusty-backport-vips/ubuntu xenial/main armhf Packages
Ign:6 http://ppa.launchpad.net/lovell/trusty-backport-vips/ubuntu xenial/main all Packages
Ign:8 http://ppa.launchpad.net/lovell/trusty-backport-vips/ubuntu xenial/main Translation-en_US
Ign:9 http://ppa.launchpad.net/lovell/trusty-backport-vips/ubuntu xenial/main Translation-en
Ign:10 http://ppa.launchpad.net/lovell/trusty-backport-vips/ubuntu xenial/main Translation-ru
Err:4 http://ppa.launchpad.net/lovell/trusty-backport-vips/ubuntu xenial/main arm64 Packages
404 Not Found
Err:5 http://ppa.launchpad.net/lovell/trusty-backport-vips/ubuntu xenial/main armhf Packages
404 Not Found
Ign:6 http://ppa.launchpad.net/lovell/trusty-backport-vips/ubuntu xenial/main all Packages
Ign:8 http://ppa.launchpad.net/lovell/trusty-backport-vips/ubuntu xenial/main Translation-en_US
Ign:9 http://ppa.launchpad.net/lovell/trusty-backport-vips/ubuntu xenial/main Translation-en
Ign:10 http://ppa.launchpad.net/lovell/trusty-backport-vips/ubuntu xenial/main Translation-ru
Hit:11 http://ports.ubuntu.com/ubuntu-ports xenial InRelease
Hit:12 http://ports.ubuntu.com/ubuntu-ports xenial-updates InRelease
Hit:13 http://ports.ubuntu.com/ubuntu-ports xenial-backports InRelease
Hit:14 http://ports.ubuntu.com/ubuntu-ports xenial-security InRelease
Hit:15 http://oph.mdrjr.net/odrobian xenial InRelease
Hit:16 http://ports.ubuntu.com/ubuntu-ports xenial-proposed InRelease
Reading package lists… Done
W: The repository ‘http://ppa.launchpad.net/lovell/trusty-backport-vips/ubuntu xenial Release’ does not have a Release file.
N: Data from such a repository can’t be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: http://oph.mdrjr.net/odrobian/dists/xenial/InRelease: Signature by key F3230DD84F39A606727D3D5D1B881FD777439C3B uses weak digest algorithm (SHA1)
E: Failed to fetch http://ppa.launchpad.net/lovell/trusty-backport-vips/ubuntu/dists/xenial/main/binary-arm64/Packages 404 Not Found
E: Failed to fetch http://ppa.launchpad.net/lovell/trusty-backport-vips/ubuntu/dists/xenial/main/binary-armhf/Packages 404 Not Found
E: Some index files failed to download. They have been ignored, or old ones used instead.
My sources contains: /etc/apt/sources.list
deb http://ports.ubuntu.com/ubuntu-ports/ xenial main universe restricted multiverse deb-src http://ports.ubuntu.com/ubuntu-ports/ xenial main universe restricted multiverse deb http://ports.ubuntu.com/ubuntu-ports/ xenial-updates main universe restricted multiverse deb-src http://ports.ubuntu.com/ubuntu-ports/ xenial-updates main universe restricted multiverse deb http://ports.ubuntu.com/ubuntu-ports/ xenial-backports main restricted universe multiverse deb-src http://ports.ubuntu.com/ubuntu-ports/ xenial-backports main restricted universe multiverse
deb http://ports.ubuntu.com/ubuntu-ports/ xenial-security main restricted universe multiverse deb-src http://ports.ubuntu.com/ubuntu-ports/ xenial-security main restricted universe multiverse
deb http://ports.ubuntu.com/ubuntu-ports/ xenial-proposed main restricted universe multiverse deb-src http://ports.ubuntu.com/ubuntu-ports/ xenial-proposed main restricted universe multiverse
uname -a Linux odroid64 3.14.29 #25 SMP PREEMPT Fri Apr 22 16:24:15 EDT 2016 aarch64 aarch64 aarch64 GNU/Linux
I’ve spent hours searching and trying different things but none have worked. Please advice how to fix this. Thanks in advance!
Issue Analytics
- State:
- Created 6 years ago
- Comments:24 (10 by maintainers)

Top Related StackOverflow Question
Great, thanks for confirming. 64-bit ARM (ARMv8) support will be fixed properly in the v0.18.0 release. (I’m also expanding the ARM packaging tests to help prevent further regression.)
@Sing-Li Pre-compiled binaries for libvips and its dependencies are provided for ARMv7-A.
https://github.com/lovell/sharp-libvips/blob/master/linux-armv7/Dockerfile#L21
Is
npm installbeing run on the same device as used at runtime?The
sharp.nodebinary will still need to be compiled, either on the device it will be used at runtime or cross-compiled to match.If the problem persists, please open a new issue with the result of running
npm install sharpon the device used at runtime.