On Feb 20, 2:34 pm, mark mcclure wrote:
Hi Mark,
> After installing the new spkg, sage compiled, Sage.app built,
> and all but the following three tests passed:
> sage -t "devel/sage/sage/graphs/graph_plot.py"
> sage -t "devel/sage/sage/misc/package.py"
> sage -t "devel/sage/sage/plot/p
After installing the new spkg, sage compiled, Sage.app built,
and all but the following three tests passed:
sage -t "devel/sage/sage/graphs/graph_plot.py"
sage -t "devel/sage/sage/misc/package.py"
sage -t "devel/sage/sage/plot/plot.py"
Mark McClure
--~--~-~--~~~
On Feb 20, 8:22 am, mark mcclure wrote:
> On Feb 20, 9:18 am, mabshoff wrote:
>
> > On Feb 20, 6:08 am, mark mcclure wrote:
> > I screwed up, please try again. The problem is that I created a tar.gz
> > instead of a tar.bzip2.
>
> I had a feeling it was something like this.
Well, it happens
On Feb 20, 9:18 am, mabshoff wrote:
> On Feb 20, 6:08 am, mark mcclure wrote:
> I screwed up, please try again. The problem is that I created a tar.gz
> instead of a tar.bzip2.
I had a feeling it was something like this.
I had a class this morning and have only just started the build.
It is ru
On Feb 20, 6:08 am, mark mcclure wrote:
> On Feb 20, 8:47 am, mabshoff wrote:
> Well, it doesn't look so good right now. I've tried two
> things:
> 1) Before you responded, I simply manually placed the
> spkg in the spkg/standard subdirectory of a freshly
> untarred sage-3.3.rc2 fold
On Feb 20, 8:47 am, mabshoff wrote:
> The spkg needs to be found by Sage. One way is to download it and
> place it into $SAGE_ROOT/spkg/standard, i.e.
>
> cd spkg/standard
> curlhttp://sage.math.washington.edu/home/mabshoff/SPKG/gmp-mpir-0.9.spkg
> -o gmp-mpir-0.9.spkg
>
> then restart the bui
On Feb 20, 5:42 am, mark mcclure wrote:
> On Feb 20, 8:34 am, mabshoff wrote:
>
> > please
> > tryhttp://sage.math.washington.edu/home/mabshoff/SPKG/gmp-mpir-0.9.spkg
> > and report back as soon as possible. I am down to 4 tickets (including
> > this one) for Sage 3.3.rc3 which will likely be
On Feb 20, 8:34 am, mabshoff wrote:
> please tryhttp://sage.math.washington.edu/home/mabshoff/SPKG/gmp-mpir-0.9.spkg
> and report back as soon as possible. I am down to 4 tickets (including
> this one) for Sage 3.3.rc3 which will likely be identical to the final
> 3.3.
I probably should have men
> Hi Michael,
Hi Mark,
> I could definitely do that today.
please try http://sage.math.washington.edu/home/mabshoff/SPKG/gmp-mpir-0.9.spkg
and report back as soon as possible. I am down to 4 tickets (including
this one) for Sage 3.3.rc3 which will likely be identical to the final
3.3.
> Mark
On Feb 20, 12:35 am, mabshoff wrote:
> On Feb 18, 10:41 am, mark mcclure wrote:
>
> > I get an error building GMP on my MacBook Pro running
> > OS X 10.4.11.
>
> Hi Mark,
>
> I haven't gotten to this yet, but I have made this
>
> http://trac.sagemath.org/sage_trac/ticket/5315
>
> If you are
On Feb 18, 10:41 am, mark mcclure wrote:
> On Feb 18, 12:33 pm, mabshoff wrote:
>
> > 3.3.rc2 has been out for a good half day,
>
> I get an error building GMP on my MacBook Pro running
> OS X 10.4.11. The partial log, starting where I think
> things went awry, is below.
>
> It's currently bu
On Feb 19, 11:51 am, Martin Albrecht
wrote:
> > And this BS since it is not running out of memory:
Hi Martin,
> > OK, this is a singular problem for sure. Check this out:
>
> That's only on OSX, right?
Yes.
> I just tried it on my 64-bit Linux box and
> everything is fine. Michael, you
On Feb 19, 11:36 am, William Stein wrote:
> On Thu, Feb 19, 2009 at 1:56 AM, John Cremona wrote:
>
> >> > 3. A segfault on OS X 10.5 32-bit Intel (bsd.math.washington.edu):
> Anyway, John, you don't have to worry about this anymore, since it has
> nothing to do with your code.
>
> Martin Al
> And this BS since it is not running out of memory:
>
> sage: for p in prime_range(390,1):
> if p%13==1: print get_memory_usage()
> v.append(E.change_ring(GF(p)))
> ...
> 139.0
> 139.0
> 139.0
> 140.0
> 141.0
> 141.0
> 141.0
>
> error: no more memory
> System 5120k:5120k Appl 4638k/48
On Thu, Feb 19, 2009 at 1:56 AM, John Cremona wrote:
>
>
>
>
>>
>>
>> > 3. A segfault on OS X 10.5 32-bit Intel (bsd.math.washington.edu):
>>
>> > sage -t -long "devel/sage/sage/schemes/elliptic_curves/ell_finite_field.py"
>> > A mysterious error (perphaps a memory error?) occurred, which may hav
Thanks Georg, my memory is not what it used to be! I just hate to see
this error recurring apparantly in something I wrote
John
On 19 Feb, 11:29, "Georg S. Weber" wrote:
> > Can William or someone who gets this error (I don't!) test what
> > happens if you replace
>
> > G=E.change_ring(GF(
> Can William or someone who gets this error (I don't!) test what
> happens if you replace
>
> G=E.change_ring(GF(p)).abelian_group()
>
> by
>
> N=E.change_ring(GF(p)).cardinality()
>
> ? The cardinality will be provided by pari, so if it is a pari
> problem that should still cause a problem. T
>
>
> > 3. A segfault on OS X 10.5 32-bit Intel (bsd.math.washington.edu):
>
> > sage -t -long "devel/sage/sage/schemes/elliptic_curves/ell_finite_field.py"
> > A mysterious error (perphaps a memory error?) occurred, which may have
> > crashed doctest.
> > [22.7 s]
>
> > Doing this aga
Hi all,
3.3.rc2 built fine on MacIntel Core2Duo Mac OS X 10.4.11 with Xcode
2.5, the only testlong failures were:
The following tests failed:
sage -t -long "devel/sage/sage/graphs/graph_plot.py"
sage -t -long "devel/sage/sage/plot/plot.py"
sage -t -long "devel/sage/sage/
On Feb 18, 2009, at 09:33 , mabshoff wrote:
>
> Hello folks,
>
> 3.3.rc2 has been out for a good half day, but we are only announcing
> it now since I did build it over night on a bunch of machines. Enough
> people were hanging out in IRC to know that it was ready, so we are
> having a good idea
On Feb 18, 3:35 pm, mabshoff wrote:
> Normally you would either run
>
> make test
> or
> make testlong
Yeah, I included that line since I knew there was the possibility I
was doing it wrong. After running 'make test', I get on
"devel/sage/sage/plot/plot.py".
> > Evidently there's still a
mabshoff wrote:
> Ooops, I forgot to mention one very important thing to do, so here
> goes another double post: If you are upgrading make sure to delete
> matplotlibrc from
>
> * $SAGE_ROOT
> * $SAGE_ROOT/tmp
> * $DOT_SAGE
>
> since otherwise you will see a lot of deprecation warnings during
>
> > 3. A segfault on OS X 10.5 32-bit Intel (bsd.math.washington.edu):
>
> > sage -t -long "devel/sage/sage/schemes/elliptic_curves/ell_finite_field.py"
> > A mysterious error (perphaps a memory error?) occurred, which may have
> > crashed doctest.
> > [22.7 s]
>
> > Doing this again w
On Feb 18, 12:28 pm, mark mcclure wrote:
> On Feb 18, 12:33 pm, mabshoff wrote:
Hi Mark,
> > 3.3.rc2 has been out for a good half day,
>
> Build went smoothly on my Intel MacPro running OS X 10.5.5.
> Passed all tests from 'sage -t devel/sage/sage/misc/all.py'.
Mhh, did you just test that f
On Feb 18, 12:33 pm, mabshoff wrote:
> 3.3.rc2 has been out for a good half day,
Build went smoothly on my Intel MacPro running OS X 10.5.5.
Passed all tests from 'sage -t devel/sage/sage/misc/all.py'.
Evidently there's still a little more to building the groovy Sage.app,
though?
Mark McClure
On Feb 18, 11:48 am, mark mcclure wrote:
> On Feb 18, 1:44 pm, mabshoff wrote:
Hi Mark,
> > Ok, I know what went wrong. I assume this is a MacIntel. Can you send
> > me the complete compressed log?
>
> Correct, this is an Intel based Mac. I'll gzip the log and email it
> to you
> shortly.
>
On Feb 18, 1:44 pm, mabshoff wrote:
> Ok, I know what went wrong. I assume this is a MacIntel. Can you send
> me the complete compressed log?
Correct, this is an Intel based Mac. I'll gzip the log and email it
to you
shortly.
Mark McClure
--~--~-~--~~~---~--~~
On Feb 18, 11:16 am, William Stein wrote:
> This is about 3.3.rc2.
>
> 1. On my macbookpro os x 10.5 intel,
> sage -t -long "devel/sage/sage/misc/package.py"
> **
> File "/Users/wstein/build/build/sage-3.3.rc2/devel/sage/sage/
This is about 3.3.rc2.
1. On my macbookpro os x 10.5 intel,
sage -t -long "devel/sage/sage/misc/package.py"
**
File "/Users/wstein/build/build/sage-3.3.rc2/devel/sage/sage/misc/package.py",
line 50:
sage: sage.misc.package.i
On Feb 18, 10:41 am, mark mcclure wrote:
> On Feb 18, 12:33 pm, mabshoff wrote:
Hi Mark,
> > 3.3.rc2 has been out for a good half day,
>
> I get an error building GMP on my MacBook Pro running
> OS X 10.4.11. The partial log, starting where I think
> things went awry, is below.
Ok, I know
On Feb 18, 12:33 pm, mabshoff wrote:
> 3.3.rc2 has been out for a good half day,
I get an error building GMP on my MacBook Pro running
OS X 10.4.11. The partial log, starting where I think
things went awry, is below.
It's currently building on my Mac Pro with OS X 10.5.5
and looks good so far.
Ooops, I forgot to mention one very important thing to do, so here
goes another double post: If you are upgrading make sure to delete
matplotlibrc from
* $SAGE_ROOT
* $SAGE_ROOT/tmp
* $DOT_SAGE
since otherwise you will see a lot of deprecation warnings during
doctesting.
Cheers,
Michael
--~
32 matches
Mail list logo
