On Apr 26, 11:05 pm, Chris Seberino <cseber...@gmail.com> wrote:
> On Apr 26, 1:36 am, mabshoff <michael.absh...@mathematik.uni-
>
> dortmund.de> wrote:
> > I do not see how that rules out clisp 2.47 - or am I just not getting
> > what you are driving at :)
>
> I meant if I can recreate the problem from 3.4 source as well as 3.4.1
> source then doesn't that mean I can recreate the problem in both
> version of clisp? Hence clisp is innocent?
No, my guess is that either clisp release triggers the same problem.
Any recent clisp source release is incredibly easy to miscompile and
we are building it with -O0 with any compiler to maximize our chances
to make it work. But no clisp release since 2.41 has ever even build
on the build farm or SkyNet, much less various OSX releases or Solaris
(at least not with anything beyond gcc 4.x). That is the reason we are
switching and numerous other projects have prevented me from doing the
clisp -> ecl switch, but finally its time has come since that is the
only way to support Solaris properly.
> 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
-~----------~----~----~----~------~----~------~--~---
