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: Wed, 20 Jul 2011 15:44:04 +0200
On 19/07/11 11:59, Antonio Trande wrote:
2011/7/18 Eugen Dedu<Eugen Dedu pu-pm univ-fcomte fr>
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
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
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.
Making a recap :
$ locate libpt.so
If i don't use *PKG_CONFIG_PATH=/usr/lib/pkgconfig* , ptlib check failed.
So the problem in your case is that ptlib.pc is installed in
/usr/lib/pkgconfig (the classical directory), however on your system it
should be installed in /usr/lib64/pkgconfig. This is a new trend,
called multiarch I think. We are looking into detail how to solve this
issue, stay tuned...
] [Thread Prev