zrnsk01@MELVIN.ZDV.UNI-TUEBINGEN.DE ("K. Spanier") (04/22/91)
Dear ISODE-runners,
in the last few days I tried to generate and install the interim version 6.8
of the ISODE package. My system is a vanilla SUN 4/20 with SunOS 4.1.1 and
16 MB of mememory. Since this is my first contact with the package (and OSI!)
I decided to install the application layers over TCP/IP using shared libs.
Having seen the recent e-mail exchanges concerning the problems of installing
version 6.8 with shared libs on SunOS, I hacked sunos4.make accordingly
(meaning, I additionally deleted the last two lines with ld -r -x stuff and
mv stuff) and stored the hack as CONFIG.make. At the same time I configured
the system in a way so that everything is located under a common parent d
irectory, namely /ksp/isode_6.8.
Next, I run the Makefile and everything compiled just fine, at least according
to my sense. Installation also seemed to be OK.
But now there is my problem:
starting tsapd with /ksp/isode_6.8/etc/tsapd merely gives the message
ld.so: libisode.so.68: not found
rather than starting the daemon.
That is OK, since my system generated libisode.so.68.385 as the shared library
and certainly not libisode.so.68 :-( !!!!
../util/make-lib.sh -bsd42 libisode.a -ranlib
ranlib libisode.a
rm -rf tmp
-rw------- 2 zrnsk01 1427592 Apr 19 13:08 libisode.a
ISODE library built normally
ld -o ../libisode.so.68.385 -assert pure-text ACS_tables.o DASE_tables.o DSE_tables.o ... vprint.o x25addr.o
ld: sunlink.o: __sunlink_stub: multiply defined
-rw------- 2 zrnsk01 1064960 Apr 19 13:09 libisode.so.68.385
shared ISODE library built normally
A symbolic link, libisode.so.68 -> libisode.so.68.385, in ISODE-LIBDIR doesn't
change the situation!!!
So my question: what is wrong, where is that libisode.so.68 shared library???
I greatly would appreciate your help, ISODE-runners.
Greetings, Kurt
------------------------------------------------------------------------------
Dr. Kurt Spanier Tel: 49-7071-29-6970
Center for Data Processing
Networking Group Fax: 49-7071-29-5400
University of Tuebingen
Brunnenstrasse 27 E-Mail: spanier@mailserv.zdv.uni-tuebingen.de
D-7400 Tuebingen
FRGzrnsk01@MELVIN.ZDV.UNI-TUEBINGEN.DE ("K. Spanier") (04/22/91)
Hi ISODE-runners, you are great!!! It took about 2 hours to get two answers to my problem with starting the tsapd on a SUN 4/20. The trick is to make a symbolic link from /usr/lib/libisode.so.68.385 to libisode.so.68.385 in my own LIBDIR and run ldconfig (you remember, I have installed ISODE under a common parent dir /ksp/isode_6.8, :-)). Now tsapd is running, although not yet tested (that's for tommorow, otherwise I might be knocked down by my lovely wife, Urgh, oh no, please...) Thanks to c.robbins%xtel.co.uk@RELAY.CS.NET and Eric.Rosenquist@dre-sw1.sofkin.ca Greetings, Kurt
j.onions@xtel.co.uk (Julian Onions) (04/23/91)
> That is OK, since my system generated libisode.so.68.385 as the shared librar y > and certainly not libisode.so.68 :-( !!!! No - the dynamic linking rules will ensure that a library of the form libisode.so.68.* will be loaded for anything requiring libisode.68. > So my question: what is wrong, where is that libisode.so.68 shared library??? Your problem is that your shared libisode is not in the standard system path. I think what you need to do is to change the definition of LIBISODE in CONFIG.make to have the path of you library directory too. So you have something like LIBISODE = -L$(TOPDIR) -L$(LIBDIR) -lisode This will allow it to find the shared object in your private lib directory. Julian.