LinuxQuestions.org
Latest LQ Deal: Linux Power User Bundle
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - General
User Name
Password
Linux - General This Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.

Notices


Reply
  Search this Thread
Old 11-16-2005, 01:05 AM   #1
M$ISBS
Member
 
Registered: Aug 2003
Posts: 834

Rep: Reputation: 30
What does this error mean and how can I fix it?


Tying to run configure on gphoto2 and I get this error:
-----------------------------------------------------------------------------------------------
No package 'libgphoto2' found
configure: error: Package requirements (libgphoto2 >= 2.1.2) were not met.
Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively you may set the GP_CFLAGS and GP_LIBS environment variables
to avoid the need to call pkg-config. See the pkg-config man page for
more details.
------------------------------------------------------------------------------------------------
I just installed libgphoto2 but I installed 2.1.6, a newer version. When I configured libgphot2 I did ./configure --prefix=/usr/local.
I dont know how to adjust the PKG_CONFIG_PATH environment variable, Is that difficult?
Thanks.
 
Old 11-16-2005, 01:27 AM   #2
Jade King
LQ Newbie
 
Registered: Nov 2005
Posts: 3

Rep: Reputation: 0
Re: What does this error mean and how can I fix it?

Quote:
Originally posted by M$ISBS
Tying to run configure on gphoto2 and I get this error:
-----------------------------------------------------------------------------------------------
No package 'libgphoto2' found
configure: error: Package requirements (libgphoto2 >= 2.1.2) were not met.
Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively you may set the GP_CFLAGS and GP_LIBS environment variables
to avoid the need to call pkg-config. See the pkg-config man page for
more details.
------------------------------------------------------------------------------------------------
I just installed libgphoto2 but I installed 2.1.6, a newer version. When I configured libgphot2 I did ./configure --prefix=/usr/local.
I dont know how to adjust the PKG_CONFIG_PATH environment variable, Is that difficult?
Thanks.

try #rpm -aq | grep libgphoto

if you can't find it,you must install it ,if it exsit
do #export PKG_CONFIG_PATH=$PKG_CONFIG_PATH :/yourlibgphotopath/libgphotofile
then you ./configure --prefix=/usr/local. will be ok

good luck.
 
Old 11-16-2005, 04:02 PM   #3
runlevel0
Member
 
Registered: Mar 2005
Location: Hilversum/Holland
Distribution: Debian GNU/Linux 5.0 (“Lenny”)
Posts: 290

Rep: Reputation: 31
Re: What does this error mean and how can I fix it?

Quote:
Originally posted by M$ISBS
Tying to run configure on gphoto2 and I get this error:
No package 'libgphoto2' found
I just installed libgphoto2 but I installed 2.1.6, a newer version. When I configured libgphot2 I did ./configure --prefix=/usr/local.
I dont know how to adjust the PKG_CONFIG_PATH environment variable, Is that difficult?
Thanks.
I don't think you need to configure this env variable.

There are nevertheless, two things you will need to do:

First of all is letting your system know that you have libraries installed in the /usr/local hierarchy.
To do this, get root, summon your favorite editor (vim, of course) and edit the file /etc/ld.so.conf
Add the line:
Code:
/usr/local/lib
save and close and run (also as root)

Code:
ldconfig
This should be enough.

After this change recompile gphoto2, it should be able to find the needed libs regardless of whether you set the path or which install prefix you use.
 
Old 11-16-2005, 08:33 PM   #4
M$ISBS
Member
 
Registered: Aug 2003
Posts: 834

Original Poster
Rep: Reputation: 30
Ive already got that in my ld.so.conf and I ran updatedb and ldconfig before trying to install anything. What else could I do?
 
Old 11-16-2005, 08:54 PM   #5
perfect_circle
Senior Member
 
Registered: Oct 2004
Location: Athens, Greece
Distribution: Slackware, arch
Posts: 1,783

Rep: Reputation: 52
can you post "./configure --help" for libgphoto. Maybe libgphoto by defaults creates static libraries only (*.a) and you need shared libraries (*.so). This should be a ./configure option.
 
Old 11-16-2005, 09:05 PM   #6
M$ISBS
Member
 
Registered: Aug 2003
Posts: 834

Original Poster
Rep: Reputation: 30
Here it is, but I thought ./configure was the same for all programs?

./configure --help
`configure' configures this package to adapt to many kinds of systems.

Usage: ./configure [OPTION]... [VAR=VALUE]...

To assign environment variables (e.g., CC, CFLAGS...), specify them as
VAR=VALUE. See below for descriptions of some of the useful variables.

Defaults for the options are specified in brackets.

Configuration:
-h, --help display this help and exit
--help=short display options specific to this package
--help=recursive display the short help of all the included packages
-V, --version display version information and exit
-q, --quiet, --silent do not print `checking...' messages
--cache-file=FILE cache test results in FILE [disabled]
-C, --config-cache alias for `--cache-file=config.cache'
-n, --no-create do not create output files
--srcdir=DIR find the sources in DIR [configure dir or `..']

Installation directories:
--prefix=PREFIX install architecture-independent files in PREFIX
[/usr/local]
--exec-prefix=EPREFIX install architecture-dependent files in EPREFIX
[PREFIX]

By default, `make install' will install all the files in
`/usr/local/bin', `/usr/local/lib' etc. You can specify
an installation prefix other than `/usr/local' using `--prefix',
for instance `--prefix=$HOME'.

For better control, use the options below.

Fine tuning of the installation directories:
--bindir=DIR user executables [EPREFIX/bin]
--sbindir=DIR system admin executables [EPREFIX/sbin]
--libexecdir=DIR program executables [EPREFIX/libexec]
--datadir=DIR read-only architecture-independent data [PREFIX/share]
--sysconfdir=DIR read-only single-machine data [PREFIX/etc]
--sharedstatedir=DIR modifiable architecture-independent data [PREFIX/com]
--localstatedir=DIR modifiable single-machine data [PREFIX/var]
--libdir=DIR object code libraries [EPREFIX/lib]
--includedir=DIR C header files [PREFIX/include]
--oldincludedir=DIR C header files for non-gcc [/usr/include]
--infodir=DIR info documentation [PREFIX/info]
--mandir=DIR man documentation [PREFIX/man]

Program names:
--program-prefix=PREFIX prepend PREFIX to installed program names
--program-suffix=SUFFIX append SUFFIX to installed program names
--program-transform-name=PROGRAM run sed PROGRAM on installed program names

System types:
--build=BUILD configure for building on BUILD [guessed]
--host=HOST cross-compile to build programs to run on HOST [BUILD]

Optional Features:
--disable-FEATURE do not include FEATURE (same as --enable-FEATURE=no)
--enable-FEATURE[=ARG] include FEATURE [ARG=yes]
--enable-maintainer-mode enable make rules and dependencies not useful
(and sometimes confusing) to the casual installer
--disable-nls do not use Native Language Support
--disable-rpath do not hardcode runtime library paths

Optional Packages:
--with-PACKAGE[=ARG] use PACKAGE [ARG=yes]
--without-PACKAGE do not use PACKAGE (same as --with-PACKAGE=no)
--with-gnu-ld assume the C compiler uses GNU ld default=no
--with-libiconv-prefix[=DIR] search for libiconv in DIR/include and DIR/lib
--without-libiconv-prefix don't search for libiconv in includedir and libdir
--with-included-gettext use the GNU gettext library included here
--with-libintl-prefix[=DIR] search for libintl in DIR/include and DIR/lib
--without-libintl-prefix don't search for libintl in includedir and libdir
--without-pthread Don't use pthread
--without-cdk Don't use cdk
--with-cdk-prefix=PREFIX Location of cdk
--without-jpeg Don't use jpeg
--with-jpeg-prefix=PREFIX Location of jpeg
--without-pkgconfig Don't use pkg-config
--without-exif Don't use libexif
--with-exif-prefix=PREFIX Location of libexif
--without-aalib Don't use aalib
--without-popt Don't use popt.h
--without-readline Don't use readline

Some influential environment variables:
CC C compiler command
CFLAGS C compiler flags
LDFLAGS linker flags, e.g. -L<lib dir> if you have libraries in a
nonstandard directory <lib dir>
CPPFLAGS C/C++ preprocessor flags, e.g. -I<include dir> if you have
headers in a nonstandard directory <include dir>
CPP C preprocessor
PKG_CONFIG path to pkg-config utility
GP_CFLAGS C compiler flags for GP, overriding pkg-config
GP_LIBS linker flags for GP, overriding pkg-config

Use these variables to override the choices made by `configure' or to help
it to find libraries and programs with nonstandard names/locations.

/home/downloads/digitalcamera/gphoto2-2.1.6# cd ..
/home/downloads/digitalcamera# ls
digikam-0.8.0-rc gphoto2-2.1.6 libgphoto2-2.1.6
digikam-0.8.0-rc.tar gphoto2-2.1.6.tar.gz libgphoto2-2.1.6.tar.gz
/home/downloads/digitalcamera# cd libgphoto2-2.1.6
/home/downloads/digitalcamera/libgphoto2-2.1.6# ls
ABOUT-NLS MAINTAINERS TESTERS config.rpath gphoto2-config.in makefile.os2 stamp-h.in
AUTHORS Makefile aclocal.m4 config.status install-sh missing tests
CHANGES Makefile.am camlibs config.sub intl mkinstalldirs
COPYING Makefile.in config.guess configure libgphoto2 os2mak.inc
ChangeLog NEWS config.h configure.in libgphoto2_port packaging
HACKING README config.h.in doc libtool po
INSTALL README.in config.log gphoto2-config ltmain.sh stamp-h
/home/downloads/digitalcamera/libgphoto2-2.1.6# ./configure --help
`configure' configures this package to adapt to many kinds of systems.

Usage: ./configure [OPTION]... [VAR=VALUE]...

To assign environment variables (e.g., CC, CFLAGS...), specify them as
VAR=VALUE. See below for descriptions of some of the useful variables.

Defaults for the options are specified in brackets.

Configuration:
-h, --help display this help and exit
--help=short display options specific to this package
--help=recursive display the short help of all the included packages
-V, --version display version information and exit
-q, --quiet, --silent do not print `checking...' messages
--cache-file=FILE cache test results in FILE [disabled]
-C, --config-cache alias for `--cache-file=config.cache'
-n, --no-create do not create output files
--srcdir=DIR find the sources in DIR [configure dir or `..']

Installation directories:
--prefix=PREFIX install architecture-independent files in PREFIX
[/usr/local]
--exec-prefix=EPREFIX install architecture-dependent files in EPREFIX
[PREFIX]

By default, `make install' will install all the files in
`/usr/local/bin', `/usr/local/lib' etc. You can specify
an installation prefix other than `/usr/local' using `--prefix',
for instance `--prefix=$HOME'.

For better control, use the options below.

Fine tuning of the installation directories:
--bindir=DIR user executables [EPREFIX/bin]
--sbindir=DIR system admin executables [EPREFIX/sbin]
--libexecdir=DIR program executables [EPREFIX/libexec]
--datadir=DIR read-only architecture-independent data [PREFIX/share]
--sysconfdir=DIR read-only single-machine data [PREFIX/etc]
--sharedstatedir=DIR modifiable architecture-independent data [PREFIX/com]
--localstatedir=DIR modifiable single-machine data [PREFIX/var]
--libdir=DIR object code libraries [EPREFIX/lib]
--includedir=DIR C header files [PREFIX/include]
--oldincludedir=DIR C header files for non-gcc [/usr/include]
--infodir=DIR info documentation [PREFIX/info]
--mandir=DIR man documentation [PREFIX/man]

Program names:
--program-prefix=PREFIX prepend PREFIX to installed program names
--program-suffix=SUFFIX append SUFFIX to installed program names
--program-transform-name=PROGRAM run sed PROGRAM on installed program names

System types:
--build=BUILD configure for building on BUILD [guessed]
--host=HOST cross-compile to build programs to run on HOST [BUILD]

Optional Features:
--disable-FEATURE do not include FEATURE (same as --enable-FEATURE=no)
--enable-FEATURE[=ARG] include FEATURE [ARG=yes]
--enable-maintainer-mode enable make rules and dependencies not useful
(and sometimes confusing) to the casual installer
--disable-nls do not use Native Language Support
--disable-rpath do not hardcode runtime library paths
--enable-shared[=PKGS]
build shared libraries [default=yes]
--enable-static[=PKGS]
build static libraries [default=yes]
--enable-fast-install[=PKGS]
optimize for fast installation [default=yes]
--disable-libtool-lock avoid locking (might break parallel builds)
--enable-docs Use gtk-doc to build documentation default=no

Optional Packages:
--with-PACKAGE[=ARG] use PACKAGE [ARG=yes]
--without-PACKAGE do not use PACKAGE (same as --with-PACKAGE=no)
--with-gnu-ld assume the C compiler uses GNU ld default=no
--with-libiconv-prefix[=DIR] search for libiconv in DIR/include and DIR/lib
--without-libiconv-prefix don't search for libiconv in includedir and libdir
--with-included-gettext use the GNU gettext library included here
--with-libintl-prefix[=DIR] search for libintl in DIR/include and DIR/lib
--without-libintl-prefix don't search for libintl in includedir and libdir
--with-gnu-ld assume the C compiler uses GNU ld [default=no]
--with-pic try to use only PIC/non-PIC objects [default=use
both]
--with-tags[=TAGS]
include additional configurations [automatic]
--with-ltdl Use ltdl
--with-camlibdir=<path> install camlibs in directory <path>
--with-drivers=<list> compile drivers in <list>;
drivers may be separated with commas;
'all' compiles all drivers;
possible drivers are:
adcs65, agfa-cl20, aox, barbie, canon, casio,
digita, dimera, directory, enigma13, fuji, gsmart300,
iclick, jamcam, jd11, kodak, konica, largan,
mars, minolta, mustek, panasonic, pccam300,
pccam600, polaroid, ptp2, ricoh, samsung, sierra,
smal, sipix, sonydscf1, sonydscf55, soundvision,
spca50x, sq905, stv0674, stv0680, sx330z, toshiba
--with-doc-dir=PATH Where to install docs default=autodetect
--with-html-dir=PATH Where to install html docs default=autodetect
--with-rpmbuild=PATH Program to use for building RPMs
--with-hotplug-doc-dir=PATH Where to install hotplug scripts as docs default=autodetect
--with-hotplug-usermap-dir=PATH Where to install hotplug scripts as docs default=autodetect
--without-pkgconfig Don't use pkg-config
--without-exif Don't use libexif
--with-exif-prefix=PREFIX Location of libexif

Some influential environment variables:
CC C compiler command
CFLAGS C compiler flags
LDFLAGS linker flags, e.g. -L<lib dir> if you have libraries in a
nonstandard directory <lib dir>
CPPFLAGS C/C++ preprocessor flags, e.g. -I<include dir> if you have
headers in a nonstandard directory <include dir>
CPP C preprocessor
CXX C++ compiler command
CXXFLAGS C++ compiler flags
CXXCPP C++ preprocessor
F77 Fortran 77 compiler command
FFLAGS Fortran 77 compiler flags

Use these variables to override the choices made by `configure' or to help
it to find libraries and programs with nonstandard names/locations.
 
Old 11-16-2005, 09:36 PM   #7
perfect_circle
Senior Member
 
Registered: Oct 2004
Location: Athens, Greece
Distribution: Slackware, arch
Posts: 1,783

Rep: Reputation: 52
I was looking for this:
Code:
 build shared libraries [default=yes]
--enable-static[=PKGS]
build static libraries [default=yes]
SO this is not the case.

Some programs do not enable the "build shared libraries by default.
 
Old 11-16-2005, 09:43 PM   #8
perfect_circle
Senior Member
 
Registered: Oct 2004
Location: Athens, Greece
Distribution: Slackware, arch
Posts: 1,783

Rep: Reputation: 52
USE those slackbuilds/slack-desc to build and pack them (since you already got the source:
for libgphoto2:
http://www.slacky.it/download/traver...%2F2.1.6%2Fsrc
As far as I see they use they use --disable-static
download doinst.sh, libgphoto2.slackbuild and slack-desc in a directory were you have the libgphoto2 source.
Give execute permision to libgphoto2.SlackBuild:
Code:
chmod +x libgphoto2.SlackBuild
and run it:
Code:
./libgphoto2.SlackBuild
Watch for error. If everything goes well, this should create a usable package in /tmp. You can install it with installpkg

for gphoto2:
http://www.slacky.it/download/traver...%2F2.1.6%2Fsrc
DO the same as above

Last edited by perfect_circle; 11-16-2005 at 09:50 PM.
 
Old 11-16-2005, 09:54 PM   #9
perfect_circle
Senior Member
 
Registered: Oct 2004
Location: Athens, Greece
Distribution: Slackware, arch
Posts: 1,783

Rep: Reputation: 52
If don't care to compile them by yourself, you may download the prebuild packages and install them with installpkg that are in the parent directory of those two links.
 
Old 11-17-2005, 07:17 AM   #10
runlevel0
Member
 
Registered: Mar 2005
Location: Hilversum/Holland
Distribution: Debian GNU/Linux 5.0 (“Lenny”)
Posts: 290

Rep: Reputation: 31
PKG_CONFIG_PATH does not mean the actual package or the lib path (this is set using LDCONFIG or LD_LIBRARY_PATH).

What is asked for is for an application called pkgconfig.
The path is/usr/lib/pkgconfig.

Ensure that you have it installed (I can't stat to which package it belongs or whether it's a single package on your distro).

If you can't find neither pkg-config or pkgconfig you will need to install it. If it's there just locate the package and export the variable pointing to the correct path.
 
Old 11-17-2005, 09:11 PM   #11
M$ISBS
Member
 
Registered: Aug 2003
Posts: 834

Original Poster
Rep: Reputation: 30
Quote:
Originally posted by runlevel0
PKG_CONFIG_PATH does not mean the actual package or the lib path (this is set using LDCONFIG or LD_LIBRARY_PATH).

What is asked for is for an application called pkgconfig.
The path is/usr/lib/pkgconfig.

Ensure that you have it installed (I can't stat to which package it belongs or whether it's a single package on your distro).

If you can't find neither pkg-config or pkgconfig you will need to install it. If it's there just locate the package and export the variable pointing to the correct path.
/usr/lib/pkgconfig is actually a directory. How do I export a variable pointing to a path?
 
Old 11-18-2005, 07:50 AM   #12
runlevel0
Member
 
Registered: Mar 2005
Location: Hilversum/Holland
Distribution: Debian GNU/Linux 5.0 (“Lenny”)
Posts: 290

Rep: Reputation: 31
Same as for anything else:
Code:
export PKG_CONFIG_PATH=/usr/lib/pkgconfig
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
What is a Signal 11 error and how do I fix this? bigredmed Linux - Newbie 8 03-20-2015 03:58 AM
can anyone fix this error ?? vstealerv Linux - Newbie 2 04-30-2005 09:03 PM
Is there a fix for this error slackrush Slackware 2 07-10-2004 09:53 AM
how do i fix this error AMArt79196 Red Hat 1 07-05-2004 04:44 PM
Whats this error and how do i fix it? Quivver Linux - Newbie 1 02-14-2004 11:56 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - General

All times are GMT -5. The time now is 10:21 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration