[bt-devel] Sword/Bibletime CVS problems

[spu]

On Fri, 2002-08-09 at 06:35, Joachim Ansorg wrote:
> Hi!
> 
> >    First of all I got a fresh copy of Sword from CVS, followed the
> > directions, and to all appearances, it installed successfully :)
> 
> Whihc commands did you use to get Sword's CVS?
    
Here are the commands that I used to get Sword:
    export
    CVSROOT=:pserver:anonymous@cvs.crosswire.org:/usr/local/cvsroot &&
    cvs login && cvs -z5 checkout sword
   As you can probably tell by the "&&", I run these commands as a shell
script.
   And also, here is the link that was sent to me in message from
someone on this mailing list.  This is the page that has the commands
that I have been using to get
Sword:http://sword.sourceforge.net/cgi-bin/twiki/view/Bibletime/CvsInfo

> Since utf8transliterator.h is missing, it seems an older version than current 
> CVS is installed.
> Are you sure no old header files are on the disk?
> What does "find / -name swmgr.h" tell you?

Here is the output of "find / -name swmgr.h":
    /home/steve/sword/include/swmgr.h
    /home/steve/sword/sword/include/swmgr.h
    /home/steve/ARCHIVES/computer/builds/sword-1.5.3/include/swmgr.h
    /home/steve/ARCHIVES/computer/builds/sword-1.5.3/sword-1.5.3/include/swmgr.h
    /home/steve/ARCHIVES/bible/BIBLETIME/BUILDS/sword-1.5.3/include/swmgr.h
    /home/steve/ARCHIVES/bible/BIBLETIME/BUILDS/sword-1.5.3/sword-1.5.3/include/swmgr.h
    find: /proc/2092/fd: No such file or directory
    /root/sword/include/swmgr.h
    /usr/include/sword/swmgr.h
   If the question about old header files is not answered in the output
shown above, please clarify where I would find these header files.  This
is the appropriate place to add that when I was still able to get
Bibletime from the CVS, I started over completely a few times, deleting
the "bibletime" directory that CVS had placed in my home directory. 

> >    The only unusual thing I did while configuring Bibletime, is that I
> > ran configure this way "./configure --prefix=/usr", so the presence of
> > "/root" in the output is inexplicable to me.
> 
> /root means you unpacked the sources in the /root/ directory and started make 
> there :)
> e.g. "Entering directory `/root/bibletime/bibletime/backend'"
   First of all, I successfully installed Sword 1.5.4 from the CVS that
I grabbed in my attempt to build and install the Bibletime CVS.  I know
that it installed successfully, because I am now running the current
stable version of Bibletime, version 1.2.1, which I compiled and
installed from source code.  My reason for getting into all of this is
because I unpacked and made the source code for Bibletime 1.2.1 in the
same directory, /root, that I attempted to make the CVS of Bibletime
in.   The difference is, with Bibletime 1.2.1, when I ran make install,
it worked.

> 
> ./configure --prefix=/usr is necessary on RedHat systems. It should make no 
> difference concerning Sword.
   On the subject of the preceding statement, I tried it a few ways,
--prefix=/usr, --prefix=/opt (when I was trying to set up a separate CVS
install of Sword/Bibletime.  I did successfully install Sword 1.5.3 and
Bibletime 1.2.1 in /opt, and the ran perefectly, using ./configure
--prefix=/opt) and I also tried it just using the default path.

In conclusion, read the words that Fred Sallbach sent to me:
    I am in a similar position, but because I attempted to install kde
    3.0.3 on my system.  kde 3.0.2 worked fine (mandrake 7.1) but the
    last kde rpm must have been compiled on mandrake 7.2.  It broke all
    sorts of things and resulted in a fresh install.
    
    I just tried to build bibletime for the first time since 
    reinstalling the OS and found that my sword did not let me build
    bibletime, I am in the process of downloading the cvs.  so this
    weekend I will try to build a new set.
    
    Every once in a while something is added to the sword CVS that 
    bibletime cvs does not like, this is usually quickly resolved, so
    please have patience.  It is worth the wait. 
    
    Fred

   This implies that he had the same problem that I've had, and he
attributes it the the build that we both got from the CVS.
   Please refer to my message with the subject "Problems logging into
CVS" and see if you can help me with that matter, because right now,
using the same commands I've been using all along (which had worked for
a while), I couldn't get a current version of the CVS for Bibletime if I
wanted to.

Thanks for your help :)
Steven P. Ulrick