On Fri, Jul 01, 2005 at 12:44:36PM -0700, Ned Konz wrote:
On Thursday 30 June 2005 6:43 pm, David T. Lewis wrote:
It appears that there is something about the vm-display-X11 file itself that causes it to be unloadable (it's world readable and world executable, so that's not it). The file itself looks fine:
$ ls -l /usr/local/lib/squeak/3.8a-2/vm-display-X11 -rwxr-xr-x 1 lewis users 150331 2005-06-30 11:26 /usr/local/lib/squeak/3.8a-2/vm-display-X11 $ file /usr/local/lib/squeak/3.8a-2/vm-display-X11 /usr/local/lib/squeak/3.8a-2/vm-display-X11: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), not stripped
And the module built without errors and warnings, so I'm thinking it may be something that has changed recently in the source tree.
I feel like Mr. Jones, something is going on but I don't know what to do. Any tips?
Try running it under strace to see what's happening. Also, you can turn on debug messages that should indicate the loader's progress.
strace -o sq.out -etrace=file,process /usr/bin/squeak -vm-sound=null
Thanks Ned, that was just the tip I needed.
The strace shows the /usr/local/lib/squeak/3.8a-2/vm-display-X11 file being opened, followed shortly thereafter by this:
open("/usr/local/lib/libXext.so.6", O_RDONLY) = -1 ENOENT (No such file or directory)
I remember this coming up before as a configuration glitch on some versions of Linux. I'll get it straightened out on my system and report back if there is anything interesting to add.
Dave