Opened 12 years ago

Closed 12 years ago

Last modified 12 years ago

#37214 closed defect (fixed)

Maxima not playing well with SBCL 1.1.2

Reported by: kirc0076@… Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 2.1.2
Keywords: Cc: easye, gwright@…, KubaO (Kuba Ober), rwc@…, tkbrekken@…
Port: maxima sbcl

Description

I upgraded my outdated packages, and SBCL was one of them. Tried to load maxima, didn't work. Tried to uninstall both maxima and sbcl, then reinstall maxima. Still unable to run maxima.

$ rmaxima
fatal error encountered in SBCL pid 93700:
can't load .core for different runtime, sorry


Welcome to LDB, a low-level debugger for the Lisp runtime environment.
ldb> 

Log attached.

Attachments (1)

maxima.log (2.7 KB) - added by kirc0076@… 12 years ago.

Download all attachments as: .zip

Change History (13)

comment:1 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)

Cc: easieste@… gwright@… kuba@… added

comment:2 Changed 12 years ago by jmroot (Joshua Root)

IIRC it's necessary to increment maxima's revision every time sbcl's version is updated.

Changed 12 years ago by kirc0076@…

Attachment: maxima.log added

comment:3 Changed 12 years ago by easye

Hmm. I'll look into fixing Maxima. It should certainly be possible to patch Maxima to dynamically compile and load its fasls if there is newer version of sbcl present. Such a patch should be trivial if Maxima is using ASDF.

Last edited 12 years ago by easye (previous) (diff)

comment:4 Changed 12 years ago by rwc@…

Cc: rwc@… added

Cc Me!

comment:5 Changed 12 years ago by tkbrekken@…

Cc: tkbrekken@… added

Cc Me!

comment:6 in reply to:  3 ; Changed 12 years ago by mcq@…

Replying to easieste@…:

Hmm. I'll look into fixing Maxima. It should certainly be possible to patch Maxima to dynamically compile and load its fasls if there is newer version of sbcl present. Such a patch should be trivial if Maxima is using ASDF.

There might be a miscommunication here. This ticket is reporting a new problem.

The problem of having to manually uninstall and reinstall maxima after sbcl update is an old problem. I believe it's reported in multiple tickets already.

The new problem is that doing that (uninstalling and reinstalling maxima) no longer works. I was not using maxima for a few months, so I just encountered it today, with

sbcl @1.1.2_0 (active)

and

maxima @5.28.0_1+xmaxima (active)

Unfortunately, I already deleted all my old versions so I'm not sure of the last time the uninstalling / reinstalling trick worked.

Version 0, edited 12 years ago by mcq@… (next)

comment:7 Changed 12 years ago by mf2k (Frank Schima)

Port: maxima, sbclmaxima sbcl

comment:8 in reply to:  6 ; Changed 12 years ago by anddam (Andrea D'Amore)

Replying to mcq@…:

The new problem is that doing that (uninstalling and reinstalling maxima) no longer works. I was not using maxima for a few months, so I just encountered it today, with

sbcl @1.1.2_0 (active)

I just stumbled into this, my guess is you're installing maxima binary package that is being built with a different version of sbcl on the build server.

Try upgrading sbcl, uninstalling maxima and then reinstalling maxima using -s option in order to build it from source.

comment:9 in reply to:  8 Changed 12 years ago by kirc0076@…

Replying to and.damore@…:

Try upgrading sbcl, uninstalling maxima and then reinstalling maxima using -s option in order to build it from source.

This fixed the problem. Thanks.

Is there a way to modify the portfile to force building from source?

Last edited 12 years ago by kirc0076@… (previous) (diff)

comment:10 Changed 12 years ago by mf2k (Frank Schima)

Confirmed. sbcl was updated since maxima. So now maxima needs to be rebuilt on the buildbot - I'm trying to figure out how to do that without modifying the portfile.

comment:11 Changed 12 years ago by mf2k (Frank Schima)

Resolution: fixed
Status: newclosed

I realized that maxima was broken for everyone currently and increased the revision in r101312.

comment:12 Changed 12 years ago by jmroot (Joshua Root)

There was no miscommunication; I said in comment:2 that the revision needed to be bumped, and easieste replied that he would rather find a way to make that unnecessary. Since that solution doesn't seem to have appeared yet, bumping the revision was of course the correct short-term fix.

Note: See TracTickets for help on using tickets.