Hi all, i have problem to start 0.8.11 SER on OpenBSD 3.4, after install port run ser report errors:
./ser:/usr/local/lib/ser/modules/sl.so: undefined symbol 'mem_lock' ./ser: /usr/local/lib/ser/modules/sl.so: can't resolve reference 'mem_lock' ./ser:/usr/local/lib/ser/modules/sl.so: undefined symbol 'process_no' ./ser: /usr/local/lib/ser/modules/sl.so: can't resolve reference 'process_no' ./ser:/usr/local/lib/ser/modules/sl.so: undefined symbol 'mem_block' ./ser: /usr/local/lib/ser/modules/sl.so: can't resolve reference 'mem_block' ./ser:/usr/local/lib/ser/modules/sl.so: undefined symbol 'dont_fork' ./ser: /usr/local/lib/ser/modules/sl.so: can't resolve reference 'dont_fork' ./ser:/usr/local/lib/ser/modules/sl.so: undefined symbol 'tcp_disable' ./ser: /usr/local/lib/ser/modules/sl.so: can't resolve reference 'tcp_disable' ./ser:/usr/local/lib/ser/modules/sl.so: undefined symbol 'sock_no' ./ser: /usr/local/lib/ser/modules/sl.so: can't resolve reference 'sock_no' ./ser:/usr/local/lib/ser/modules/sl.so: undefined symbol 'debug' ./ser: /usr/local/lib/ser/modules/sl.so: can't resolve reference 'debug' ./ser:/usr/local/lib/ser/modules/sl.so: undefined symbol 'fifo' ./ser: /usr/local/lib/ser/modules/sl.so: can't resolve reference 'fifo' ./ser:/usr/local/lib/ser/modules/sl.so: undefined symbol 'prev_ser_error' ./ser: /usr/local/lib/ser/modules/sl.so: can't resolve reference 'prev_ser_error' ./ser:/usr/local/lib/ser/modules/sl.so: undefined symbol 'children_no' ./ser: /usr/local/lib/ser/modules/sl.so: can't resolve reference 'children_no' ./ser:/usr/local/lib/ser/modules/sl.so: undefined symbol 'sock_info' ./ser: /usr/local/lib/ser/modules/sl.so: can't resolve reference 'sock_info' ./ser:/usr/local/lib/ser/modules/sl.so: undefined symbol 'reply_to_via' ./ser: /usr/local/lib/ser/modules/sl.so: can't resolve reference 'reply_to_via' ./ser:/usr/local/lib/ser/modules/sl.so: undefined symbol 'log_stderr' ./ser: /usr/local/lib/ser/modules/sl.so: can't resolve reference 'log_stderr' ./ser:/usr/local/lib/ser/modules/sl.so: undefined symbol 'shm_block' ./ser: /usr/local/lib/ser/modules/sl.so: can't resolve reference 'shm_block' ./ser:/usr/local/lib/ser/modules/sl.so: undefined symbol 'tcp_children_no' ./ser: /usr/local/lib/ser/modules/sl.so: can't resolve reference 'tcp_children_no' ./ser:/usr/local/lib/ser/modules/sl.so: undefined symbol 'timer_list' ./ser: /usr/local/lib/ser/modules/sl.so: can't resolve reference 'timer_list'
how i can fix this problem ?
On Nov 21, 2003 at 14:05, Evgeniy evgeniy@riscom.net wrote:
Hi all, i have problem to start 0.8.11 SER on OpenBSD 3.4, after install port run ser report errors:
./ser:/usr/local/lib/ser/modules/sl.so: undefined symbol 'mem_lock'
Are you sure you are not trying to run and older ser version with newer modules? Is this a clean install? Did you make install from the ser port dir?
It works for me on openbsd 3.2.
Andrei
On Friday 21 November 2003 15:37, Andrei Pelinescu-Onciul wrote:
On Nov 21, 2003 at 14:05, Evgeniy evgeniy@riscom.net wrote:
Hi all, i have problem to start 0.8.11 SER on OpenBSD 3.4, after install port run ser report errors:
./ser:/usr/local/lib/ser/modules/sl.so: undefined symbol 'mem_lock'
Are you sure you are not trying to run and older ser version with newer modules?
yes, i sure, i donwloads versions 0.8.10, 0.8.11, latest
Is this a clean install?
what do you mean ?
Did you make install from the ser port dir?
yes of course, i can sent final package, if you need ?
It works for me on openbsd 3.2.
OpenBSD 3.4 have changed binary format from aout to elf maybe problem is here ? i can send full install log or create ssh access to my system.
Andrei
On Nov 21, 2003 at 15:58, Evgeniy evgeniy@riscom.net wrote: [...]
It works for me on openbsd 3.2.
OpenBSD 3.4 have changed binary format from aout to elf maybe problem is here ? i can send full install log or create ssh access to my system.
Hmm, it seems that it changed the symbols which are exported. Maybe different link flags? (the symbols from ser are used by the modules, so they must be exported; adding -E to the gcc link command for ser takes care of this for all arhitectures, until now...).
Could you send me (along with the full install log), the output of:
nm ser nm -D ser # this does not work on openbsd 3.2 because is a.out, # nm doesn't even have the -D switch, but if the format is # now elf, it should work objdump -T ser # same as above, in case nm does not have the -D switch
same thing on one of the modules:
nm modules/textops/textops.so nm -D modules/textops/textops.so # or objdump -T ...
If I can't figure this out from the logs, I will ask you for the ssh access.
Thanks, Andrei
On Friday 21 November 2003 16:55, you wrote:
On Nov 21, 2003 at 15:58, Evgeniy evgeniy@riscom.net wrote: [...]
It works for me on openbsd 3.2.
OpenBSD 3.4 have changed binary format from aout to elf maybe problem is here ? i can send full install log or create ssh access to my system.
Hmm, it seems that it changed the symbols which are exported. Maybe different link flags? (the symbols from ser are used by the modules, so they must be exported; adding -E to the gcc link command for ser takes care of this for all arhitectures, until now...).
Could you send me (along with the full install log), the output of:
nm ser nm -D ser # this does not work on openbsd 3.2 because is a.out, # nm doesn't even have the -D switch, but if the format is # now elf, it should work objdump -T ser # same as above, in case nm does not have the -D switch
same thing on one of the modules:
nm modules/textops/textops.so nm -D modules/textops/textops.so # or objdump -T ...
i did this is the result log
If I can't figure this out from the logs, I will ask you for the ssh access.
Thanks, Andrei
On Nov 24, 2003 at 10:54, Evgeniy evgeniy@riscom.net wrote:
On Friday 21 November 2003 16:55, you wrote:
On Nov 21, 2003 at 15:58, Evgeniy evgeniy@riscom.net wrote: [...]
It works for me on openbsd 3.2.
OpenBSD 3.4 have changed binary format from aout to elf maybe problem is here ? i can send full install log or create ssh access to my system.
Hmm, it seems that it changed the symbols which are exported. Maybe different link flags? (the symbols from ser are used by the modules, so they must be exported; adding -E to the gcc link command for ser takes care of this for all arhitectures, until now...).
Hmmm, I think I should read my own comments from time to time : LDFLAGS= # openbsd ld doesn't like -O2 or -E :-)
So because I clear LDFLAGS on openbsd, ser won't be compiled with -Wl,-E on 3.4 and the symbols won't be exported.
i did this is the result log
Thanks.
Try the attached patch (patch -p0 < ~/sip_router/makefile_defs_openbsd.3.4.patch from your ser sources dir).
I try to detect openbsd release number and set LDFLAGS based on it. If this works for you I will commit it on the cvs. If not please send me the last make line (something like: gcc -Wl,-O2 -Wl,-E action.o crc.o data_lump.o ...)
Andrei
On Monday 24 November 2003 16:27, you wrote:
On Nov 24, 2003 at 10:54, Evgeniy evgeniy@riscom.net wrote:
On Friday 21 November 2003 16:55, you wrote:
On Nov 21, 2003 at 15:58, Evgeniy evgeniy@riscom.net wrote: [...]
It works for me on openbsd 3.2.
OpenBSD 3.4 have changed binary format from aout to elf maybe problem is here ? i can send full install log or create ssh access to my system.
Hmm, it seems that it changed the symbols which are exported. Maybe different link flags? (the symbols from ser are used by the modules, so they must be exported; adding -E to the gcc link command for ser takes care of this for all arhitectures, until now...).
Hmmm, I think I should read my own comments from time to time : LDFLAGS= # openbsd ld doesn't like -O2 or -E
:-)
So because I clear LDFLAGS on openbsd, ser won't be compiled with -Wl,-E on 3.4 and the symbols won't be exported.
i did this is the result log
Thanks.
Try the attached patch (patch -p0 < ~/sip_router/makefile_defs_openbsd.3.4.patch from your ser sources dir).
I try to detect openbsd release number and set LDFLAGS based on it. If this works for you I will commit it on the cvs. If not please send me the last make line (something like: gcc -Wl,-O2 -Wl,-E action.o crc.o data_lump.o ...)
cool, but one error exists
0(13333) loading module /usr/local/lib/ser/modules/sl.so 0(13333) ERROR: no version info in module </usr/local/lib/ser/modules/sl.so>: Unable to resolve symbol
this is full gmake & gmake install log
thnaks.
Andrei
-
Andrei Pelinescu-Onciul -
Evgeniy