[bt-devel] 1.2.2 execute troubles

mark lybarger bt-devel@crosswire.org
Wed, 16 Oct 2002 13:05:14 +0000


Lamar Owen wrote:
> On Wednesday 16 October 2002 07:44 am, mark lybarger wrote:
> 
>>Lamar Owen wrote:
>>
>>>Umm, if this is for a distribution's package, you might reconsider
>>>putting the SWORD modules in /usr/share/sword.  The modules are typically
>>
> 
>>the sword libs are actually installed in /usr/sword/1, but the text
>>stuff is in /var/db/sword.  i'm not to particular where it's installed,
>>but i was told that in gentoo, you can't touch /usr/local.  i'll check
>>with the ebuild maintainer to see his reasons for putting this into
>>/var/db and if there's a chance of moving it.
> 
> 
> Not /usr/local -- /usr/share. No distribution can touch /usr/local -- 
> according to the LSB at least (I get grief over this for the PostgreSQL RPMs 
> quite frequently, as they don't use /usr/local/pgsql like the standard source 
> distribution wants).  But /usr/share/sword is where the RPMs for bibletime 
> put things, and it works fine.

i submitted the question to the ebuild maintainer to see his reasons for 
putting it /var/db/sword as oppose to /usr/share/sword.

> 
> 
>>regardless, i thought bibletime would pick up the setting in
>>/etc/sword.conf and use that...
> 
> 
> Interesting.  As I said, the RPMs use /usr/share/sword, and set that value in 
> /etc/sword.conf as such:
> [lowen@localhost lowen]$ cat /etc/sword.conf
> [Install]
> DataPath=/usr/share/sword
> [lowen@localhost lowen]$
> 
> The RPMs build the sword libs statically at the moment -- is the gentoo ebuild 
> requiring a preinstalled sword library?  Is that library configured 
> differently?


my problems are happening both with the sword installed by the ebuild 
and with sword from cvs, so i don't think it's an issue related to the 
build procedure. my cvs install uses whatever the defaults for for 
static/dynamic lib building.  i seem to get a core before sword is 
really used.  as i mentioned, when i comment out the recursive function 
in bibletime.cpp, all works well. i can browse the modules just fine.