On 1/17/08, mabshoff <[EMAIL PROTECTED]> wrote: > > [I am not CCing the FriCAS google group since I am not subscribed] > > On Jan 17, 10:44 pm, "Bill Page" <[EMAIL PROTECTED]> wrote: > ... > > > > In principle doing a new fricas4sage release is fairly easy. First you > > need to generate a cached Lisp distribution and then just replace the > > contents of the source directory in the fricas4sage.spkg (tgz format) > > file. There are a few things that should also be done in the > > 'axiom.py' interface code: 1) the hack to disable readline in clisp > > is required in order to run FriCAS built with clisp to run properly on > > some systems. > > Sage installs readline per default in $SAGE_LOCAL >
I am sorry. Could you please explain how this applies or helps? The problem to which I was referring is that readline as compiled and linked into clisp can not be disabled through any command line option. readline when used with pexpect (on some machines) seems to cause problems with the 'axiom.py' interface. Discussions with Sam Steingold about this problem lead to his suggestion that we can disable readline for programs built with clisp by ensuring that stdin and stdout refer to different streams. Doing this solves the problems that have been reported when using axiom4sage (fricas4sage) on some platforms. The problem also does not occur for Axiom built using GCL when readlib support is disabled. Unfortunately I have to been able to provide Sam with a simplified test environment which demonstrates the problem so as of this date he has not considered this a bug in clisp. > 2) I really really would like to include a new method to > > allow sage to compile spad programs. 3) It would be great to have > > standard mechanism to build and install optional Axiom/FriCAS > > packages, e.g. JETbundles and PAFF. > > > > Also, it would be great to allow the 'axiom.console()' command to > > start the *full* version of FriCAS including HyperDoc and Graphics. > > Unfortunately this requires building FriCAS using a newer version of > > clisp than what is currently distributed with Sage. > > Note that we renamed the clip binary into clisp.bin in order to make > %clisp work when the sage directory has been moved. We fixed maxima, > but obviously nobody fixes the FriCAS optional spkg. > How can I reproduce this problem with the FriCAS optional spkg? Thanks. Regards, Bill Page. --~--~---------~--~----~------------~-------~--~----~ 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://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
