Update of bug #17485 (project freeciv):
Status:None = Invalid
Assigned to:None = syntron
Open/Closed:Open = Closed
Update of bug #17485 (project freeciv):
Summary: can start freeciv using ./ser if build with shared
libraries = can't start freeciv using ./ser if build with shared libraries
___
Follow-up Comment #1:
One cannot debug
Follow-up Comment #2, bug #17485 (project freeciv):
Are you enabling only shared libraries, or are you also building ai as
modules? I just noticed that latter has a problem related to new directory
structure when running out of build directory.
Follow-up Comment #3, bug #17485 (project freeciv):
Attached patch makes it possible to run --enable-aimodules --enable-shared
--enable-debug builds out of builddir. Without --enable-debug and with ai
modules enabled one has to install freeciv.
Will commit immediately, but leaving this ticket
Follow-up Comment #5, bug #17485 (project freeciv):
The error message reads:
# ./ser -f xyz
./server/.libs/freeciv-server: error while loading shared libraries:
libfreeciv-srv.so.0: cannot open shared object file: No such file or
directory
the file libfreeciv-srv.so.0 exists in the directory
Follow-up Comment #6, bug #17485 (project freeciv):
I suspect there is something wrong with wrappers allowing execution in build
dir.
What versions of libtool, automake and autoconf are you using? I'm using
libtool 2.2.6b, automake 1.11.1 and autoconf 2.67.
Follow-up Comment #7, bug #17485 (project freeciv):
What versions of libtool, automake and autoconf are you using?
That's the root of the bug. Due to a bug somethere in the kernel level I
can't run freeciv on the computer there it is build. If freeciv does a core
dump (-F), the computer will
Follow-up Comment #8, bug #17485 (project freeciv):
Shared libs (freeciv and AI) are working on the computer where they were
compiled. If I do try to start it in the nfs mounted directory on another
computer it is not working. But this is _not_ a problem of the freeciv code
but of the different
