Re: [Ekiga-list] Compiling opal-3.10.1
- From: Eugen Dedu <Eugen Dedu pu-pm univ-fcomte fr>
- To: Ekiga mailing list <ekiga-list gnome org>
- Subject: Re: [Ekiga-list] Compiling opal-3.10.1
- Date: Mon, 18 Jul 2011 19:11:31 +0200
On 17/07/11 18:30, Antonio Trande wrote:
Solved with $ PKG_CONFIG_PATH=/usr/lib/pkgconfig ./configure .
There is a problem with your machine. By default, pkg-config looks at
/usr/lib/pkgconfig, there is no need to tell it so.
From man pkg-config:
pkg-config retrieves information about packages from special
metadata files. These files are
named after the package, and has a .pc extension. On most
systems, pkg-config looks in
/usr/lib/pkgconfig, /usr/share/pkgconfig,
/usr/local/lib/pkgconfig and /usr/local/share/pkg‐
config for these files. It will additionally look in the
colon-separated (on Windows, semi‐
colon-separated) list of directories specified by the
PKG_CONFIG_PATH environment variable.
Since with PKG_CONFIG_PATH=/usr/lib/pkgconfig ./configure it works, it
means that on your system pkg-config does not look in
/usr/lib/pkgconfig, so it was somewhat wrongly installed.
2011/7/17 Antonio Trande<anto trande gmail com>
Same output:
$ PKG_CONFIG_PATH=/usr/local/lib/pkgconfig ./configure
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for g++... g++
checking whether the C++ compiler works... yes
checking for C++ compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking for gcc... gcc
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for a BSD-compatible install... /usr/bin/install -c
checking for ranlib... ranlib
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for ar... ar
configure: gcc version is 4.6.0
checking if gcc version is valid... yes
checking for working bit scan intrinsic... no
configure: Opal version is 3.10.1
checking where plugins are being installed... /usr/local/lib/opal-3.10.1
checking for PTLIB... no
configure: error: Package requirements (ptlib>= 2.10.1) were not met:
No package 'ptlib' found
Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.
Alternatively, you may set the environment variables PTLIB_CFLAGS
and PTLIB_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
Try this :
$ PKG_CONFIG_PATH=/usr/local/lib/pkgconfig ./configure
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]