On Dec 6, 11:36 pm, "Bill Page" <[EMAIL PROTECTED]> wrote:
> On 12/6/07, mabshoff wrote:
>
> > The clisp update didn't work out due to a known issue with
> > gcc 4.2.3 with Debian testing on x86. So I reverted back
> > to clisp-2.41.p11.spkg.
>
> :-(
>
> Michael, do you mean that this is a problem known to the clisp
> developers?

Yep, see

http://sourceforge.net/tracker/index.php?func=detail&aid=1836142&group_id=1355&atid=101355

Ismail, aka cartman in IRC, reported it a while back and has narrowed
it down to

[quote]
Even further debugging shows following code from symbol.c is
miscompiled
at -O2 :

==========================

#include "lispbibl.c"

LISPFUNNR(keywordp,1)
{ /* (KEYWORDP object), CLTL p. 170 */
  {var object obj = popSTACK();
    VALUES_IF(symbolp(obj) && keywordp(obj));
  }}

==========================


Bruno do you think you could help me to get this code standalone
somehow
so I can report a gcc bug?
[/quote]

So I hope that Bruno can figure it out and fix.

> If so do you know if they have developed a work around?

Carl Witty played with the optimization flags and got it to work (he
reported the problem on debian testing x86 and also gave some details
in the 2.9.alpha0 thread). I will add that info to the ticket soon.
But there is no clean way to automate that workaround yet, so bumping
it back a week or two and hoping from an upstream patch is the way to
go. You might want to let Sam & Bruno know that we are counting on
them :)

What we can do is offer clisp-2.43.spkg as experimental, so that
people who want to install FriCAS or OpenAxiom can install it and
cross their fingers that it works.

>
> Regards,
> Bill Page.

Cheers,

Michael
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/
-~----------~----~----~----~------~----~------~--~---

Reply via email to