On Mon, May 19, 2008 at 7:53 PM, William Stein <[EMAIL PROTECTED]> wrote:
Hi,
>
> On Mon, May 19, 2008 at 10:47 AM, Lon Hutchison <[EMAIL PROTECTED]> wrote:
> > Hello,
> > Sorry, but for the life of me I can't find where the system requirements
> are
> > for SAGE 3.0.1 binary for Mac OS X... ple
On Mon, May 19, 2008 at 10:47 AM, Lon Hutchison <[EMAIL PROTECTED]> wrote:
> Hello,
> Sorry, but for the life of me I can't find where the system requirements are
> for SAGE 3.0.1 binary for Mac OS X... please advise!
>
>
At least 512MB RAM, 1GB hard drive space (probably less, but...),
and OS X
On Wed, May 7, 2008 at 5:19 PM, Franco Saliola <[EMAIL PROTECTED]> wrote:
>
> Hello.
>
>
> On Tue, May 6, 2008 at 6:17 PM, mabshoff <[EMAIL PROTECTED]> wrote:
> > Hhhm:
> >
> > gcc version 4.0.1 (Apple Computer, Inc. build 5341)
> >
>
Hello.
On Tue, May 6, 2008 at 6:17 PM, mabshoff <[EMAIL PROTECTED]> wrote:
> Hhhm:
>
> gcc version 4.0.1 (Apple Computer, Inc. build 5341)
>
...
> That gcc isn't on the black list yet. Can you try updating to a newer
> XCode and try again?
On May 7, 12:03 am, "Franco Saliola" <[EMAIL PROTECTED]> wrote:
> Me again. Different machine, same OS, different error.
>
> Compilation failed with the message:
>
> sage: An error occurred while installing lapack-20071123.p0
Hhhm:
gcc version 4.0.1 (Apple Computer, Inc. build 5341)
*
On Tue, May 6, 2008 at 6:06 PM, mabshoff <[EMAIL PROTECTED]> wrote:
> Your gcc is way too old and know buggy:
Ah, the problem is that these machines haven't been updated in a
while. (I'm trying to compile on machines in a computer lab.)
> > I'm attaching the install.log.
>
> Please don't do
On May 6, 11:59 pm, "Franco Saliola" <[EMAIL PROTECTED]> wrote:
> Not sure if this has been reported.
Hi Franco,
> Compilation failed with the message:
>
> sage: An error occurred while installing ntl-5.4.2.p2
Your gcc is way too old and know buggy:
G_LLL_QP.c: In function `long int NTL::G_B
2008/5/5 Robert Bradshaw <[EMAIL PROTECTED]>:
>
>
> On May 5, 2008, at 12:07 PM, John Cremona wrote:
> >
> > 2008/5/5 Robert Bradshaw <[EMAIL PROTECTED]>:
> >>
> >> On May 5, 2008, at 8:32 AM, John Cremona wrote:
> >>
> >>> I took a quick look at Ondrej's detailed changelog, and was
> >>>
On May 5, 2008, at 12:07 PM, John Cremona wrote:
>
> 2008/5/5 Robert Bradshaw <[EMAIL PROTECTED]>:
>>
>> On May 5, 2008, at 8:32 AM, John Cremona wrote:
>>
>>> I took a quick look at Ondrej's detailed changelog, and was
>>> interested
>>> to see that major speedups had been made by technical-lo
2008/5/5 Robert Bradshaw <[EMAIL PROTECTED]>:
>
>
> On May 5, 2008, at 8:32 AM, John Cremona wrote:
>
> > I took a quick look at Ondrej's detailed changelog, and was interested
> > to see that major speedups had been made by technical-looking changes
> > to __eq__ and __ne__ functions.
> >
>
On May 5, 2008, at 8:32 AM, John Cremona wrote:
> I took a quick look at Ondrej's detailed changelog, and was interested
> to see that major speedups had been made by technical-looking changes
> to __eq__ and __ne__ functions.
>
> When I was testing the generic groups code for Sage a month or two
I took a quick look at Ondrej's detailed changelog, and was interested
to see that major speedups had been made by technical-looking changes
to __eq__ and __ne__ functions.
When I was testing the generic groups code for Sage a month or two
ago, using the profiler, I was concerned to see what a la
On Mon, May 5, 2008 at 3:46 PM, mabshoff <[EMAIL PROTECTED]> wrote:
>
> On May 5, 3:41 pm, "Ondrej Certik" <[EMAIL PROTECTED]> wrote:
>
>
> Hi,
>
>> That would indeed be useful. Maybe even links to the respective commits? :)
>>
>> At least I like to browse how each major feature was implemented,
On May 5, 3:41 pm, "Ondrej Certik" <[EMAIL PROTECTED]> wrote:
Hi,
> That would indeed be useful. Maybe even links to the respective commits? :)
>
> At least I like to browse how each major feature was implemented, for
> learning purposes. In SymPy, we do this:
>
> http://code.google.com/p/sympy
On Mon, May 5, 2008 at 2:03 PM, Michael Abshoff <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> we are listing major features for Sage 3.0.1 at
>
> http://wiki.sagemath.org/sage-3.0.1
>
> Currently we would like you to add some text, i.e. a couple sentences,
> describing what is new/changed/improved so t
On May 4, 5:11 am, elflapper <[EMAIL PROTECTED]> wrote:
> 512 mb
> I think these are relevant part I forgot to post.
> Exception exceptions.TypeError: TypeError(RuntimeError('Unable to
> start maxima b
> ecause the command \'maxima -p "/mnt/documents/sage-3.0.1.rc0/local/
> bin/sage-max
> ima
512 mb
I think these are relevant part I forgot to post.
--copy and paste---
sage -t devel/sage/sage/rings/polynomial/pbori.pyx
**
File "/mnt/documents/sage-3.0.1.rc0/tmp/pbori.py", line 2512:
sage: f(x=var('a'),y=va
On Sat, May 3, 2008 at 7:53 PM, elflapper <[EMAIL PROTECTED]> wrote:
>
> I just ran the test:
> The following tests failed:
>
>
> sage -t devel/sage/sage/rings/polynomial/pbori.pyx
> sage -t devel/sage/sage/rings/complex_double.pyx
> Total time for all tests: 5126.3 seconds
>
I just ran the test:
The following tests failed:
sage -t devel/sage/sage/rings/polynomial/pbori.pyx
sage -t devel/sage/sage/rings/complex_double.pyx
Total time for all tests: 5126.3 seconds
On Archlinux x86
On May 3, 12:17 am, elflapper <[EMAIL PROTECTED]> wrote:
> This build
On Sat, May 3, 2008 at 1:24 PM, Willem Jan Palenstijn <[EMAIL PROTECTED]> wrote:
>
> On Sat, May 03, 2008 at 11:57:00AM -0700, mabshoff wrote:
> > On May 3, 8:44?pm, "William Stein" <[EMAIL PROTECTED]> wrote:
> > > ? ? ? ? sage -t ?devel/sage/sage/rings/ring.pyx
>
> > know issue. Track ticket s
On Sat, May 03, 2008 at 11:57:00AM -0700, mabshoff wrote:
> On May 3, 8:44?pm, "William Stein" <[EMAIL PROTECTED]> wrote:
> > ? ? ? ? sage -t ?devel/sage/sage/rings/ring.pyx
> know issue. Track ticket should be up shortly. Singular related.
This is now #3098.
It is caused by a rather subtle prob
On Sat, May 3, 2008 at 11:57 AM, mabshoff <[EMAIL PROTECTED]> wrote:
>
> On May 3, 8:44 pm, "William Stein" <[EMAIL PROTECTED]> wrote:
> > Build testing of sage-3.0.1.rc0:
>
> Hi,
>
>
> > Powerpc OS X 10.5:
> > sage -t devel/sage/sage/dsage/tests/testdoc.py
> > sage -t deve
On May 3, 8:44 pm, "William Stein" <[EMAIL PROTECTED]> wrote:
> Build testing of sage-3.0.1.rc0:
Hi,
> Powerpc OS X 10.5:
> sage -t devel/sage/sage/dsage/tests/testdoc.py
> sage -t devel/sage/sage/modular/abvar/abvar.py
> sage -t devel/sage/sage/modular/abvar/homspace.
Build testing of sage-3.0.1.rc0:
Powerpc OS X 10.5:
sage -t devel/sage/sage/dsage/tests/testdoc.py
sage -t devel/sage/sage/modular/abvar/abvar.py
sage -t devel/sage/sage/modular/abvar/homspace.py
sage -t devel/sage/sage/server/simple/twist.py
Total time for all
On May 3, 4:18 pm, Alex Ghitza <[EMAIL PROTECTED]> wrote:
> Built fine on
Hi Alex,
> 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
>
> Doing 'make test', got stuck at dsage/tests/testdoc.py so I had to k
On May 3, 7:37 pm, "David Joyner" <[EMAIL PROTECTED]> wrote:
Hi David,
> Sorry. Here it ishttp://sage.math.washington.edu/home/wdj/patches/install.log
> (or will be in a few minutes - it's still uploading).
I think I found it: The working version of mwrank.so is compiled with g
++, while the no
Built fine 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
Doing 'make test', got stuck at dsage/tests/testdoc.py so I had to kill
it. I've put the build log at
http://bayes.colby.edu/~ghitza/inst
On Sat, May 3, 2008 at 1:19 PM, mabshoff <[EMAIL PROTECTED]> wrote:
>
>
>
> On May 3, 7:14 pm, "David Joyner" <[EMAIL PROTECTED]> wrote:
> > On Sat, May 3, 2008 at 12:55 PM, mabshoff <[EMAIL PROTECTED]> wrote:
>
>
>
> Hi David,
>
>
> > > Can you post a link to the build log? This is very li
On May 3, 7:14 pm, "David Joyner" <[EMAIL PROTECTED]> wrote:
> On Sat, May 3, 2008 at 12:55 PM, mabshoff <[EMAIL PROTECTED]> wrote:
Hi David,
> > Can you post a link to the build log? This is very likely related to
> > pbuild's different linker flags. We should be able to hunt this down
>
On Sat, May 3, 2008 at 12:55 PM, mabshoff <[EMAIL PROTECTED]> wrote:
>
> On May 3, 6:33 pm, "David Joyner" <[EMAIL PROTECTED]> wrote:
>
> Hi David,
>
>
> > Possibly strange results on an ubuntu 7.10amd64 machine. (It is a
> > rather old machine
> > though, so many this is not something to wor
On May 3, 6:33 pm, "David Joyner" <[EMAIL PROTECTED]> wrote:
Hi David,
> Possibly strange results on an ubuntu 7.10amd64 machine. (It is a
> rather old machine
> though, so many this is not something to worry about.)
Yes, it is ;)
> export SAGE_PBUILD=yes
> export SAGE_BUILD_THREADS=2
> make
>
Possibly strange results on an ubuntu 7.10amd64 machine. (It is a
rather old machine
though, so many this is not something to worry about.)
export SAGE_PBUILD=yes
export SAGE_BUILD_THREADS=2
make
Build went fine. However, sage -testall started messing up almost immediately.
Here is some of it:
On May 3, 5:26 pm, Andrzej Giniewicz <[EMAIL PROTECTED]> wrote:
> Hi,
Hi Andrzej,
> built and tested on Arch 32, only one failure (were 3 for alpha)...
> same as with 3.0.0:
>
> sage -t 3.0.1.rc0/devel/sage/sage/rings/complex_double.pyx
> **
Hi,
built and tested on Arch 32, only one failure (were 3 for alpha)...
same as with 3.0.0:
sage -t 3.0.1.rc0/devel/sage/sage/rings/complex_double.pyx
**
File "/opt/sage/tmp/complex_double.py", line 1659:
sage: z^2 - z + 1
On May 3, 4:14 pm, "John Cremona" <[EMAIL PROTECTED]> wrote:
Hi John,
> ok , I thought I should have been listening in on IRC when sage-devel
> went quiet!
Yes, #sage-devel is often the place to get quick answers, especially
to debug problems.
> This doesn't actually tell me what I should do.
ok , I thought I should have been listening in on IRC when sage-devel
went quiet!
This doesn't actually tell me what I should do. (You were right that
this is with PBUILD, by the way). But I killed the --testall.
Any ideas on the 8 rogue sage processes I have goung back to April 10?
In full t
On May 3, 3:07 pm, "John Cremona" <[EMAIL PROTECTED]> wrote:
> Two successful builds of rc0 (32 and 64 bit linux). The 64-bit one
> seems to have stalled doing testall at this point:
>
> sage -t devel/sage/sage/dsage/dist_functions/all.py
> [1.3 s]
> sage -t devel/sage/sage/dsage/sc
All ok on my 32-bit machine:
All tests passed!
Total time for all tests: 4034.3 seconds
Please see /home/jec/sage-3.0.1.rc0/tmp/test.log for the complete log
from this test.
[EMAIL PROTECTED] -a
Linux fermat 2.6.22-14-generic #1 SMP Tue Feb 12 07:42:25 UTC 2008
i686 GNU/Linux
2008/5/3 John Crem
All tests passed on my intel mac pro, running OS X 10.4.11.
-M. Hampton
On May 3, 8:07 am, "John Cremona" <[EMAIL PROTECTED]> wrote:
> Two successful builds of rc0 (32 and 64 bit linux). The 64-bit one
> seems to have stalled doing testall at this point:
>
> sage -t devel/sage/sage/dsage/dist
Two successful builds of rc0 (32 and 64 bit linux). The 64-bit one
seems to have stalled doing testall at this point:
sage -t devel/sage/sage/dsage/dist_functions/all.py
[1.3 s]
sage -t devel/sage/sage/dsage/scripts/nodoctest.py (skipping) --
nodoctest.py file in directory
sage -t d
This builds without error on Archlinux (3.0 didn't build with just
'make')!!!
On May 2, 11:43 pm, mabshoff <[EMAIL PROTECTED]> wrote:
> Hello,
>
> This is the end of the 3.0.1 release cycle. The build was announced
> in IRC about eight hours ago, but since I took a long nap in the
> meantime I
On May 3, 1:50 am, Andrzej Giniewicz <[EMAIL PROTECTED]> wrote:
> Hi,
>
> built fine of Arch linux 32 bit without any change, didn't run tests
> yet but will soon...
>
> anyway small off-topic - I was making spkg for R 2.7 and RPy 1.0.2 to
> see if it would work (2.7 have some nice Cairo graphic
Hi,
built fine of Arch linux 32 bit without any change, didn't run tests
yet but will soon...
anyway small off-topic - I was making spkg for R 2.7 and RPy 1.0.2 to
see if it would work (2.7 have some nice Cairo graphics driver in
addition to X11 and others, examples from wiki already works), but
John Cremona wrote:
Hi,
> Thanks for the explanations!
>
> For my own build, I recovered by doing "sage -ba" as previously
> reported. So I don't know whether the original problem (running sage
> for the first time after an apparently successful build) was caused by
> the SAGE_PBUILD thing or no
Thanks for the explanations!
For my own build, I recovered by doing "sage -ba" as previously
reported. So I don't know whether the original problem (running sage
for the first time after an apparently successful build) was caused by
the SAGE_PBUILD thing or not. Before doing "sage -ba" I also d
On May 1, 9:02 pm, "John Cremona" <[EMAIL PROTECTED]> wrote:
Hi John,
> Thanks -- I mistakenly thought "pbuild" was short for "parallel build".
Yes, it is meant to emphasize the parallel nature. Gary builds
routinely with 8 cores on his box and it cuts down the build time in a
linear fashion.
On Thu, May 01, 2008 at 04:12:36AM -0600, Gary Furnish wrote:
>
> If you export SAGE_PBUILD=yes before you run make (so that it uses
> pbuild from the beginning) it is necessary to link site-packages
> yourself with the following command from $SAGE_ROOT:
> ln -s devel/sage/build/sage/ local/lib/p
On an ubuntu 7.10amd64 machine:
The following tests failed:
sage -t devel/sage/sage/server/simple/twist.py
Total time for all tests: 4833.6 seconds
Please see /home/wdj/wdj/sagefiles/sage-3.0.1.alpha1/tmp/test.log for
the complete log from this test.
[EMAIL PROTECTED]:~/wdj/sagefiles/s
Doing "sage -ba" sorted that out. Here is the result of --testall:
The following tests failed:
sage -t devel/sage/sage/server/simple/twist.py
sage -t devel/sage/sage/dsage/tests/testdoc.py
Both passed when rerun separately.
John
Linux host-57-71 2.6.18.8-0.3-default #1 SMP
Thanks -- I mistakenly thought "pbuild" was short for "parallel
build". If it is not about building Sage, while is it called
SAGE_PBUILD?
Anyway, can someone remind me what causes this and how to fix it?
SAGE build/upgrade complete!
[EMAIL PROTECTED]/sage
---
On May 1, 2008, at 11:08 AM, Jaap Spies wrote:
> mabshoff wrote:
>> Hello,
>>
>> this release should have been out two days ago, but somehow
>> general slowness and me spending a lot of time on various
>> porting issues did delay this release more than it should
>> have. Gary's pbuild should now
mabshoff wrote:
> Hello,
>
> this release should have been out two days ago, but somehow
> general slowness and me spending a lot of time on various
> porting issues did delay this release more than it should
> have. Gary's pbuild should now be fully functional, but it
> wasn't made the default b
The symlink is needed only after make completes when you try to run
sage, not to build it.
On Thu, May 1, 2008 at 11:18 AM, John Cremona <[EMAIL PROTECTED]> wrote:
>
> Gary, that does not work!
>
> [EMAIL PROTECTED] SAGE_PBUILD=yes
> [EMAIL PROTECTED] -s devel/sage/build/sage/
> local/lib/pyt
Gary, that does not work!
[EMAIL PROTECTED] SAGE_PBUILD=yes
[EMAIL PROTECTED] -s devel/sage/build/sage/ local/lib/python/site-packages/sage
ln: creating symbolic link `local/lib/python/site-packages/sage': No
such file or directory
This is in a freshly unpacked SAGE_ROOT, which does not yet have
mabshoff wrote:
> Hello,
>
> this release should have been out two days ago, but somehow
> general slowness and me spending a lot of time on various
> porting issues did delay this release more than it should
> have. Gary's pbuild should now be fully functional, but it
> wasn't made the default b
If you export SAGE_PBUILD=yes before you run make (so that it uses
pbuild from the beginning) it is necessary to link site-packages
yourself with the following command from $SAGE_ROOT:
ln -s devel/sage/build/sage/ local/lib/python/site-packages/sage
This will be fixed in rc0.
On Thu, May 1, 2008
mabshoff wrote:
> Hello folks,
>
> this is 3.0.1.alpha0. So far we have only merged bugfixes,
> nothing invasive so far. 24 tickets have been closed so far
> and I am not quite sure what the rest of the release cycle
> will look like because it currently doesn't look like we
> need a pure bug fix
57 matches
Mail list logo
