[sage-devel] Re: Project

a situation that you find entirely uncommon among the packages > that have been added to Sage in the past. Necessity is what drives > most of this kind of work. > > >  I've made a gcl Sage optional spkg: > > >    http://sage.math.washington.edu/home/was/tmp/gcl/gcl-200804

[sage-devel] Sage 3.0 is out

Hello folks, Sage 3.0 has been released on April 21st, 2008. It is available at http://sagemath.org/download.html * About Sage (http://www.sagemath.org) Sage is developed by volunteers and combines 71 open source packages. It is available for download from sagemath.org and its mirro

[sage-devel] East Coast Computer Algebra Day

On Saturday, May 10, the next East Coast Computer Algebra Day is being held. The contributors to Sage might find it an interesting meeting. I know that Sage sent a student last year. Tim --~--~-~--~~~---~--~~ To post to this gr

[sage-devel] Re: Project

entirely uncommon among the packages that have been added to Sage in the past. Necessity is what drives most of this kind of work. > I've made a gcl Sage optional spkg: > >http://sage.math.washington.edu/home/was/tmp/gcl/gcl-20080421.spkg > > It's just GCL-from-cvs +

[sage-devel] Re: Disable ENABLE_PADLOCK_SUPPORT?

It was released Aug last year? It's GCC 4.2 Developer Preview 1 (from the Developer Connection | Member Site - http://connect.apple.com/ ). It adds gcc-4.2 to gcc-4.0 included in Xcode. Rob On Apr 21, 2008, at 5:05 PM, William Stein wrote: > > On Mon, Apr 21, 2008 at 11:54 AM, Rob Goedman <

[sage-devel] Re: Project

Thank you very much for agreeing to work on this Michael. Way down the road, thin will be a big deal i think. On Mon, Apr 21, 2008 at 8:45 PM, mabshoff <[EMAIL PROTECTED]> wrote: > > William suggested I forward/post the stuff I wrote on fricas-devel > over there, too. Since his wish is my comma

[sage-devel] Re: Project

William suggested I forward/post the stuff I wrote on fricas-devel over there, too. Since his wish is my command ;) here we go: On Apr 21, 9:46 pm, Robert Dodier <[EMAIL PROTECTED]> wrote: > On Apr 20, 9:29 am, "William Stein" <[EMAIL PROTECTED]> wrote: Hello folks, > > c) ecls: the ray of hop

[sage-devel] Re: Disable ENABLE_PADLOCK_SUPPORT?

On Mon, Apr 21, 2008 at 11:54 AM, Rob Goedman <[EMAIL PROTECTED]> wrote: > > This is XCode 3.0 with the updated gcc suite from the Apple developer > site. It sure seems to compile an awful lot before hitting this. How does one get the "updated gcc suite from the Apple Developer site"? I just fo

[sage-devel] Re: How to use alternate gfortran-4.3

On Apr 22, 12:05 am, "Gonzalo Tornaria" <[EMAIL PROTECTED]> wrote: > On 4/21/08, mabshoff <[EMAIL PROTECTED]> wrote: > > > > >  > export CC=gcc-4.3 > >  > export CXX=g++-4.3 > > > I am not sure this will work all the time since sometimes we overwrite > >  CC or CXX. I would suggest you put the 4

[sage-devel] Re: Sage 3.0.rc1 released!

One test failed on standard rc1+clisp...p15, running 32 bit Arch linux with GCC 4.3, /proc/cpuinfo below and doctest below it. cheers, Andrzej. cat /proc/cpuinfo processor : 0 vendor_id : AuthenticAMD cpu family : 6 model : 10 model name : AMD Athlon(tm) XP 2600+

[sage-devel] Re: Project

On Apr 21, 11:48 pm, Robert Dodier <[EMAIL PROTECTED]> wrote: > On Apr 20, 5:55 pm, mabshoff <[EMAIL PROTECTED] Hi Robert, > dortmund.de> wrote: > > I forgot one important argument here: With ecls you can embed the lisp > > interpreter into an external library, hence we would be able to use >

[sage-devel] Re: How to use alternate gfortran-4.3

On 4/21/08, mabshoff <[EMAIL PROTECTED]> wrote: > > > export CC=gcc-4.3 > > export CXX=g++-4.3 > > > I am not sure this will work all the time since sometimes we overwrite > CC or CXX. I would suggest you put the 4.3 gcc and g++ somewhere in > $PATH before gcc and g++ - Sage will then use them

[sage-devel] Re: Sage 3.0.rc1 released!

On my 32-bit kubuntu machine all is well with rc1: All tests passed! Total time for all tests: 3933.1 seconds John 2008/4/21 mabshoff <[EMAIL PROTECTED]>: > > > > On Apr 21, 11:14 pm, "John Cremona" <[EMAIL PROTECTED]> wrote: > > 2008/4/21 William Stein <[EMAIL PROTECTED]>: > > > > > Both

[sage-devel] Re: Disable ENABLE_PADLOCK_SUPPORT?

On Apr 21, 8:54 pm, Rob Goedman <[EMAIL PROTECTED]> wrote: Hi Rob, > This is XCode 3.0 with the updated gcc suite from the Apple developer   > site. It sure seems to compile an awful lot before hitting this. > > I wonder how to make this work with R. R has these 100s of packages,   > many of whi

[sage-devel] Re: Project

On Apr 20, 5:55 pm, mabshoff <[EMAIL PROTECTED] dortmund.de> wrote: > I forgot one important argument here: With ecls you can embed the lisp > interpreter into an external library, hence we would be able to use > Maxima as a library instead of using the inefficient pexpect > interface. I am not s

[sage-devel] Re: Sage 3.0.rc1 released!

On Apr 21, 11:14 pm, "John Cremona" <[EMAIL PROTECTED]> wrote: > 2008/4/21 William Stein <[EMAIL PROTECTED]>: > >  Both of the failures you guys report -- in twist.py and testdoc.py involve > >  opening a network port, doing some tests that things are working, > >  then closing it. I think clos

[sage-devel] Re: How to use alternate gfortran-4.3

On Apr 21, 11:17 pm, "Gonzalo Tornaria" <[EMAIL PROTECTED]> wrote: Hi Gonzalo > I am compiling with gcc-4.3, my previous build of 3.0rc0 worked fine > (no gfortran installed in the system). However, for my build of 3.0rc1 > I tried to install using gfortran-4.3 (from debian/testing). > > I follo

[sage-devel] Re: Sage 3.0.rc1 released!

Please keep reporting them. It should be the case that these tests pass on the first run. On Mon, Apr 21, 2008 at 2:14 PM, John Cremona <[EMAIL PROTECTED]> wrote: > > 2008/4/21 William Stein <[EMAIL PROTECTED]>: > > > > > > On Mon, Apr 21, 2008 at 12:49 PM, Jaap Spies <[EMAIL PROTECTED]> wrote

[sage-devel] How to use alternate gfortran-4.3

I am compiling with gcc-4.3, my previous build of 3.0rc0 worked fine (no gfortran installed in the system). However, for my build of 3.0rc1 I tried to install using gfortran-4.3 (from debian/testing). I followed instructions in README.txt, and set: export CC=gcc-4.3 export CXX=g++-4.3 export SAG

[sage-devel] Re: Sage 3.0.rc1 released!

2008/4/21 William Stein <[EMAIL PROTECTED]>: > > On Mon, Apr 21, 2008 at 12:49 PM, Jaap Spies <[EMAIL PROTECTED]> wrote: > > > > mabshoff wrote: > > > > > > Hello folks, > > > > > > here goes Sage 3.0.rc1. We are down to one blocker, i.e. the "-O0" > > > fallback for clips in case of

[sage-devel] Re: Project

>> Having spent a fair portion of my life porting software, I understand >> the frustrations you feel. And having spent the bulk of my life using >> Lisp I "get" the get-rid-of-lisp pushback. But a lot of astonishingly >> good computer algebra exists in lisp (we won't discuss the reasons). >> Repr

[sage-devel] Re: Sage 3.0.rc1 released!

On Mon, Apr 21, 2008 at 12:49 PM, Jaap Spies <[EMAIL PROTECTED]> wrote: > > mabshoff wrote: > > > > Hello folks, > > > > here goes Sage 3.0.rc1. We are down to one blocker, i.e. the "-O0" > > fallback for clips in case of failure. Other than that this release > > should build and test fine.

[sage-devel] Re: Sage 3.0.rc1 released!

Built ok but one test fail on 64-bit Suse system The following tests failed: sage -t devel/sage/sage/dsage/tests/testdoc.py -- but passed when run by itself. Still building on 32 bit kubuntu. John 2008/4/21 mabshoff <[EMAIL PROTECTED]>: > > > Hello folks, > > here goes Sage 3.0.rc1

[sage-devel] Re: Sage 3.0.rc1 released!

mabshoff wrote: > > Hello folks, > > here goes Sage 3.0.rc1. We are down to one blocker, i.e. the "-O0" > fallback for clips in case of failure. Other than that this release > should build and test fine. The 3.0 release is imminent, so if you > find anything you better be quick. The plan is to f

[sage-devel] Re: Project

On Apr 21, 6:09 pm, root <[EMAIL PROTECTED]> wrote: Hi Tim, > > The GCL-devel mailing list has on average about 5-6 messages a month > > during the last couple of months, except for a bunch of messages in > > January about people trying to build GCL from cvs. > > You claim that you pass prob

[sage-devel] Re: Fwd: mercurial --> plain text --> mercurial

On Apr 21, 2008, at 11:47 AM, John Cremona wrote: > Sorry if this is a stupid question: if you are going to make a new > complete repository with a patched version of mercurial, does that > mean that native mercurial installations will not work with Sage from > now on, only Sage's "own" version?

[sage-devel] Re: Disable ENABLE_PADLOCK_SUPPORT?

This is XCode 3.0 with the updated gcc suite from the Apple developer site. It sure seems to compile an awful lot before hitting this. I wonder how to make this work with R. R has these 100s of packages, many of which need to be compiled when installed. Right now, at least on the Mac, R-2-7

[sage-devel] Re: Compile Error

On Apr 21, 12:47 pm, "William Stein" <[EMAIL PROTECTED]> wrote: > Thanks.  That's helpful.  Unfortunately it also means at least I have > no clue how to fix the problem. > > You might try just installing clisp system-wide (using your package > management system), then tell SAge to use that by typi

[sage-devel] Re: Compile Error

Just as pasted in 4'th post in topic (it's of course 32bit Arch... otherwise would have said Arch64 as it's not-so-finished-port in my opinion)... there's cpuinfo again: processor : 0 vendor_id : AuthenticAMD cpu family : 6 model : 10 model name : AMD Athlon(tm) XP

[sage-devel] Re: Compile Error

Well, I don't know if Arch's clisp works with Sage, it just works by itself... and about downgrade, it would be hard, because many packages in Arch are already built against GCC4.3 and downgrade would require manual rebuild of many vital packages and introduce many incompatibilities with new softw

[sage-devel] Re: Fwd: mercurial --> plain text --> mercurial

Sorry if this is a stupid question: if you are going to make a new complete repository with a patched version of mercurial, does that mean that native mercurial installations will not work with Sage from now on, only Sage's "own" version? John 2008/4/21 Robert Bradshaw <[EMAIL PROTECTED]>: > >

[sage-devel] Re: Fwd: mercurial --> plain text --> mercurial

On Apr 21, 2008, at 11:34 AM, mabshoff wrote: > On Apr 21, 8:24 pm, Robert Bradshaw <[EMAIL PROTECTED]> > wrote: >> On Apr 21, 2008, at 11:14 AM, William Stein wrote: > > Hi, > Yes, I could. This would mean that no pre-3.0 bundles would apply to post-3.0 (short of re-basing the

[sage-devel] Re: Fwd: mercurial --> plain text --> mercurial

On Apr 21, 8:24 pm, Robert Bradshaw <[EMAIL PROTECTED]> wrote: > On Apr 21, 2008, at 11:14 AM, William Stein wrote: Hi, > >>  Yes, I could. This would mean that no pre-3.0 bundles would apply to > >>  post-3.0 (short of re-basing the bundles--and the big one (coercion) > >>  I could rebase mys

[sage-devel] Re: Fwd: mercurial --> plain text --> mercurial

On Apr 21, 2008, at 11:14 AM, William Stein wrote: > On Mon, Apr 21, 2008 at 11:06 AM, Robert Bradshaw > <[EMAIL PROTECTED]> wrote: >> >> >> On Apr 21, 2008, at 10:53 AM, William Stein wrote: >> >>> On Mon, Apr 21, 2008 at 10:51 AM, mabshoff >>> <[EMAIL PROTECTED]> wrote: Hi, >>>

[sage-devel] Re: Sage 3.0.rc0 released!

On 4/21/08, John Cremona <[EMAIL PROTECTED]> wrote: > Better late than never (perhaps): rc0 built fine for me but has two > failures with testall: Same here, rc0, both on a 64 bit and a 32 bit build. In the 64 bit build (A) there is also a failure in rings/real_double.pyx. I will compile rc1 o

[sage-devel] Re: Fwd: mercurial --> plain text --> mercurial

On Mon, Apr 21, 2008 at 11:06 AM, Robert Bradshaw <[EMAIL PROTECTED]> wrote: > > > On Apr 21, 2008, at 10:53 AM, William Stein wrote: > > > On Mon, Apr 21, 2008 at 10:51 AM, mabshoff > > <[EMAIL PROTECTED]> wrote: > >> > >> Hi, > >> > >> > >>> Could you "rebase" the entire Sage repo so it

[sage-devel] Re: Fwd: mercurial --> plain text --> mercurial

On Apr 21, 2008, at 10:53 AM, William Stein wrote: > On Mon, Apr 21, 2008 at 10:51 AM, mabshoff > <[EMAIL PROTECTED]> wrote: >> >> Hi, >> >> >>> Could you "rebase" the entire Sage repo so it has the new hashes, >>> then included >>> it for Sage-3.0 :-) If we're going to make a massive change

[sage-devel] Re: Project

I get the following error: ;; Compiling ../lsp/gcl_listlib.lsp. ;; End of Pass 1. ;; End of Pass 2. ;; OPTIMIZE levels: Safety=3, Space=0, Speed=3, (Debug quality ignored) ;; Finished compiling ../lsp/gcl_listlib.o. ;; Loading /opt/sage-3.0.alpha6/spkg/build/gcl-20080421/src/lsp/gcl_listlib.o

[sage-devel] Re: Compile Error

On Mon, Apr 21, 2008 at 10:53 AM, Andrzej Giniewicz <[EMAIL PROTECTED]> wrote: > > Also have same error with both .p13 and .p14, but by some random case > I got other error when run make for the second time, there is complete > log from first build: www.giniu.ravenlord.ws/install.log.1 (HUGE on

[sage-devel] Re: Compile Error

Also have same error with both .p13 and .p14, but by some random case I got other error when run make for the second time, there is complete log from first build: www.giniu.ravenlord.ws/install.log.1 (HUGE one), and there is second one, small log from second build ( www.giniu.ravenlord.ws/install.

[sage-devel] Re: Disable ENABLE_PADLOCK_SUPPORT?

On Apr 21, 6:54 pm, "William Stein" <[EMAIL PROTECTED]> wrote: > On Mon, Apr 21, 2008 at 9:31 AM, Rob Goedman <[EMAIL PROTECTED]> wrote: > > Hi, > > >  Brand new to Sage builds! > > >  On Mac OS 10.5.2, with: > > >  Robs-Intel:sage-3.0.rc0 rob$ gcc -v > >  Using built-in specs. > >  Target: i686

[sage-devel] Re: Fwd: mercurial --> plain text --> mercurial

On Mon, Apr 21, 2008 at 10:51 AM, mabshoff <[EMAIL PROTECTED]> wrote: > > Hi, > > > > Could you "rebase" the entire Sage repo so it has the new hashes, then > included > > it for Sage-3.0 :-) If we're going to make a massive change like > > that, 3.0 would > > be the time to do it. Or does

[sage-devel] Re: Fwd: mercurial --> plain text --> mercurial

Hi, > Could you "rebase" the entire Sage repo so it has the new hashes, then > included > it for Sage-3.0 :-)  If we're going to make a massive change like > that, 3.0 would > be the time to do it.  Or does that request make no sense? We will likely have the same problem every time we merge hea

[sage-devel] Re: Fwd: mercurial --> plain text --> mercurial

On Mon, Apr 21, 2008 at 10:32 AM, Robert Bradshaw <[EMAIL PROTECTED]> wrote: > > > On Apr 21, 2008, at 7:12 AM, William Stein wrote: > > > On Thu, Mar 27, 2008 at 4:49 PM, Robert Bradshaw > > <[EMAIL PROTECTED]> wrote: > >> > >> I've looked into this some more and it looks like we can comple

[sage-devel] Re: Fwd: mercurial --> plain text --> mercurial

On Apr 21, 2008, at 7:12 AM, William Stein wrote: > On Thu, Mar 27, 2008 at 4:49 PM, Robert Bradshaw > <[EMAIL PROTECTED]> wrote: >> >> I've looked into this some more and it looks like we can completely >> reconstruct a repository from the export of all its keywords. The >> trick is to use th

[sage-devel] Re: Disable ENABLE_PADLOCK_SUPPORT?

On Mon, Apr 21, 2008 at 9:31 AM, Rob Goedman <[EMAIL PROTECTED]> wrote: > Hi, > > Brand new to Sage builds! > > On Mac OS 10.5.2, with: > > Robs-Intel:sage-3.0.rc0 rob$ gcc -v > Using built-in specs. > Target: i686-apple-darwin9 > Configured with: /var/tmp/gcc_42/gcc_42-5531~1/src/configure

[sage-devel] Re: Sage 3.0.rc0 released!

Better late than never (perhaps): rc0 built fine for me but has two failures with testall: sage -t devel/sage/sage/interfaces/r.py sage -t devel/sage/sage/rings/polynomial/laurent_polynomial_ring.py That's on a 32-bit machine running kubuntu: Linux fermat 2.6.22-14-generic #1 SMP Tue Feb

[sage-devel] Re: Compile Error

On Mon, Apr 21, 2008 at 9:42 AM, <[EMAIL PROTECTED]> wrote: > > And by same error I mean the one I initially started this thread with, > sorry about the ambiguity. Thanks. That's helpful. Unfortunately it also means at least I have no clue how to fix the problem. You might try just installi

[sage-devel] Re: Project

On Mon, Apr 21, 2008 at 11:09 AM, root <[EMAIL PROTECTED]> wrote: > GCL runs on windows although I have not spent any time on a > windows port. Waldek has, so he might have an opinion. Well, *I* spend considerable time making Axiom buildable on Windows back when I was working on Axiom.build-im

[sage-devel] Re: Compile Error

And by same error I mean the one I initially started this thread with, sorry about the ambiguity. --~--~-~--~~~---~--~~ 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,

[sage-devel] Re: Compile Error

Yessir, I tried it both ways, the first way gave me an error saying that I didn't have CFLAGS set, here is the error: gcc -I/home/zarathustra/Download/sage-3.0.rc1/local/include -g -O2 -W - Wswitch -Wcomment -Wpointer-arith -Wimplicit -Wreturn-type -Wmissing In file included from lispbibl.d:325,

[sage-devel] Re: Compile Error

On Mon, Apr 21, 2008 at 9:21 AM, <[EMAIL PROTECTED]> wrote: > > On Apr 21, 11:36 am, "William Stein" <[EMAIL PROTECTED]> wrote: > > > > Michael did not implement the -O0 thing as planned, since > > he ran out of time and got tired after working nearly nonstop > > on other issues with rc0. >

[sage-devel] Re: Compile Error

On Apr 21, 11:36 am, "William Stein" <[EMAIL PROTECTED]> wrote: > > Michael did not implement the -O0 thing as planned, since > he ran out of time and got tired after working nearly nonstop > on other issues with rc0. > > So I just made a clisp spkg for you to try.  It sets CFLAGS to -O0 if > the

[sage-devel] Re: Compile Error

>export CFLAGS="-O0" and then > > ./sage -i clisp-2.41.p13.spkg > > If that doesn't work, then a method other than setting CFLAGS will be > needed... I had the same problem and CFLAGS="-O0"; ./spkg-install (which is equivalent to the above) in the appropriate "sage -sh" fixed the p

[sage-devel] Re: Compile Error

On Mon, Apr 21, 2008 at 8:26 AM, <[EMAIL PROTECTED]> wrote: > > On Apr 20, 10:04 pm, mabshoff <[EMAIL PROTECTED] > > dortmund.de> wrote: > > On Apr 21, 4:01 am, [EMAIL PROTECTED] wrote: > > > > > The plan now is to do the following: > > > > a) Compile clisp with "-02" - if it works everybod

[sage-devel] Re: Compile Error

On Apr 20, 10:04 pm, mabshoff <[EMAIL PROTECTED] dortmund.de> wrote: > On Apr 21, 4:01 am, [EMAIL PROTECTED] wrote: > > The plan now is to do the following: > >  a) Compile clisp with "-02" - if it works everybody is happy >  b) If it doesn't work fall back to "-O0" and hope for the best. > > This

[sage-devel] Re: Project

>> I think you'd feel the same frustrations with Python if you compiled >> Python from scratch for every platform. You ship "sources" but assume >> that the python language exists and is compatible, which is not likely >> to be the case when 3.0 arrives. If you can assume the python >> language,

[sage-devel] Re: Project

On Mon, Apr 21, 2008 at 9:09 AM, root <[EMAIL PROTECTED]> wrote: > > >For example, is the fact that GCL doesn't build for us anywhere, something > >that you think we'll get passed by just trying harder? Or is it going > >to be really really hard. > >

[sage-devel] Re: Project

On Apr 21, 2008, at 12:09 PM, root wrote: > I think you'd feel the same frustrations with Python if you compiled > Python from scratch for every platform. You ship "sources" but assume > that the python language exists and is compatible, which is not likely > to be the case when 3.0 arrives. If

[sage-devel] Re: Project

>For example, is the fact that GCL doesn't build for us anywhere, something >that you think we'll get passed by just trying harder? Or is it going >to be really really hard. All versions are built with GCL. I do not have access to a

[sage-devel] Re: Fwd: mercurial --> plain text --> mercurial

On Thu, Mar 27, 2008 at 4:49 PM, Robert Bradshaw <[EMAIL PROTECTED]> wrote: > > I've looked into this some more and it looks like we can completely > reconstruct a repository from the export of all its keywords. The > trick is to use the --exact keyword when importing. This forces it to > appl

[sage-devel] Re: Project

de has been tested or not or what. The last released version is from 2005, and it's clear the website is just dead (maybe somebody lost the password?!) I mean, it just looks a little silly for the website (http://www.gnu.org/software/gcl/) to start with: NEW! (20050810) GCL 2.6.7 is relea

[sage-devel] Re: [fricas-devel] Re: Project

On Mon, Apr 21, 2008 at 3:22 AM, Ondrej Certik <[EMAIL PROTECTED]> wrote: > > > On Mon, Apr 21, 2008 at 9:25 AM, mabshoff > <[EMAIL PROTECTED]> wrote: > > > > On Apr 21, 9:09 am, Martin Rubey <[EMAIL PROTECTED]> wrote: > > > Just a quick note now, maybe more later: > > > > > > > > Hi

[sage-devel] Re: [fricas-devel] Re: Project

On Mon, Apr 21, 2008 at 9:25 AM, mabshoff <[EMAIL PROTECTED]> wrote: > > On Apr 21, 9:09 am, Martin Rubey <[EMAIL PROTECTED]> wrote: > > Just a quick note now, maybe more later: > > > > Hi Martin, > > > > > "I know of three open source implementations of lisp that do not need to > > > boots

[sage-devel] Re: Sage 3.0.rc0 released!

On Apr 21, 11:01 am, bill purvis <[EMAIL PROTECTED]> wrote: > On Sunday 20 April 2008, mabshoff wrote: > > > Hello folks, > > > Here goes 3.0.rc0. We knocked out a couple blocker, merged the new > > R pexpect interface. This release should also build out of the box > > on RHEL 5/Itanium and SLES

[sage-devel] Sage 3.0.rc1 released!

Hello folks, here goes Sage 3.0.rc1. We are down to one blocker, i.e. the "-O0" fallback for clips in case of failure. Other than that this release should build and test fine. The 3.0 release is imminent, so if you find anything you better be quick. The plan is to follow up the 3.0 release with

[sage-devel] Re: Sage 3.0.rc0 released!

On Sunday 20 April 2008, mabshoff wrote: > Hello folks, > > Here goes 3.0.rc0. We knocked out a couple blocker, merged the new > R pexpect interface. This release should also build out of the box > on RHEL 5/Itanium and SLES 10/Itanium without the need to set any > FORTRAN env variables. We have a

[sage-devel] Re: [fricas-devel] Re: Project

On Apr 21, 9:09 am, Martin Rubey <[EMAIL PROTECTED]> wrote: > Just a quick note now, maybe more later: Hi Martin, > > "I know of three open source implementations of lisp that do not need to > > bootstrap themselves" > > What's wrong with bootstrapping, and in particular with > sbcl?http://ww

[sage-devel] Re: [fricas-devel] Re: [sage-devel] Re: [fricas-devel] Re: Project

Just a quick note now, maybe more later: "William Stein" <[EMAIL PROTECTED]> writes: > I don't understand the Axiom distribution enough to understand > how big it is, but my impression is that it is *also* huge. Looking > in the src/src/algebra directory there are many hundreds of > thousands o