[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [libextractor] EXTRACTOR_getDefaultLibraries failing
From: |
Christian Grothoff |
Subject: |
Re: [libextractor] EXTRACTOR_getDefaultLibraries failing |
Date: |
Thu, 22 May 2008 07:23:07 -0600 |
User-agent: |
KMail/1.9.9 |
AFAIK the only reason why it could fail is that it cannot find the plugins.
LE uses various strategies to try to locate the plugin files (details asre a
bit OS dependent, but on Linux LE tries to find the path to libextractor.so
from /proc/self/ and then assumes that the plugins are located relative to
that path -- for details, look at the C code).
Anyway, if the plugins cannot be found (lt_dlopen fails), then NULL is likely
to be returned. This can usually be fixed by correcting the installation
(not LE's code). Now, I've not had any reports about the Debian/Ubuntu
packages being broken, so this is a bit odd. Maybe something quite
installation-specific.
You might want to start by contacting the Ubuntu maintainer to see if it is
something package-specific.
Good luck!
Christian
On Wednesday 21 May 2008 09:49:28 am Vazquez, Jose SPAWAR wrote:
> Hi Christian and Vids,
>
> I'm trying to install FOSSology 0.7.0 in a virtual machine running Ubuntu
> Hardy server edition that had libextractor-dev and libextractor-plugins
> version 0.5.18a-2 installed. At run time one of the applications makes a
> call to EXTRACTOR_getDefaultLibraries and the call is failing every time.
> Why will that call ever fail? By looking at the libextractor code, I can
> see that there are some default libraries defined.
>
> I was able to install and run FOSSology 0.7.0 in another virtual machine
> running Ubuntu Hardy desktop edition with the same libraries as the other
> virtual machine. The only difference between the machines is the edition
> of the OS.
>
> Any help will be appreciated.
>
> Regards.
>
> Jose Vazquez