On Apr 25, 2:17 pm, Chris Seberino <cseber...@gmail.com> wrote:
Hi Chris,
> On Apr 25, 2:10 am, mabshoff <michael.absh...@mathematik.uni-
<SNIP>
> Hmm. That is weird. I just compiled 3.4.1 from source and got the
> same error on the newer version too.
Ok.
<SNIP>
> That seems to be the only delta between you guys and me so chances are
> that's the problem.
Not really, we switched from clisp 2.46 to 2.47 and if you look at
https://groups.google.com/group/sage-devel/t/753a8d2f3c052183
for some people who have had issues for a long, long time we could
never get to the bottom of all the sudden they completely disappear.
Clisp seems to be working or not working depending on compiler
release, target CPU, etc, so I am not surprised you are seeing
oddities no one can reproduce. We are in progress of switching to ecl
as the basis for Maxima which will hopefully serve as a more stable
basis than clisp. Given that we want 3.4.2 out early next week the ecl
switch will probably miss the boat on that one, but since it is
essential to switch for Sage 4.0 to get Solaris support working it
will be in 4.0.
> cs
Cheers,
Michael
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to
sage-support-unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/sage-support
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
