[bt-devel] problem building sword...

[Mark Lybarger]

Sorry to be a bother, but I am still having lots of troubles building 
the sword cvs.  I was able to build and install this morning as per the 
suggestion from Daniel.  After that, I was getting errors building the 
Bibletime CVS, but the errors were pointing to sword header files.  So, 
I noticed the make file issue was resolved for Sword, and decided to get 
a clean copy.  I wiped my sword directory, and again obtained from CVS. 
    I checked the Makefile.cfg, buildshare := yes, and icu := no.  The 
below is the error messages I see when I try to run "make".

Please let me know if there is a separate sword mailing list I should 
send this type of issue to.

Also, Is there a static snapshot of the sword cvs that we know will work 
for building the current CVS bibletime?

---------------------------------------------------------------------------
make[1]: Leaving directory `/home/mark/bibletime/sword/lib'
make -C tests just-targets
make[1]: Entering directory `/home/mark/bibletime/sword/tests'
gcc -I../include/ -D_GNU_SOURCE -D_GNU_SOURCE -pipe -Wall -Wno-format 
-pedantic -pedantic  -fomit-frame-pointer -ggdb -O0 -DUSBINARY -m486 -o 
keytest keytest.cpp   -L../lib/  -lsword -lstdc++ -lz
../lib//libsword.a(rawld.o): In function `RawLD::RawLD(char const *, 
char const *, char const *, SWDisplay *, char, char, char)':
/home/mark/bibletime/sword/src/modules/lexdict/rawld/rawld.cpp:33: 
undefined reference to `SWLD::SWLD(char const *, char const *, SWDisplay 
*, char, char, char)'
../lib//libsword.a(rawld.o): In function `RawLD::~RawLD(void)':
/home/mark/bibletime/sword/src/modules/lexdict/rawld/rawld.cpp:43: 
undefined reference to `SWLD::~SWLD(void)'
../lib//libsword.a(rawld.o):/home/mark/bibletime/sword/src/modules/lexdict/rawld/../../../../include/rawld.h:57: 
undefined reference to `SWLD type_info node'
../lib//libsword.a(rawld.o):/home/mark/bibletime/sword/src/modules/lexdict/rawld/../../../../include/rawld.h:48: 
undefined reference to `SWLD::KeyText(char const *)'
../lib//libsword.a(rawld.o):/home/mark/bibletime/sword/src/modules/lexdict/rawld/rawld.cpp:33: 
undefined reference to `SWLD::CreateKey(void)'
../lib//libsword.a(rawld.o): In function `RawLD type_info function':
/home/mark/bibletime/sword/src/modules/lexdict/rawld/../../../../include/rawld.h:57: 
undefined reference to `SWLD type_info function'
../lib//libsword.a(rawld4.o): In function `RawLD4::RawLD4(char const *, 
char const *, char const *, SWDisplay *, char, char, char)':
/home/mark/bibletime/sword/src/modules/lexdict/rawld4/rawld4.cpp:33: 
undefined reference to `SWLD::SWLD(char const *, char const *, SWDisplay 
*, char, char, char)'
../lib//libsword.a(rawld4.o): In function `RawLD4::~RawLD4(void)':
/home/mark/bibletime/sword/src/modules/lexdict/rawld4/rawld4.cpp:43: 
undefined reference to `SWLD::~SWLD(void)'
../lib//libsword.a(rawld4.o):/home/mark/bibletime/sword/src/modules/lexdict/rawld4/../../../../include/rawld4.h:52: 
undefined reference to `SWLD type_info node'
../lib//libsword.a(rawld4.o):/home/mark/bibletime/sword/src/modules/lexdict/rawld4/../../../../include/rawld4.h:47: 
undefined reference to `SWLD::KeyText(char const *)'
../lib//libsword.a(rawld4.o):/home/mark/bibletime/sword/src/modules/lexdict/rawld4/rawld4.cpp:33: 
undefined reference to `SWLD::CreateKey(void)'
../lib//libsword.a(rawld4.o): In function `RawLD4 type_info function':
/home/mark/bibletime/sword/src/modules/lexdict/rawld4/../../../../include/rawld4.h:52: 
undefined reference to `SWLD type_info function'
collect2: ld returned 1 exit status
make[1]: *** [keytest] Error 1


Chris Little wrote:

> The utilities/Makefile is fixed now and should prevent the make system 
> from trying to compile normcode when icu is set to no.
> 
> Sorry about this.  If you got that far, though, the libarary was finished 
> building anyway.
> 
> --Chris
> 
> On Mon, 5 Nov 2001, Mark Lybarger wrote:
> 
> 
>>i checked my Makefile.cfg, and it has the following line which appears 
>>that it should exclude icu support.
>>
>># icu support
>>icu := no
>>
>>i still get the error i noted with this line as such.
>>
> 
> 
>