Am Mittwoch, 16. Januar 2008 schrieb Raymond Toy (RT/EUS):
> Hanno Behrens wrote:
> >> To fix this problem, try recompiling maxima. Incidentally, if you're
> >> running debian unstable, there was an sbcl upgrade a couple of days ago
> >> which would have done this - I only realised when my precompiled slime
> >> stopped working.
> >
> > I recompiled maxima and the problem didn't solve.
>
> If you recompiled maxima, try using maxima-local in the maxima
> directory. This will at least tell you if it's working.
>
> Did you run "make install" to install maxima into the usual place?
I did not run any make by hand, I let it do gentoo/portage/layman with the
installed scientific overlay, in which maxima 5.14.0 is part of and simply
emerged maxima. The last time I did it by checking out the cvs by hand and
compiling it by hand. But that way brings normally some troubles when the
rest of the system is updating (just as it happend this time).
I think I solved the problem, which was quite easy after all. Should have seen
it earlier. Before using the portage-version I was using the cvs-version of
maxima. Those worked in /usr/local/bin, which is earlier in the path.
The new versions compiled to /usr/bin and were not called. I removed the old
ones and now its working fine:
---snip---
> maxima --version
Maxima 5.14.0
---snap---
After all this I suggest, that "maxima --version" should work even without a
working core. That would have made me able to find this error earlier.
But anyway - I'm happy now and going to check all my code on the new version.
Hopefully I don't have questions of the kind "does not work" again. :D
And thanks for the help! Great!
Hanno