[sage-devel] Re: Sage 3.0 released

On Apr 24, 2:22 am, mark mcclure <[EMAIL PROTECTED]> wrote: > On Apr 23, 6:24 pm, mark mcclure <[EMAIL PROTECTED]> wrote: Hi Mark, > make; followed by "sage -ba" seems to have done the trick.  Everything > seems to be working great and "./sage -testall" passed all tests. > > I've got a workin

[sage-devel] Re: Sage 3.0 released

On Apr 23, 6:24 pm, mark mcclure <[EMAIL PROTECTED]> wrote: > On Apr 23, 6:17 pm, mabshoff <[EMAIL PROTECTED] > > dortmund.de> wrote: > > On Apr 24, 12:14 am, mark mcclure <[EMAIL PROTECTED]> wrote: > > > The trailing kg is missing. Should I simply change the > > > name and try again? > > > Yes.

[sage-devel] Re: Sage 3.0 released

On Apr 23, 6:17 pm, mabshoff <[EMAIL PROTECTED] dortmund.de> wrote: > On Apr 24, 12:14 am, mark mcclure <[EMAIL PROTECTED]> wrote: > > The trailing kg is missing. Should I simply change the > > name and try again? > > Yes. Run make, then a "sage -b". If Sage starts up all ought be be > fixed. If

[sage-devel] Re: Sage 3.0 released

On Apr 24, 12:14 am, mark mcclure <[EMAIL PROTECTED]> wrote: > On Apr 23, 6:10 pm, mabshoff <[EMAIL PROTECTED] > > dortmund.de> wrote: > > for whatever reason there is no Singular in your build log. Right at > > the top it says: > > ... > > Could you check if spkg/standard contains any file call

[sage-devel] Re: Sage 3.0 released

On Apr 23, 6:10 pm, mabshoff <[EMAIL PROTECTED] dortmund.de> wrote: > for whatever reason there is no Singular in your build log. Right at > the top it says: > ... > Could you check if spkg/standard contains any file called > singular-3-0-4-2-20080405.p1.spkg, i.e: No, there's not. Strangely, th

[sage-devel] Re: Sage 3.0 released

On Apr 23, 11:51 pm, mark mcclure <[EMAIL PROTECTED]> wrote: > On Apr 23, 4:43 pm, mabshoff <[EMAIL PROTECTED] > > dortmund.de> wrote: > >  We will be much more aggressive from now on in blacklisting know > > broken compilers since at least on OSX it should work out of the box > > because there

[sage-devel] Re: Sage 3.0 released

On Apr 23, 5:54 pm, "William Stein" <[EMAIL PROTECTED]> wrote: > Could you type >./sage -br > form the SAGE_ROOT directory and send the output? Sure: -- sage: Building and installing modified SAGE library files. Installing c_lib g++

[sage-devel] Re: Sage 3.0 released

On Wed, Apr 23, 2008 at 2:51 PM, mark mcclure <[EMAIL PROTECTED]> wrote: > > On Apr 23, 4:43 pm, mabshoff <[EMAIL PROTECTED] > > dortmund.de> wrote: > > > We will be much more aggressive from now on in blacklisting know > > broken compilers since at least on OSX it should work out of the box >

[sage-devel] Re: Sage 3.0 released

On Apr 23, 4:43 pm, mabshoff <[EMAIL PROTECTED] dortmund.de> wrote: > We will be much more aggressive from now on in blacklisting know > broken compilers since at least on OSX it should work out of the box > because there is so little variety of the OS itself and Apple usually > is the tool chai

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

Andrzej Giniewicz wrote: > 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. > > and only test that failed: > > sage -t devel/sage-main/sage/rings/complex_double.pyx > ***

[sage-devel] Re: Sage 3.0 released

On Apr 23, 10:04 pm, mark mcclure <[EMAIL PROTECTED]> wrote: > On Apr 23, 3:53 pm, mabshoff <[EMAIL PROTECTED] > > dortmund.de> wrote: > > This looks like Singular did not build properly. > > > > Please post a link to the  whole install.log here so I can take a > > look. Hi Mark, > Unfortunat

[sage-devel] Re: Sage 3.0 released

On Apr 23, 3:53 pm, mabshoff <[EMAIL PROTECTED] dortmund.de> wrote: > This looks like Singular did not build properly. > > Please post a link to the whole install.log here so I can take a > look. Unfortunately, I no longer have the whole install.log. In hopes of fixing the problem, I upgraded

[sage-devel] Re: Sage 3.0 released

On Apr 23, 3:54 pm, mhampton <[EMAIL PROTECTED]> wrote: > I'm not sure what the problem is, probably William Stein or Michael > Abshoff will be able to answer that, but maybe its simplest to just > upgrade your gcc with the latest stuff from apple. My gcc is build > 5465; I'm not sure how they

[sage-devel] Re: Sage 3.0 released

Hi Mark! I'm not sure what the problem is, probably William Stein or Michael Abshoff will be able to answer that, but maybe its simplest to just upgrade your gcc with the latest stuff from apple. My gcc is build 5465; I'm not sure how they pick those version numbers. I know you are (or were?) a

[sage-devel] Re: Sage 3.0 released

On Apr 23, 9:23 pm, mark mcclure <[EMAIL PROTECTED]> wrote: > On Apr 23, 1:08 pm, Robert Bradshaw <[EMAIL PROTECTED]> > wrote: > > > >>  Are their binaries for OS X 10.4? > > > NO.  And there won't be until somebody volunteers to make them. > > > Can you make them? > > > Yes, do I just build and

[sage-devel] Re: Sage 3.0 released

On Apr 23, 1:08 pm, Robert Bradshaw <[EMAIL PROTECTED]> wrote: > >> Are their binaries for OS X 10.4? > > NO. And there won't be until somebody volunteers to make them. > > Can you make them? > > Yes, do I just build and do sage -bdist? I attempted to compile sage 3.0 on my Mac G5 running OS

[sage-devel] Re: Sage 3.0 released

I have a MAC OX X 10.4.4 build in process. Its on a PowerPC (G4) I'll make it available when it completes. Tim --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] Fo

[sage-devel] Re: Sage 3.0 released

On Apr 23, 2008, at 10:06 AM, William Stein wrote: > > On Wed, Apr 23, 2008 at 10:03 AM, Robert Bradshaw > <[EMAIL PROTECTED]> wrote: >> >> Are their binaries for OS X 10.4? > > NO. And there won't be until somebody volunteers to make them. See > my long email about this a few minutes ago in Sa

[sage-devel] Re: Sage 3.0 released

On Wed, Apr 23, 2008 at 10:03 AM, Robert Bradshaw <[EMAIL PROTECTED]> wrote: > > Are their binaries for OS X 10.4? NO. And there won't be until somebody volunteers to make them. See my long email about this a few minutes ago in Sage-support. Can you make them? > > On Apr 23, 2008, at 4:58 A

[sage-devel] Re: Sage 3.0 released

Are their binaries for OS X 10.4? On Apr 23, 2008, at 4:58 AM, mabshoff wrote: > > [Note: If you are interested in announcements only please subscribe to > sage-announce. It is limited to roughly one email every ten days.] > > Hello folks, > > Sage 3.0 has been released on April 21st, 2008. It is

[sage-devel] Re: Sage 3.0 notebook fails to display

sage -b solved it. thanks --Tim --~--~-~--~~~---~--~~ 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 UR

[sage-devel] Re: Sage 3.0 notebook fails to display

On Apr 23, 3:50 am, [EMAIL PROTECTED] wrote: Hi Tim, > On a clean build (see specs below) > (log is at ) > > I tried > > sage: hg_sage.pull() > sage: hg_sage.update() > sage: hg_sage.merge() > but it says there is nothing to merge. > > Tim When

[sage-devel] Re: Sage 3.0 is out

Installed fine and all tests passed on an ubuntu 7.10 amd64 machine. On Tue, Apr 22, 2008 at 2:10 AM, mabshoff <[EMAIL PROTECTED]> wrote: > > Hello folks, > > Sage 3.0 has been released on April 21st, 2008. It is available at > >http://sagemath.org/download.html > > * About Sage (h

[sage-devel] Re: Sage 3.0 is out

That worked for me to (after the pull()) on a 64-bit Suse machine. John 2008/4/22 Jaap Spies <[EMAIL PROTECTED]>: > > William Stein wrote: > > On Tue, Apr 22, 2008 at 8:04 AM, Jaap Spies <[EMAIL PROTECTED]> wrote: > >> mabshoff wrote: > >> > Hello folks, > >> > > >> > Sage 3.0 has be

[sage-devel] Re: Sage 3.0 is out

On Apr 22, 6:00 pm, "William Stein" <[EMAIL PROTECTED]> wrote: > On Tue, Apr 22, 2008 at 10:10 AM, root <[EMAIL PROTECTED]> wrote: > > >  Sage 3.0 build failed. See: > >   > > You have to use a c99 compliant compiler. You're using gcc-3.2.2 which isn

[sage-devel] Re: Sage 3.0 is out

On Tue, Apr 22, 2008 at 10:10 AM, root <[EMAIL PROTECTED]> wrote: > > Sage 3.0 build failed. See: > > You have to use a c99 compliant compiler. You're using gcc-3.2.2 which isn't C99 compliant. Please use a modern compiler (anything newer than gcc

[sage-devel] Re: Sage 3.0 is out

On Tue, Apr 22, 2008 at 8:51 AM, Jaap Spies <[EMAIL PROTECTED]> wrote: > > William Stein wrote: > > > > > > Please do > >sage: hg_sage.pull() > > > > then > > > >sage -br > > > > and try that test again > > Something strange was going on with the notebook(), but > after hg_sag

[sage-devel] Re: Sage 3.0 is out

Sage 3.0 build failed. See: --~--~-~--~~~---~--~~ 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 h

[sage-devel] Re: Sage 3.0 is out

William Stein wrote: > > > Please do >sage: hg_sage.pull() > > then > >sage -br > > and try that test again Something strange was going on with the notebook(), but after hg_sage.pull() and ./sage -br the notebook starts in Firefox. The problem I have reported in trac #2935 is still th

[sage-devel] Re: Sage 3.0 is out

William Stein wrote: > On Tue, Apr 22, 2008 at 8:04 AM, Jaap Spies <[EMAIL PROTECTED]> wrote: >> mabshoff wrote: >> > Hello folks, >> > >> > Sage 3.0 has been released on April 21st, 2008. It is available at >> > >> >http://sagemath.org/download.html >> > >> > * About Sage (htt

[sage-devel] Re: Sage 3.0 is out

On Tue, Apr 22, 2008 at 8:04 AM, Jaap Spies <[EMAIL PROTECTED]> wrote: > > mabshoff wrote: > > 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-devel] Re: Sage 3.0 is out

mabshoff wrote: > 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) > Fedora 7, 32 bits: -- The fo

[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: 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: 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: 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] 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: 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: 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: 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: 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] 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: Sage 3.0.rc0 released!

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 new blocker (#2972), so

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

On the following machine: Linux sillyname 2.6.22-gentoo-r5 #2 SMP Tue Aug 28 23:46:12 UTC 2007 i686 Intel(R) Core(TM)2 CPU 6400 @ 2.13GHz GenuineIntel GNU/Linux it compiled fine and passed all tests with one exception: sage -t devel/sage/sage/interfaces/r.py *

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

All tests passed! Total time for all tests: 2339.5 seconds grep: /home/jec/sage-3.0.rc0/tmp/test-dsage.log: No such file or directory Please see /home/jec/sage-3.0.rc0/tmp/test.log for the complete log from this test. John 2008/4/20 mabshoff <[EMAIL PROTECTED]>: > > Hello folks, > > Here goes

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

mabshoff wrote: > Folks, > > here we go with 3.0.alpha6. On Fedora 7, 32 bits: -- All tests passed! Total time for all tests: 4916.4 seconds grep: /home/jaap/downloads/sage-3.0.alpha6/tmp/test-dsage.log: No such file or direct

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

Built fine. --testall produced this The following tests failed: sage -t devel/sage/sage/rings/polynomial/pbori.pyx but a retry of that one worked fine. John 2008/4/19 mabshoff <[EMAIL PROTECTED]>: > > Folks, > > here we go with 3.0.alpha6. It should have been out a day or two ago,

[sage-devel] Re: Sage 3.0.alpha5 released

On Apr 17, 7:47 pm, Kate <[EMAIL PROTECTED]> wrote: > Michael, > > > Mhh, can you remove the extra redirection in spkg-install and try > > again. Hi Kate. > I still have a problem in clisp.  To remind you this is 3.0.alpha5 > compiled with gcc-4.3.0. How could I forget? ;) > gcc -g -O2 -W -W

[sage-devel] Re: Sage 3.0.alpha5 released

Michael, > Mhh, can you remove the extra redirection in spkg-install and try > again. I still have a problem in clisp. To remind you this is 3.0.alpha5 compiled with gcc-4.3.0. gcc -g -O2 -W -Wswitch -Wcomment -Wpointer-arith -Wimplicit -Wreturn- type -Wmissing-declarations -Wno-sign-compare -

[sage-devel] Re: Sage 3.0.alpha5 released

On Apr 17, 6:04 pm, Kate <[EMAIL PROTECTED]> wrote: > Michael, Hi Kate, > Adding #include  to >     givaro-3.2.10.rc3.p0/src/src/kernel/gmp++/gmp++.h > worked. Ok, I will patch Givaro And LinBox then to do so. IIRC I already patched that in LinBox for gcc 4.3 once, but maybe I am mixing thin

[sage-devel] Re: Sage 3.0.alpha5 released

Michael, Adding #include to givaro-3.2.10.rc3.p0/src/src/kernel/gmp++/gmp++.h worked. I also have had to add #include to libfplll-2.1.6-20071129.p2/src/src/main.cpp. Now it has failed in clisp-2.41.p13 with [1] + Suspended (tty input) make >& zzz1.4 Kate On Apr 16, 5:19

[sage-devel] Re: Sage 3.0.alpha5 released

On Apr 16, 9:22 pm, Kate <[EMAIL PROTECTED]> wrote: > Michael, > > When trying to build 3.0.alpha5 using gcc-4.3.0 on x86-Linux > (pentium4-fc6), I get the following error in givaro > > make[5]: Entering directory `/home/kate/sage/sage-3.0.alpha5-x86-Linux/ > spkg/build/givaro-3.2.10.rc3.p0/src/

[sage-devel] Re: Sage 3.0.alpha5 released

Michael, When trying to build 3.0.alpha5 using gcc-4.3.0 on x86-Linux (pentium4-fc6), I get the following error in givaro make[5]: Entering directory `/home/kate/sage/sage-3.0.alpha5-x86-Linux/ spkg/build/givaro-3.2.10.rc3.p0/src/src/kernel/gmp++' /bin/sh ../../../libtool --tag=CXX --mode=comp

[sage-devel] Re: Sage 3.0.alpha5 released

All tests passed for me on Linux host-57-71 2.6.18.8-0.3-default #1 SMP Tue Apr 17 08:42:35 UTC 2007 x86_64 x86_64 x86_64 GNU/Linux with gcc version 4.1.2 20061115 (prerelease) (SUSE Linux) John 2008/4/16 Justin C. Walker <[EMAIL PROTECTED]>: > > > On Apr 15, 2008, at 04:18 , mabshoff wrote: >

[sage-devel] Re: Sage 3.0.alpha5 released

On Apr 15, 2008, at 04:18 , mabshoff wrote: > > Hello folks > > here we go with 3.0.alpha5. So, that happened to 3.0.alpha4? It was > never announced in public since it was a snapshot I initially > considered > potentially unstable, but that didn't happen. We have closed a total > of *221* ticket

[sage-devel] Re: Sage 3.0.alpha5 released

All tests passed on my intel mac pro (running 10.4.11). -M. Hampton On Apr 15, 4:04 pm, "William Stein" <[EMAIL PROTECTED]> wrote: > My alpha5 build report: > > (1) arch linux failure when building lapack; this is a known issue involving > fortran. I'll try working around it... yep that gets pas

[sage-devel] Re: Sage 3.0.alpha5 released

My alpha5 build report: (1) arch linux failure when building lapack; this is a known issue involving fortran. I'll try working around it... yep that gets past the lapack issue. (2) 32-bit ubuntu, debian, 64-bit debian; sage.math: 100% good (3) OS X 10.5 ppc: sage -t devel/sage/sage/mod

[sage-devel] Re: Sage 3.0.alpha5 released

Jaap Spies wrote: > mabshoff wrote: >> Hello folks >> >> here we go with 3.0.alpha5. So, that happened to 3.0.alpha4? It was >> never announced in public since it was a snapshot I initially >> considered >> potentially unstable, but that didn't happen. We have closed a total >> of *221* tickets so

[sage-devel] Re: Sage 3.0.alpha5 released

mabshoff wrote: > Hello folks > > here we go with 3.0.alpha5. So, that happened to 3.0.alpha4? It was > never announced in public since it was a snapshot I initially > considered > potentially unstable, but that didn't happen. We have closed a total > of *221* tickets so far. This alpha should bu

[sage-devel] Re: Sage 3.0.alpha5 released

Installed and passed sage -testall on an intel macbook running os 10.4. On Tue, Apr 15, 2008 at 7:18 AM, mabshoff <[EMAIL PROTECTED]> wrote: > > Hello folks > > here we go with 3.0.alpha5. So, that happened to 3.0.alpha4? It was > never announced in public since it was a snapshot I initially >

[sage-devel] Re: Sage 3.0.alpha5 released

All tests pass on 64-bit RHEL (Opteron), and no more segfaults at exit either. Kiran mabshoff wrote: > Hello folks > > here we go with 3.0.alpha5. So, that happened to 3.0.alpha4? It was > never announced in public since it was a snapshot I initially > considered > potentially unstable, but that

[sage-devel] Re: Sage 3.0.alpha3 released

Tom, Confirmed working in 3.0.alpha3. On Apr 9, 10:39 pm, [EMAIL PROTECTED] wrote: > Try alpha3, and ignore my last email. William and I have been re-working > js.py quite a bit. As of alpha2, I think you needed to use ctrl-backspace to > delete a cell. That didn't last long, and backspace

[sage-devel] Re: Sage 3.0.alpha3 released

Alpha 3 issues: On sage.math: The following tests failed: sage -t devel/sage/sage/matrix/matrix_generic_dense.pyx # Segfault sage -t devel/sage/sage/matrix/matrix_mod2_dense.pyx # Segfault sage -t devel/sage/sage/libs/ntl/ntl_GF2.pyx # Segfault sage -t devel/

[sage-devel] Re: Sage 3.0.alpha3 released

Installs fine (ubuntu 7.10 amd64) but has anyone seen something like this: sage -t devel/sage/sage/gsl/gsl_random.pxi [2.3 s] sage -t devel/sage/sage/lfunctions/lcalc.py Aborted (core dumped) A mysterious error (perphaps a memory error?) occurred, which may have crashed doctest.

[sage-devel] Re: Sage 3.0.alpha3 released

I built alpha3 ok but had two bad fails with --testall: The following tests failed: sage -t devel/sage/sage/plot/plot.py # Segfault sage -t devel/sage/sage/interfaces/psage.py # Segfault -- BUT when I re-ran t

[sage-devel] Re: Sage 3.0.alpha3 released

Try alpha3, and ignore my last email. William and I have been re-working js.py quite a bit. As of alpha2, I think you needed to use ctrl-backspace to delete a cell. That didn't last long, and backspace is back in alpha3. Please tell me if you find otherwise. On Wed, 9 Apr 2008, Robert Mil

[sage-devel] Re: Sage 3.0.alpha3 released

On OSX 10.5/Firefox 2, I cannot delete cells in a notebook worksheet as of sage-3.0.alpha2. On Apr 9, 9:48 pm, "Justin C. Walker" <[EMAIL PROTECTED]> wrote: > On Apr 9, 2008, at 12:56 , mabshoff wrote: > > > On Apr 9, 8:40 pm, mabshoff <[EMAIL PROTECTED] > > dortmund.de> wrote: > > Can somebody o

[sage-devel] Re: Sage 3.0.alpha3 released

On Apr 9, 2008, at 12:56 , mabshoff wrote: > On Apr 9, 8:40 pm, mabshoff <[EMAIL PROTECTED] > dortmund.de> wrote: > Can somebody on OSX 10.4 try the spkg at > http://sage.math.washington.edu/home/mabshoff/SPKG/polybori-0.3.1.p0.spkg > You need to first install the updated linbox.spkg at > http:

[sage-devel] Re: Sage 3.0.alpha3 released

Hi, Michael, On Apr 9, 2008, at 12:56 PM, mabshoff wrote: > > On Apr 9, 8:40 pm, mabshoff <[EMAIL PROTECTED] [snip] > > Can somebody on OSX 10.4 try the spkg at > http://sage.math.washington.edu/home/mabshoff/SPKG/ > polybori-0.3.1.p0.spkg > You need to first install the updated linbox.spkg at >

[sage-devel] Re: Sage 3.0.alpha3 released

On Apr 9, 8:40 pm, mabshoff <[EMAIL PROTECTED] dortmund.de> wrote: > In other news: The world hates me. The latest PolyBoRi is borken on > OSX 10.4 - see #2865. It appears that stripping bundles on OSX 10.4 is > a bad thing. Since I wanted debugging support for PolyBoRi anyway I > will look int

[sage-devel] Re: Sage 3.0.alpha3 released

On Apr 9, 8:48 pm, Jaap Spies <[EMAIL PROTECTED]> wrote: > mabshoff wrote: > > On Fedora 7, 32 bits: > > sage -t  devel/doc/prog/prog.tex > >           [3.6 s] > sage -t  devel/doc/const/const.tex > >           [27.6 s] > All tests passed! > Total time for all tests: 4129.4 seconds > [EMAIL PROT

[sage-devel] Re: Sage 3.0.alpha3 released

mabshoff wrote: > Hello folks, > > here is alpha3. Loads of small fixes, a total of 141 tickets > have been closed for the 3.0 milestone so far. > > First the good news: > > The Fortran doctest issue has been fixed by Josh Kantor. > > Now the not so good news: > > Issue: Invalid read in libgr

[sage-devel] Re: Sage 3.0.alpha3 released

On Apr 9, 8:33 pm, Alex Ghitza <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Built fine and all tests passed on Great. > Linux sillyname 2.6.22-gentoo-r5 #2 SMP Tue Aug 28 23:46:12 UTC 2007 > i686 Intel(R) Core(TM)2 CPU 6400 @ 2.13GHz GenuineIntel GNU/Linux >

[sage-devel] Re: Sage 3.0.alpha3 released

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Built fine and all tests passed on Linux sillyname 2.6.22-gentoo-r5 #2 SMP Tue Aug 28 23:46:12 UTC 2007 i686 Intel(R) Core(TM)2 CPU 6400 @ 2.13GHz GenuineIntel GNU/Linux Best, Alex mabshoff wrote: | Hello folks, | | here is alpha3. Loads of smal

[sage-devel] Re: Sage 3.0.alpha2 released

Build report: on this machine: Linux host-57-71 2.6.18.8-0.3-default #1 SMP Tue Apr 17 08:42:35 UTC 2007 x86_64 x86_64 x86_64 GNU/Linux with gcc version 4.1.2 20061115 (prerelease) (SUSE Linux) it builds fine and testall passes except for these: sage -t devel/sage/sage/dsage/tests/test

[sage-devel] Re: Sage 3.0.alpha2 released

On Apr 7, 9:31 pm, "Justin C. Walker" <[EMAIL PROTECTED]> wrote: > On Apr 6, 2008, at 22:29 , mabshoff wrote: > > > > > Hello folks, > > > this is Sage 3.0.alpha2. Up to now we closed 111 tickets. But > > things are still of alpha quality: > > Sources and binaries are in the usual place: > > >ht

[sage-devel] Re: Sage 3.0.alpha2 released

On Apr 6, 2008, at 22:29 , mabshoff wrote: > > Hello folks, > > this is Sage 3.0.alpha2. Up to now we closed 111 tickets. But > things are still of alpha quality: > Sources and binaries are in the usual place: > > http://sage.math.washington.edu/home/mabshoff/release-cycles-3.0/sage-3.0.alpha2.t

[sage-devel] Re: Sage 3.0.alpha2 released

The following tests failed: sage -t devel/sage/sage/functions/piecewise.py sage -t devel/sage/sage/dsage/tests/testdoc.py sage -t devel/sage/sage/combinat/cartan_matrix.py sage -t devel/sage/sage/matrix/action.pyx sage -t devel/sage/sage/categories/ca

[sage-devel] Re: Sage 3.0.alpha2 released

Installed fine on ubuntu 7.10 amd64. My machine hangs randomly (and non-reproducibly) during a sage -testall, apparently only when it encounters maxima. I have to ctl-c and restart. However, so far I did get this: sage -t devel/sage/sage/functions/piecewise.py ***

[sage-devel] Re: Sage 3.0.alpha2 released

On Apr 7, 5:13 pm, Jaap Spies <[EMAIL PROTECTED]> wrote: > mabshoff wrote: > > Hello folks, > > > this is Sage 3.0.alpha2. Up to now we closed 111 tickets. But > > things are still of alpha quality: Hi Jaap, > On Fedora 7, 32 bits: > > sage -t  devel/sage/sage/coding/sd_codes.py              

[sage-devel] Re: Sage 3.0.alpha2 released

mabshoff wrote: > Hello folks, > > this is Sage 3.0.alpha2. Up to now we closed 111 tickets. But > things are still of alpha quality: > On Fedora 7, 32 bits: sage -t devel/sage/sage/coding/sd_codes.py sh: line 1: 10820 Aborted /home/jaap/downloads/sage-3.0.alp

[sage-devel] Re: Sage 3.0.alpha1 released

On Apr 6, 12:06 am, "Justin C. Walker" <[EMAIL PROTECTED]> wrote: > On Apr 4, 2008, at 17:35 , mabshoff wrote: > > > Hello folks, > > > here is Sage 3.0.alpha1. The bad news upfront: The gcc 4.3 > > compiler support didn't make it since the updated Singular > > SPKG is delayed due to some bugs.

[sage-devel] Re: Sage 3.0.alpha1 released

On Apr 4, 2008, at 17:35 , mabshoff wrote: > > Hello folks, > > here is Sage 3.0.alpha1. The bad news upfront: The gcc 4.3 > compiler support didn't make it since the updated Singular > SPKG is delayed due to some bugs. Martin Albrecht is working > on it, so hopefully it will be in alpha2. We mer

[sage-devel] Re: Sage 3.0.alpha1 released

On Sat, Apr 5, 2008 at 8:51 AM, mabshoff <[EMAIL PROTECTED]> wrote: > > > > > On Apr 5, 5:43 pm, "David Joyner" <[EMAIL PROTECTED]> wrote: > > I got a compilation error on a macbook with OS10.4. However, it was > > trying to compile a > > version loaded on a firewire external drive, which may

[sage-devel] Re: Sage 3.0.alpha1 released

On Apr 5, 7:18 pm, mabshoff <[EMAIL PROTECTED] dortmund.de> wrote: > On Apr 5, 6:23 pm, Jaap Spies <[EMAIL PROTECTED]> wrote: > > Hi Jaap, > > >          sage -t  devel/sage/sage/misc/inline_fortran.py > > Total time for all tests: 4476.2 seconds > > tee: /test.log: Permission denied > > grep:

[sage-devel] Re: Sage 3.0.alpha1 released

On Apr 5, 6:23 pm, Jaap Spies <[EMAIL PROTECTED]> wrote: > mabshoff wrote: > > Hello folks, > > > here is Sage 3.0.alpha1. The bad news upfront: The gcc 4.3 > > compiler support didn't make it since the updated Singular > > SPKG is delayed due to some bugs. Martin Albrecht is working > > on it,

[sage-devel] Re: Sage 3.0.alpha1 released

mabshoff wrote: > Hello folks, > > here is Sage 3.0.alpha1. The bad news upfront: The gcc 4.3 > compiler support didn't make it since the updated Singular > SPKG is delayed due to some bugs. Martin Albrecht is working > on it, so hopefully it will be in alpha2. We merged a massive > number of tic

[sage-devel] Re: Sage 3.0.alpha1 released

On Apr 5, 5:43 pm, "David Joyner" <[EMAIL PROTECTED]> wrote: > I got a compilation error on a macbook with OS10.4. However, it was > trying to compile a > version loaded on a firewire external drive, which may be the issue. > Anyway, the problem was with linbox and here is the tail: > > ld: mult

[sage-devel] Re: Sage 3.0.alpha1 released

I got a compilation error on a macbook with OS10.4. However, it was trying to compile a version loaded on a firewire external drive, which may be the issue. Anyway, the problem was with linbox and here is the tail: ld: multiple definitions of symbol __ZN6LinBox11commentatorE .libs/linbox_wrap.o d

[sage-devel] Re: Sage 3.0.alpha1 released

On Apr 5, 3:52 pm, "John Cremona" <[EMAIL PROTECTED]> wrote: Hi John, > I only had two test failures after a successful build: > >         sage -t  devel/sage/sage/misc/prandom.py >         sage -t  devel/sage/sage/misc/inline_fortran.py > > In detail: > > sage -t  devel/sage/sage/misc/prandom.p

[sage-devel] Re: Sage 3.0.alpha1 released

I only had two test failures after a successful build: sage -t devel/sage/sage/misc/prandom.py sage -t devel/sage/sage/misc/inline_fortran.py In detail: sage -t devel/sage/sage/misc/prandom.py ** File "/home/

[sage-devel] Re: Sage 3.0.alpha1 released

On Apr 5, 2:35 am, mabshoff <[EMAIL PROTECTED] dortmund.de> wrote: > Hello folks, > > here is Sage 3.0.alpha1. The bad news upfront: The gcc 4.3 > compiler support didn't make it since the updated Singular > SPKG is delayed due to some bugs. Martin Albrecht is working > on it, so hopefully it wi

[sage-devel] Re: Sage 3.0.alpha0 released

mabshoff wrote: > Hello folks, > > the Sage 3.0 release cycle has started. So far we have merged > > * the new Crystal code > * PolyBoRi 0.3.1 > * plenty of Debian build fixes > > Alpha1 is planned for the next 36 hours and should finally make > compilation with gcc 4.3 possible. > > The so

[sage-devel] Re: Sage 3.0.alpha0 released

On Wed, Apr 2, 2008 at 6:45 AM, mabshoff <[EMAIL PROTECTED]> wrote: > > > > On Apr 2, 3:32 pm, "William Stein" <[EMAIL PROTECTED]> wrote: > > > > On Wed, Apr 2, 2008 at 6:17 AM, Alex Ghitza <[EMAIL PROTECTED]> wrote: > > > > > -BEGIN PGP SIGNED MESSAGE- > > > Hash: SHA1 > > > > >

[sage-devel] Re: Sage 3.0.alpha0 released

On Apr 2, 3:32 pm, "William Stein" <[EMAIL PROTECTED]> wrote: > On Wed, Apr 2, 2008 at 6:17 AM, Alex Ghitza <[EMAIL PROTECTED]> wrote: > > >  -BEGIN PGP SIGNED MESSAGE- > >  Hash: SHA1 > > >  Builds and tests without problems on 32-bit machine running Gentoo. > > * Works on sage.math. >

[sage-devel] Re: Sage 3.0.alpha0 released

On Wed, Apr 2, 2008 at 6:17 AM, Alex Ghitza <[EMAIL PROTECTED]> wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Builds and tests without problems on 32-bit machine running Gentoo. > * Works on sage.math. * integer.pyx fails on meccah (32-bit athlon): sage -t devel/sage-main/s

[sage-devel] Re: Sage 3.0.alpha0 released

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Builds and tests without problems on 32-bit machine running Gentoo. Alex mabshoff wrote: | Hello folks, | | the Sage 3.0 release cycle has started. So far we have merged | | * the new Crystal code | * PolyBoRi 0.3.1 | * plenty of Debian build f

[sage-devel] Re: sage-3.0

Hi On Fri, Mar 07, 2008 at 08:29:33AM -0800, William Stein wrote: > Hi Sage-Devel: > The main goals for Sage-3.0 are: > The target date is April 5, 2008. Awesome, great work, good luck, and thanks to all the devs! Jan -- .~. /V\ Jan Groenewald /( )\www.aims.ac.za ^^-^^ --~-

  1   2   >