question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Package vips was not found in the pkg-config search path.

See original GitHub issue

Can you tell me what I’m doing wrong?

node --version

v0.10.25

sudo apt-get install build-essential pkg-config glib2.0-dev libxml2-dev

sudo apt-get install libvips

Reading package lists... Done
Building dependency tree       
Reading state information... Done
Note, selecting 'libvips37' instead of 'libvips'
Recommended packages:
  nip2
The following NEW packages will be installed:
  libvips37
0 upgraded, 1 newly installed, 0 to remove and 41 not upgraded.

npm install sharp

// ....

> node-gyp rebuild

Package vips was not found in the pkg-config search path.
Perhaps you should add the directory containing `vips.pc'
to the PKG_CONFIG_PATH environment variable
No package 'vips' found
gyp: Call to 'PKG_CONFIG_PATH=":$PKG_CONFIG_PATH:/usr/local/lib/pkgconfig:/usr/lib/pkgconfig" pkg-config --libs vips' returned exit status 1. 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/share/node-gyp/lib/configure.js:431: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.13.0-24-generic
gyp ERR! command "nodejs" "/usr/bin/node-gyp" "rebuild"
gyp ERR! cwd /home/mt/nodejs/imgtest/sharp
gyp ERR! node -v v0.10.25
gyp ERR! node-gyp -v v0.10.10
gyp ERR! not ok 
npm WARN This failure might be due to the use of legacy binary "node"
npm WARN For further explanations, please read
/usr/share/doc/nodejs/README.Debian

npm ERR! weird error 1
npm ERR! not ok code 0

Issue Analytics

  • State:closed
  • Created 8 years ago
  • Comments:9 (4 by maintainers)

github_iconTop GitHub Comments

3reactions
lovellcommented, Jun 2, 2015

Hello, the libvips-dev package includes the vips.pc file required by pkgconfig.

The mention of libvips37 suggests the use of Ubuntu 14.04, which provides v7.38.x via apt. The minimum libvips version required is v7.40.0 (vips -v will provide the installed version) so the preinstall.sh script may help.

0reactions
canebatcommented, Jun 2, 2015

Oops, no I didn’t! Thanks.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Package was not found in the pkg-config search path
1 Answer 1 · configure and compile libmaus2 this way : ./configure --prefix=/SOFT/libmaus2 && make -j8 install · export PKG_CONFIG_PATH=/SOFT/ ...
Read more >
Ubuntu 16.04 LTS Installation libvips appears "Package VIPs ...
First run vips -v to see if libvips installed successfully, if the installation is not a problem, it may be the PKG_CONFIG_PATH environment ......
Read more >
PKG_CONFIG_PATH environment variable - Ask Ubuntu
This variable is used to augment pkg-config's default search path. On a typical Unix system ... Package openssl was not found in the...
Read more >
vips - Go Packages
Go Vips is a go bind to libvips C API. Install. Check if pkg-config is able to find the right libvips include: pkg-config...
Read more >
vips and pkg-config: problem compiling examples [Archive]
The error that I get is: Package vips/vips-7.14 was not found in the pkg-config search path. ... I checked the PKG_CONFIG_PATH variable and...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found