Allright, I understand. And good to hear it's almost solved :) Greetings, - Willem
On Mon, 28 Oct 2002 14:27:49 -0700 "Troy A. Griffitts" <[EMAIL PROTECTED]> wrote: > Willem, > Officially 1.5.x is a development thread, but in practice, all > the > frontends have moved from 1.4.x to 1.5.x. This is my fault. We > should have a new stable thread started soon that will remain binary > compatible with .x releases. > > -Troy. > > > > > > Willem van Engen wrote: > > Hmm, too bad. Thanks for answering though :) > > > > But ... is it very hard to keep binary compatibility (between major > > versions - now and then api changes are really needed) ? If more > > applications start using sword, it will get more annoying and > > finally maybe unacceptable when upgrades break many programs (e.g. > > webbrowser). Plugins might work around this, but still. > > > > - Willem > > > > On Mon, 28 Oct 2002 20:45:43 +0100 > > Joachim Ansorg <[EMAIL PROTECTED]> wrote: > > > > > >>Yes, sadly you have recomple Gnomesword after you upgraded your > >Sword>version because binary compatibity is not guaranteed for > >between Sword>versions. > >> > >>Joachim > >> > >> > >>>Hello, > >>> > >>>I upgraded sword from 1.5.3 to 1.5.5. Then I tried to run > >>>gnomesword, dynamically with the 1.5.3 library. It fails with this > >>>error: > >>> > >>> /usr/libexec/ld-elf.so.1: Undefined symbol > >>> "_9LocaleMgr$systemLocaleMgr" referenced from COPY relocation in > >>> gnomesword > >>> > >>>(on a freebsd box). I remember unresolved symbols appearing at past > >>>upgrades. Does it mean that I really have to recompile all > >>>applications linked with sword, when it's upgraded? Or is there a > >>>solution to this? > >>> > >>>Greetings, > >>>- Willem > >>> > >>>btw. thanks for making sword compile with gcc3.2! I don't use gcc3 > >>>yet, but it's needed for freebsd-current which uses gcc3.2 by > >>>default. > >> > >>-- > >>Joachim Ansorg > >>www.bibletime.de > >>www.ansorgs.de > > > >
