Hi,<br><br>I have a question about the implementation of %load-foreign-library on SBCL. It seems that the call to load-shared-object remembers the absolute pathname to the library that is loaded unless :dont-save t is used. This causes portability issues for my application, which can&#39;t load from the same path when used on different systems. Is there any reason to choose this behavior?<br>
<br>Of course, with :dont-save t, the user then has to call use-foreign-library again when starting up from the saved image, but I find this preferable to the crash I receive otherwise.<br><br>An example patch is included below.<br>
<br>Thanks.<br><br>--- src/cffi-sbcl.lisp~ 2009-04-14 19:33:40.000000000 -0700<br>
+++ src/cffi-sbcl.lisp  2009-04-03 15:28:37.000000000 -0700<br>
@@ -324,7 +324,7 @@<br>
 (defun %load-foreign-library (name path)<br>
  &quot;Load a foreign library.&quot;<br>
  (declare (ignore name))<br>
-  (load-shared-object path))<br>
+  (load-shared-object path :dont-save t))<br>
<br>
 ;;; SBCL 1.0.21.15 renamed SB-ALIEN::SHARED-OBJECT-FILE but introduced<br>
 ;;; SB-ALIEN:UNLOAD-SHARED-OBJECT which we can use instead.<br clear="all"><br>-- <br>Elliott Slaughter<br><br>&quot;Don&#39;t worry about what anybody else is going to do. The best way to predict the future is to invent it.&quot; - Alan Kay<br>