>Number:         13216
>Category:       pkg
>Synopsis:       STk fails to load dynamically linked objects
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    pkg-manager
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Jun 15 01:25:01 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     Jarle Greipsland
>Release:        NetBSD 1.5.1_BETA2 (2001-06-06)
>Organization:
UNINETT
>Environment:
	
System: NetBSD festningen.uninett.no 1.5.1_BETA2 NetBSD 1.5.1_BETA2 (FESTNINGEN) #2: Thu Jun 7 18:01:40 CEST 2001 root@festningen.uninett.no:/usr/src/sys/arch/i386/compile/FESTNINGEN i386


>Description:
Some of the supplied STk library modules require extra functionality found
in a shared object file that will be dynamically loaded whenever the
scheme library is loaded.  However, the loading of these objects fail.

Example:

$ snow
Welcome to the STk interpreter version 3.99.2 [NetBSD-1.5.1_BETA2-i386]
Copyright © 1993-1998 Erick Gallesio - I3S - CNRS / ESSI <eg@unice.fr>
STk> (require "socket")
*** Error at line 25 of file /usr/pkg/lib/stk/3.99.2/STk/socket.stk:
    dynload: cannot open object file: "/usr/pkg/lib/stk/3.99.2/NetBSD-1.5.1_BETA2-i386/socket.so"
Current eval stack:
__________________
  0    (load (string-append "socket." *shared-suffix*))
  1    (load what (current-module))
  2    (begin (load what (current-module)) (unless (member what provided) (format #t "WARNING: ~S was not provided~%" what)))
  3    (require "socket")
STk> 

The strange part is that a ktrace of the STk interpreter show that it does
indeed both read and mmap the socket.so file.

	
>How-To-Repeat:

$ cd /usr/pkgsrc/lang/STk
$ make install
$ echo '(require "socket")' > /tmp/dltest.stk
$ snow -f /tmp/dltest.stk

	
>Fix:
	
Unknown to me.  Maybe upgrade to a newer version of the package?
>Release-Note:
>Audit-Trail:
>Unformatted: