Opened 6 years ago

Closed 6 years ago

#1471 closed defect (fixed)

[with spkg, with positive review] moving a sage install breaks clisp

Reported by: mabshoff Owned by: mabshoff
Priority: critical Milestone: sage-2.9.2
Component: distribution Keywords:
Cc: Merged in:
Authors: Reviewers:
Report Upstream: Work issues:
Branch: Commit:
Dependencies: Stopgaps:

Description

Moving a Sage install breaks clisp. I moved sage-2.9.alpha5 to sage-2.9.alpha5-vg and it broke clisp:

mabshoff@sage:/tmp/Work-mabshoff/release-cycles-2.9/sage-2.9.alpha5-vg$ clisp
clisp: /tmp/Work-mabshoff/release-cycles-2.9/sage-2.9.alpha5/local/lib/clisp/base/lisp.run: No such file or directory

I have no clue how Maxima still manages to work, but there must be a fix somehow.

Cheers,

Michael

Change History (4)

comment:1 Changed 6 years ago by jsp

Since sage-2.9.1.alpha3 this issue seems to be gone, maybe earlier? My standard procedure now is to relocate my installed sage before I do a make check.

clisp just worked

Jaap

comment:2 Changed 6 years ago by mabshoff

  • Summary changed from moving a sage install breaks clisp to [with spkg, needs review] moving a sage install breaks clisp

I still see the problem with Sage 2.9.1.1. I assume you might have some other sage install in the right location, so you don't see the problem. I needed to adapt maxima to use clisp.bin instead of clisp (the default) to build. The following two spkgs fix the problem:

Cheers,

Michael

comment:3 Changed 6 years ago by mhansen

  • Summary changed from [with spkg, needs review] moving a sage install breaks clisp to [with spkg, with positive review] moving a sage install breaks clisp

Michael, your spkgs fixed the problem for me.

comment:4 Changed 6 years ago by mabshoff

  • Resolution set to fixed
  • Status changed from new to closed

Merged in 2.9.2.alpha0

Note: See TracTickets for help on using tickets.