Squeak 1.3 Solaris link problem

Mike Klein mike at twinsun.com
Fri Jan 23 22:26:44 UTC 1998


It looks as if the solaris VM used to always hard-code the path to
	libXext.so.0
but the 1.3 VM's (both ordinary and JIT) now have to use the search
path somewhere. Notice that the first invocation of ldd (on 12% below)
shows two entries for the library, one which resolves to 
	/usr/openwin/lib/libXext.so.0
and the other is not found.

Doing
	setenv LD_LIBRARY_PATH /usr/openwin/lib
seems to work-around the problem.
____________________________________________

11% SqueakVM-1.30-sparc-solaris-2.5.1
ld.so.1: SqueakVM-1.30-sparc-solaris-2.5.1: fatal: libXext.so.0: can't open 
file: errno=2
Killed
12% ldd SqueakVM-1.30-sparc-solaris-2.5.1
        libX11.so.4 =>   /usr/lib/libX11.so.4
        libXext.so.0 =>  (not found)
        libm.so.1 =>     /usr/lib/libm.so.1
        libsocket.so.1 =>        /usr/lib/libsocket.so.1
        libnsl.so.1 =>   /usr/lib/libnsl.so.1
        libc.so.1 =>     /usr/lib/libc.so.1
        libXext.so.0 =>  /usr/openwin/lib/libXext.so.0
        libdl.so.1 =>    /usr/lib/libdl.so.1
        libw.so.1 =>     /usr/lib/libw.so.1
        libintl.so.1 =>  /usr/lib/libintl.so.1
        libmp.so.1 =>    /usr/lib/libmp.so.1
13% setenv LD_LIBRARY_PATH /usr/openwin/lib
14% ldd SqueakVM-1.30-sparc-solaris-2.5.1
        libX11.so.4 =>   /usr/openwin/lib/libX11.so.4
        libXext.so.0 =>  /usr/openwin/lib/libXext.so.0
        libm.so.1 =>     /usr/lib/libm.so.1
        libsocket.so.1 =>        /usr/lib/libsocket.so.1
        libnsl.so.1 =>   /usr/lib/libnsl.so.1
        libc.so.1 =>     /usr/lib/libc.so.1
        libdl.so.1 =>    /usr/lib/libdl.so.1
        libw.so.1 =>     /usr/lib/libw.so.1
        libintl.so.1 =>  /usr/lib/libintl.so.1
        libmp.so.1 =>    /usr/lib/libmp.so.1
15% SqueakVM-1.30-sparc-solaris-2.5.1
Could not open the Squeak image file 'squeak.image'.

There are two ways to open a Squeak image file.  You can:
  1. Put the name of the image file on the command line
     when you run Squeak (use '-help' for more information).
  2. Save an image (from inside Squeak) with the name 'clone'
     and run Squeak from the directory containing it.
16% 





More information about the Squeak-dev mailing list