Dr David Kirkby wrote:
>
>
> On Jun 5, 8:48 am, Dan Drake wrote:
>> Note that right now, building Sage fails on that machine with an
>> internal compiler error -- the Fortran compiler fails. There's a partial
>> build in /scratch/drake if you want to see an install log.
>>
>> Dan
>>
>> --
>> -
Sourav recently experienced this same problem on sage.math -- I
figured it was because the sage build failed, but now I'm thinking
that a bug may have been introduced when dsage was moved into a spkg.
On Fri, Jun 5, 2009 at 11:54 AM, William Stein wrote:
>
> 2009/6/5 Dr David Kirkby :
>>
>>
>>
>>
2009/6/5 Dr David Kirkby :
>
>
>
> On Jun 5, 8:48 am, Dan Drake wrote:
>> On Fri, Jun 5 2009 12:37 am, William Stein wrote:
>> > Have you got an account on t2.math.washington.edu yet? If so, it
>> > would be *extremely* useful if you could build Sage there (I haven't
>> > yet!), since then I cou
On Jun 5, 8:48 am, Dan Drake wrote:
> On Fri, Jun 5 2009 12:37 am, William Stein wrote:
> > Have you got an account on t2.math.washington.edu yet? If so, it
> > would be *extremely* useful if you could build Sage there (I haven't
> > yet!), since then I could directly debug this notebook probl
2009/6/5 Dr. David Kirkby :
>
> Dan Drake wrote:
>> On Fri, Jun 5 2009 12:37 am, William Stein wrote:
>>> Have you got an account on t2.math.washington.edu yet? If so, it
>>> would be *extremely* useful if you could build Sage there (I haven't
>>> yet!), since then I could directly debug this not
William Stein wrote:
> On Fri, Jun 5, 2009 at 12:48 AM, Dan Drake wrote:
>> On Fri, Jun 5 2009 12:37 am, William Stein wrote:
>>> Have you got an account on t2.math.washington.edu yet? If so, it
>>> would be *extremely* useful if you could build Sage there (I haven't
>>> yet!), since then I coul
Dan Drake wrote:
> On Fri, Jun 5 2009 12:37 am, William Stein wrote:
>> Have you got an account on t2.math.washington.edu yet? If so, it
>> would be *extremely* useful if you could build Sage there (I haven't
>> yet!), since then I could directly debug this notebook problem.
>
> Note that right
On Fri, Jun 5, 2009 at 12:48 AM, Dan Drake wrote:
> On Fri, Jun 5 2009 12:37 am, William Stein wrote:
>> Have you got an account on t2.math.washington.edu yet? If so, it
>> would be *extremely* useful if you could build Sage there (I haven't
>> yet!), since then I could directly debug this noteb
On Fri, Jun 5 2009 12:37 am, William Stein wrote:
> Have you got an account on t2.math.washington.edu yet? If so, it
> would be *extremely* useful if you could build Sage there (I haven't
> yet!), since then I could directly debug this notebook problem.
Note that right now, building Sage fails on
On Thu, Jun 4, 2009 at 10:27 AM, Jason Grout
wrote:
>
> William Stein wrote:
>> 2009/6/4 Dr. David Kirkby :
>>> FWIW,
>>>
>>> sage-4.0.1.alpha0 compiled without any hickups on my Blade 2000 running
>>> Solaris 10 update 6.
>>
>> Did you run the test suite? I also built from scratch
>> sage-4.0.
William Stein wrote:
> 2009/6/4 Dr. David Kirkby :
>> FWIW,
>>
>> sage-4.0.1.alpha0 compiled without any hickups on my Blade 2000 running
>> Solaris 10 update 6.
>
> Did you run the test suite? I also built from scratch
> sage-4.0.1.alpha0 on a Blade 2000 (I think), and 5 file didn't pass
> the
> FWIW,
>
> sage-4.0.1.alpha0 compiled without any hickups on my Blade 2000 running
> Solaris 10 update 6.
William Stein wrote:
> 2009/6/4 Dr. David Kirkby :
>> FWIW,
>>
>> sage-4.0.1.alpha0 compiled without any hickups on my Blade 2000 running
>> Solaris 10 update 6.
>
> Did you run the test
2009/6/4 Dr. David Kirkby :
>
> FWIW,
>
> sage-4.0.1.alpha0 compiled without any hickups on my Blade 2000 running
> Solaris 10 update 6.
Did you run the test suite? I also built from scratch
sage-4.0.1.alpha0 on a Blade 2000 (I think), and 5 file didn't pass
the suite for me. 3 were due to ti
Dr. David Kirkby wrote:
>
> Again, like any version of Sage I've tried (including the binary Micheal
> compiled), the GUI interface, with
>
> 'notebook()'
>
> will not work for me. I'm unable to find any server listening on port
> 8.
I was checking port 8000 - the 8 is a typo.
--~--
14 matches
Mail list logo
