I just found out, that the plugin-mechanism needs some very advanced libtool
features. libtool is not able to figure it out but relies on some entries
for special system names in ltconfig. My SINIX-M 5.41 is a i386-sni-sysv4
system but sni is not known to ltconfig. So it decides to skip all the
shared library dlopen stuff:
*** Warning: inter-library dependencies are not known to be supported.
*** All declared inter-library dependencies are being dropped.
It then tries to link the plugin static with the main program. Both use
symbols like proto_init(), so it can't link.
I changed ltconfig with the patch:
Index: ltconfig
===================================================================
RCS file: /usr/local/cvsroot/ethereal/ltconfig,v
retrieving revision 1.1
diff -u -r1.1 ltconfig
--- ltconfig 1999/12/26 22:37:20 1.1
+++ ltconfig 2000/01/18 10:52:49
@@ -2069,7 +2069,7 @@
soname_spec='${libname}${release}.so$major'
shlibpath_var=LD_LIBRARY_PATH
case "$host_vendor" in
- ncr)
+ ncr | sni)
deplibs_check_method='pass_all'
;;
motorola)
and everything is just fine. Who is responsable for this file? Should I send
this patch to the ltconfig programmers? Does it make sense to check it in
our ethereal tree?
Uwe
