Jaap Spies wrote:
> mabshoff wrote:
>>
>> On Mar 26, 10:53 pm, Jaap Spies <[EMAIL PROTECTED]> wrote:
>>> mabshoff wrote:
>>>
Well, maybe I did accidentally nuke more than the .svn directories. I
cannot imagine a scenario where anything would depend on the content
of a .svn directory
mabshoff wrote:
>
>
> On Mar 26, 10:53 pm, Jaap Spies <[EMAIL PROTECTED]> wrote:
>> mabshoff wrote:
>>
>>> Well, maybe I did accidentally nuke more than the .svn directories. I
>>> cannot imagine a scenario where anything would depend on the content
>>> of a .svn directory to run. But I wouldn't
On Mar 26, 10:53 pm, Jaap Spies <[EMAIL PROTECTED]> wrote:
> mabshoff wrote:
>
> > Well, maybe I did accidentally nuke more than the .svn directories. I
> > cannot imagine a scenario where anything would depend on the content
> > of a .svn directory to run. But I wouldn't be surprised to be prov
mabshoff wrote:
>
>
> Well, maybe I did accidentally nuke more than the .svn directories. I
> cannot imagine a scenario where anything would depend on the content
> of a .svn directory to run. But I wouldn't be surprised to be proven
> wrong ;)
>
I did a diff -r on both directories, only .svn
On Mar 26, 10:31 pm, Jaap Spies <[EMAIL PROTECTED]> wrote:
> mabshoff wrote:
> > Hi folks,
>
> > Sage 2.11.alpha1 is out. It is a collection of various
> > fixes, nothing particular seems to stand out. We finally
> > pushed the updated experimental mayavi and vtl.spkg.
>
> [...]
> > #2493: Jaap
mabshoff wrote:
> Hi folks,
>
> Sage 2.11.alpha1 is out. It is a collection of various
> fixes, nothing particular seems to stand out. We finally
> pushed the updated experimental mayavi and vtl.spkg.
>
[...]
> #2493: Jaap Spies: Updated experimental vtk spkg
>(vtk-5.0.4.spkg)
> #2495: J
On Mar 26, 2008, at 11:07 , William Stein wrote:
>
> On Wed, Mar 26, 2008 at 11:05 AM, Justin C. Walker <[EMAIL PROTECTED]>
> wrote:
>>
>>
>> On Mar 26, 2008, at 10:37 , William Stein wrote:
>>>
>>> On Wed, Mar 26, 2008 at 9:15 AM, mabshoff
>>> <[EMAIL PROTECTED]> wrote:
>> [snip]
>>
Yeah,
On Wed, Mar 26, 2008 at 11:05 AM, Justin C. Walker <[EMAIL PROTECTED]> wrote:
>
>
> On Mar 26, 2008, at 10:37 , William Stein wrote:
> >
> > On Wed, Mar 26, 2008 at 9:15 AM, mabshoff
> > <[EMAIL PROTECTED]> wrote:
> [snip]
>
> >> Yeah, but that mean that any Sage release that is supposed to w
On Mar 26, 2008, at 10:37 , William Stein wrote:
>
> On Wed, Mar 26, 2008 at 9:15 AM, mabshoff
> <[EMAIL PROTECTED]> wrote:
[snip]
>> Yeah, but that mean that any Sage release that is supposed to work
>> will so far only work up to 10.5.1. I didn't know that the tiny
>> version number of OSX can
On Wed, Mar 26, 2008 at 9:15 AM, mabshoff
<[EMAIL PROTECTED]> wrote:
>
>
>
> On Mar 26, 4:43 pm, "Justin C. Walker" <[EMAIL PROTECTED]> wrote:
> > On Mar 26, 2008, at 24:27 , mabshoff wrote:
> >
> >
>
> > > Ok, this is the culprit. It will need fixes all over the place and
> > > this time we
On Mar 26, 5:53 pm, "Justin C. Walker" <[EMAIL PROTECTED]> wrote:
> On Mar 26, 2008, at 09:15 , mabshoff wrote:
>
>
>
> > On Mar 26, 4:43 pm, "Justin C. Walker" <[EMAIL PROTECTED]> wrote:
> >> On Mar 26, 2008, at 24:27 , mabshoff wrote:
> [snip]
> >>> Yeah, the culprit is the above regexp. I wil
On Mar 26, 2008, at 09:15 , mabshoff wrote:
>
> On Mar 26, 4:43 pm, "Justin C. Walker" <[EMAIL PROTECTED]> wrote:
>> On Mar 26, 2008, at 24:27 , mabshoff wrote:
[snip]
>>> Yeah, the culprit is the above regexp. I will fix those before
>>> 2.11.alpha2. Sorry for the mess. I made this #2672 - a blo
On Mar 26, 4:43 pm, "Justin C. Walker" <[EMAIL PROTECTED]> wrote:
> On Mar 26, 2008, at 24:27 , mabshoff wrote:
>
>
> > Ok, this is the culprit. It will need fixes all over the place and
> > this time we might as well do it right.
>
> Oh, what the heck. Do it wrong for a couple of more times :-
On Mar 26, 2008, at 24:27 , mabshoff wrote:
>
> On Mar 26, 5:45 am, "Justin C. Walker" <[EMAIL PROTECTED]> wrote:
>>
>> On Mar 25, 2008, at 19:16 , mabshoff wrote:
[snip]
>>> more GMP trouble. Can you post the output from "uname -r | sed s/9\.
>>> [0-9]\.0/9\.0\.0/" and a "uname -a".
>>
>> $ unam
It started working after I installed atlas system wide. Atlas was not
installed in the first attempt to compile sage. After linbox failed, my
solution was to install atlas through gentoo package manager and try again.
Cheers,
Soroosh
On Wed, Mar 26, 2008 at 3:36 AM, mabshoff <
[EMAIL PROTECTED]>
On Mar 26, 3:25 am, "Soroosh Yazdani" <[EMAIL PROTECTED]> wrote:
> Should I uninstall atlas if I want to check your patch for the future
> version? Atlas is installed system wide on my computer, and linbox seemed to
> have found those libraries as it compiled afterward. Is there a way to force
>
On Mar 26, 5:45 am, "Justin C. Walker" <[EMAIL PROTECTED]> wrote:
> Hi, Hichael,
>
> On Mar 25, 2008, at 19:16 , mabshoff wrote:
>
>
>
>
>
> > On Mar 26, 2:58 am, "Justin C. Walker" <[EMAIL PROTECTED]> wrote:
> >> On Mar 22, 2008, at 16:02 , mabshoff wrote:
> >>>http://sage.math.washington.edu/h
Hi, Hichael,
On Mar 25, 2008, at 19:16 , mabshoff wrote:
>
> On Mar 26, 2:58 am, "Justin C. Walker" <[EMAIL PROTECTED]> wrote:
>> On Mar 22, 2008, at 16:02 , mabshoff wrote:
>>> http://sage.math.washington.edu/home/mabshoff/release-cycles-2.11/sag
>>> ...
>>
>> Things didn't go so well on my sys
Should I uninstall atlas if I want to check your patch for the future
version? Atlas is installed system wide on my computer, and linbox seemed to
have found those libraries as it compiled afterward. Is there a way to force
linbox to compile against the local version?
Cheers,
Soroosh
On Tue, Mar
On Mar 26, 2:58 am, "Justin C. Walker" <[EMAIL PROTECTED]> wrote:
> On Mar 22, 2008, at 16:02 , mabshoff wrote:
>
>
>
> > Hi folks,
>
> > Sage 2.11.alpha1 is out. It is a collection of various
> > fixes, nothing particular seems to stand out. We finally
> > pushed the updated experimental mayavi
On Mar 22, 2008, at 16:02 , mabshoff wrote:
>
> Hi folks,
>
> Sage 2.11.alpha1 is out. It is a collection of various
> fixes, nothing particular seems to stand out. We finally
> pushed the updated experimental mayavi and vtl.spkg.
>
> We still have the doctest failure in plot.py. I do not
> quite
On Mar 25, 9:42 pm, "Soroosh Yazdani" <[EMAIL PROTECTED]> wrote:
> Hi,
>
> compiling fails for me on linbox. Apparently it can't find blas libraries.
> My computer is an hp laptop, with amd 64x2 processor, running gentoo. I have
> acml installed on my computer, although looking at install.log it
Hi,
compiling fails for me on linbox. Apparently it can't find blas libraries.
My computer is an hp laptop, with amd 64x2 processor, running gentoo. I have
acml installed on my computer, although looking at install.log it seems like
sage is compiling atlas libraries as well, so I'm not sure if tha
That one is a known issue.
On Mon, Mar 24, 2008 at 2:55 PM, David Joyner <[EMAIL PROTECTED]> wrote:
>
> On Mon, Mar 24, 2008 at 12:38 PM, mabshoff
>
> <[EMAIL PROTECTED]> wrote:
> >
>
>
> > Hi David,
> >
> >
> > > "Rerunning sage -t" yields all tests pass. I was reporting "sage -tp".
> >
On Mon, Mar 24, 2008 at 12:38 PM, mabshoff
<[EMAIL PROTECTED]> wrote:
>
> Hi David,
>
>
> > "Rerunning sage -t" yields all tests pass. I was reporting "sage -tp".
>
> I know ;)
>
>
>
> > Here is
> > a copy+paste from the terminal history:
> >
> > sage -t 1/devel/sage/sage/misc/preparser.p
On Mar 24, 7:32 pm, "Bill Furnish" <[EMAIL PROTECTED]> wrote:
> Could it be a Maxima pexpect issue?
I doubt it since there was only one thread running. The interesting
question is whether it is reproducible.
Cheers,
Michael
--~--~-~--~~~---~--~~
To post to this
Could it be a Maxima pexpect issue?
On Mon, Mar 24, 2008 at 10:38 AM, mabshoff
<[EMAIL PROTECTED]> wrote:
>
> Hi David,
>
>
> > "Rerunning sage -t" yields all tests pass. I was reporting "sage -tp".
>
> I know ;)
>
>
>
> > Here is
> > a copy+paste from the terminal history:
> >
> > sage -
Hi David,
> "Rerunning sage -t" yields all tests pass. I was reporting "sage -tp".
I know ;)
> Here is
> a copy+paste from the terminal history:
>
> sage -t 1/devel/sage/sage/misc/preparser.py
> **
> File "preparser.py", line
On Mon, Mar 24, 2008 at 8:50 AM, mabshoff
<[EMAIL PROTECTED]> wrote:
>
>
>
> On Mar 24, 1:13 pm, "David Joyner" <[EMAIL PROTECTED]> wrote:
> > Ubuntu 7.10, amd64:
> > ./sage -tp 1 devel/sage/sage
> > gave
> > The following tests failed:
> >
> > sage -t 1/devel/sage/sage/plot/plot.p
On Mar 24, 1:13 pm, "David Joyner" <[EMAIL PROTECTED]> wrote:
> Ubuntu 7.10, amd64:
> ./sage -tp 1 devel/sage/sage
> gave
> The following tests failed:
>
> sage -t 1/devel/sage/sage/plot/plot.py: 1 doctests failed
Hi David,
> sage -t 1/devel/sage/sage/calculus/calculus.py: 5
Ubuntu 7.10, amd64:
./sage -tp 1 devel/sage/sage
gave
The following tests failed:
sage -t 1/devel/sage/sage/plot/plot.py: 1 doctests failed
sage -t 1/devel/sage/sage/calculus/calculus.py: 5 doctests failed
sage -t 1/devel/sage/sage/misc/preparser.py: 1 doctests failed
-
On Mar 24, 3:18 am, Alex Ghitza <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On a Dual Core machine running Gentoo, I've tried
>
> ./sage -tp 1 devel/sage/sage
>
> and
>
> ./sage -tp 2 devel/sage/sage
>
> Both appeared to run fine; the first used only one core
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On a Dual Core machine running Gentoo, I've tried
./sage -tp 1 devel/sage/sage
and
./sage -tp 2 devel/sage/sage
Both appeared to run fine; the first used only one core and the second
used both. Running times: 1878 seconds for one core and 1031 s
On Mar 23, 9:54 pm, "William Stein" <[EMAIL PROTECTED]> wrote:
> On Sun, Mar 23, 2008 at 1:03 PM, mabshoff
>
> I put logs from all tests here:
>
> http://sage.math.washington.edu/home/was/build/tests/2.11.alpha1/
Thanks, meccah's unusual failures are due to timeouts, some corrupted
GAP workspa
On Sun, Mar 23, 2008 at 1:03 PM, mabshoff
<[EMAIL PROTECTED]> wrote:
>
>
>
> On Mar 23, 8:43 pm, "William Stein" <[EMAIL PROTECTED]> wrote:
> > On Sun, Mar 23, 2008 at 12:38 PM, mabshoff
> >
> >
> >
>
> > <[EMAIL PROTECTED]> wrote:
> >
> > > On Mar 23, 4:09 pm, "Bill Furnish" <[EMAIL PROTE
35 matches
Mail list logo
