From b71f242e1332582e10e5f7df3cd056f20f96f93e Mon Sep 17 00:00:00 2001
From: rtoy <rtoy>
Date: Tue, 15 Feb 2005 18:15:10 +0000
Subject: [PATCH] In dump-symbol, don't do anything special when the symbol is
 in the same package as *package*, because when the fasl is loaded in a
 different package, the symbols are in the wrong package.

---
 compiler/dump.lisp | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/compiler/dump.lisp b/compiler/dump.lisp
index e57253eaa..ad189020b 100644
--- a/compiler/dump.lisp
+++ b/compiler/dump.lisp
@@ -5,7 +5,7 @@
 ;;; Carnegie Mellon University, and has been placed in the public domain.
 ;;;
 (ext:file-comment
-  "$Header: /Volumes/share2/src/cmucl/cvs2git/cvsroot/src/compiler/dump.lisp,v 1.80 2003/06/30 14:59:03 gerd Exp $")
+  "$Header: /Volumes/share2/src/cmucl/cvs2git/cvsroot/src/compiler/dump.lisp,v 1.81 2005/02/15 18:15:10 rtoy Exp $")
 ;;;
 ;;; **********************************************************************
 ;;;
@@ -1195,6 +1195,11 @@
     (cond ((null pkg)
 	   (dump-fop* pname-length lisp::fop-uninterned-small-symbol-save
 		      lisp::fop-uninterned-symbol-save file))
+	  ;; Why do we do this?  It causes weird things to happen if
+	  ;; you're in, say, the KERNEL package when you compile-file
+	  ;; something and load the fasl back in when you're in a
+	  ;; different package.
+	  #-(and)
 	  ((eq pkg *package*)
 	   (dump-fop* pname-length lisp::fop-small-symbol-save
 		      lisp::fop-symbol-save file))
-- 
GitLab