[sword-devel] unresolved symbol after upgrade
Willem van Engen
Mon, 28 Oct 2002 21:51:15 +0100
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.
On Mon, 28 Oct 2002 20:45:43 +0100
Joachim Ansorg <firstname.lastname@example.org> wrote:
> Yes, sadly you have recomple Gnomesword after you upgraded your Sword
> version because binary compatibity is not guaranteed for between Sword
> > 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