windows cannnot install 1.4.2

Bug #1735974 reported by Lein Matsumaru
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
SBCL
Invalid
Undecided
Unassigned

Bug Description

Background:
  I have sbcl installed version 1.3.15 from sbcl-1.3.15-x86-64-windows-binary.msi
  In the directory D:/SteelBankCommonLisp/1.3.15/

I wanted to install the lastest version(1.4.2) the same way as I did in 1.3.15,
the installer puts bunch of files in the directory D:/SteelBankCommonLisp/1.4.2/
but it removes the directory of 1.3.15, and when I run sbcl.exe, it says

fatal error encountered in SBCL pid 12472(tid 031B2FE8):
can't find core file at D:\SteelBankCommonLisp\1.3.15/sbcl.core

so I copied the direcotory of sbcl-1.3.15 installed in another directory,
so that sbcl.exe (of version 1.4.2) can find D:\SteelBankCommonLisp\1.3.15/sbcl.core
and run again sbcl.exe (of version 1.4.2) it says,

This is SBCL 1.4.2, an implementation of ANSI Common Lisp.
More information about SBCL is available at <http://www.sbcl.org/>.

SBCL is free software, provided as is, with absolutely no warranty.
It is mostly in the public domain; some portions are provided under
BSD-style licenses. See the CREDITS and COPYING files in the
distribution for more information.

WARNING: the Windows port is fragile, particularly for multithreaded
code. Unfortunately, the development team currently lacks the time
and resources this platform demands.
fatal error encountered in SBCL pid 2824(tid 001E2FE8):
unknown core file entry: 0x0

OS: Windows 10 (64-bit)

thank you.

Revision history for this message
Lein Matsumaru (apple-princess) wrote :

Self resolved.
The reason is that the environment variable SBCL_HOME is set to the directory of sbcl-1.3.15. and this is why I could not run.

So this bug report is marked as Invalid.

Thank you.

Changed in sbcl:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.