I am verifying tht libgig is not only installed but set LD_LIBRARY_PATH,
ran ldconfig and even moved the libs to /usr/lib and /usr/lib64..
uname -a = Linux tcrgi.tri-century.com 2.6.12-12mdksmp #1 SMP Fri Sep 9
17:20:34 CEST 2005 x86_64 AMD Athlon(tm) 64 Processor 3000+ unknown GNU/Linux
(Mandrake 2006 w/Jack, etc... 4 GB RAM)
Any ideas? faking out def_arch_x86 (setting to 1) didn't help..
Weird how the libgig build generates libgig.so.2.2.0 instead of 2.0.2
(linking to ...2.0.2 to fake it didn't help either0
Please send your config.log.
The given libgig.so version is absolutely ok. The .so version has nothing to
do with the release version of the library. Even though they seem to be
similar at the moment.
Unfortunately I don't have x86_64 box to test if this might be a x86_64
Created attachment 14 [details]
Config log as requested.
config.log as requested.
Thanks for looking at it.
PS Any code tweaks you request I can do rapidly and test...
Check where the gig.pc file was installed. That's actually the file which
pkg-config checks for the version of the libgig library:
find / -name gig.pc
Usually it should be in /usr/lib/pkgconfig/, but I guess in your case it's
somewhere under /usr/local/. Then add that directory to the pkg-config search
Also make sure you don't have two different version of libgig installed. It
often happens that people have an old version of libgig in /usr/lib installed
(from their distribution) and a younger version under /usr/local which they
compiled and installed manually.
did the trick...