Hi guys,
Thanks for the insights. I knew that trying to define the generators
in my original way was asking for trouble, but it's good to learn
why. Right now, I just did the simple thing (which I should have done
from the start):
class DifferentialForms(Algebra):
def __init__(..., coordinat
On May 23, 2010, at 6:10 PM, Dr. David Kirkby wrote:
> Trying to build Sage on OpenSolaris in 64-bit mode I discovered two packages
> which look to me that they don't try to build 64-bit. They don't use the
> SAGE64 variable at all and nothing else there suggests that the -m64 flag
> ever gets
Trying to build Sage on OpenSolaris in 64-bit mode I discovered two packages
which look to me that they don't try to build 64-bit. They don't use the SAGE64
variable at all and nothing else there suggests that the -m64 flag ever gets added.
This makes me think that they will not build properly
>
> Besides the usual suspects (who I hope are interested as well, you
> know who you are!), Mike O'Sullivan and his students at San Diego
> State might also be interested.
>
> Rob
Yes, indeed, we are very interested. Our primary interest is
classroom use, rather
than research. Some of the of th
On 24 Mai, 01:18, Tim Daly wrote:
> how about using:
>
> find . -name "*.pyx" -exec touch {} \;
We can save one more character:
find . -name \*.pyx -exec touch {} \;
-Leif
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
s
how about using:
find . -name "*.pyx" -exec touch {} \;
William A. Stein wrote:
On May 23, 2010, at 1:12 PM, leif wrote:
On 23 Mai, 21:40, "Dr. David Kirkby" wrote:
'lcalc' had a particularly annoying attempt to cover up warnings from the
assembler, as it actually caused the build
> I've tried to create a 64-bit version of Sage on OpenSolaris, but some
> files are building as 32-bit. Does anyone know what package(s) these are
> part of?
>
> local/bin/class.x:
> local/bin/cws.x:
> local/bin/dikcube:
> local/bin/nef.x:
> local/bin/poly.x:
> local/bin/QuadraticSieve:
> local/b
I've tried to create a 64-bit version of Sage on OpenSolaris, but some files are
building as 32-bit. Does anyone know what package(s) these are part of?
local/bin/class.x:
local/bin/cws.x:
local/bin/dikcube:
local/bin/nef.x:
local/bin/poly.x:
local/bin/QuadraticSieve:
local/bin/size222:
local/l
On 23 Mai, 22:47, "Dr. David Kirkby" wrote:
> >> Host system
> >> uname -a:
> >> SunOS hawk 5.11 snv_134 i86pc i386 i86pc
>
> > uname -m == i386 is bad for a 64-bit machine...
>
> uname -m does not give i386.
>
> drkir...@hawk:~/sage-4.4.2$ uname -m
> i86pc
> drkir...@hawk:~/sage-4.4.2$ uname -p
>
I found this page:
http://sites.google.com/site/easylinuxtipsproject/java#TOC-Install-JRE-32-bit-
to be quite useful. jmol now works on all my machines (running Ubuntu
10.04)
-Bruce
On May 12, 9:07 pm, Bruce Cohen wrote:
> I have just tried jmol on two machines running 32 bitUbuntu10.04.
> At
On 23 Mai, 22:41, "Dr. David Kirkby" wrote:
> On 05/23/10 09:16 PM, William A. Stein wrote:
> > Instead of keeping this as a favorite, implement a better version, and post
> > a patch.
Work in progress. (But things depend on reviewing/merging other
tickets, too.
> I'm not going to hunt down the
On 05/23/10 09:40 PM, leif wrote:
On 23 Mai, 22:03, "Dr. David Kirkby" wrote:
gcc is being called without the -m64 option when building 'gdmodule' on
OpenSolaris, despite SAGE64 being set to "yes".
But I've no idea how to go about changing this behavior. There seems to be no
code which does an
On 05/23/10 09:16 PM, William A. Stein wrote:
On May 23, 2010, at 1:12 PM, leif wrote:
On 23 Mai, 21:40, "Dr. David Kirkby" wrote:
'lcalc' had a particularly annoying attempt to cover up warnings from the
assembler, as it actually caused the build to break on Solaris, as the option to
cover
On 23 Mai, 22:03, "Dr. David Kirkby" wrote:
> gcc is being called without the -m64 option when building 'gdmodule' on
> OpenSolaris, despite SAGE64 being set to "yes".
>
> But I've no idea how to go about changing this behavior. There seems to be no
> code which does anything special on OS X for 6
On May 23, 2010, at 1:12 PM, leif wrote:
> On 23 Mai, 21:40, "Dr. David Kirkby" wrote:
>> 'lcalc' had a particularly annoying attempt to cover up warnings from the
>> assembler, as it actually caused the build to break on Solaris, as the
>> option to
>> cover up the warnings was passed directly
On May 23, 2010, at 1:12 PM, leif wrote:
> On 23 Mai, 21:40, "Dr. David Kirkby" wrote:
>> 'lcalc' had a particularly annoying attempt to cover up warnings from the
>> assembler, as it actually caused the build to break on Solaris, as the
>> option to
>> cover up the warnings was passed directly
On 23 Mai, 21:40, "Dr. David Kirkby" wrote:
> 'lcalc' had a particularly annoying attempt to cover up warnings from the
> assembler, as it actually caused the build to break on Solaris, as the option
> to
> cover up the warnings was passed directly to the Sun assembler, but it did not
> accept th
gcc is being called without the -m64 option when building 'gdmodule' on
OpenSolaris, despite SAGE64 being set to "yes".
But I've no idea how to go about changing this behavior. There seems to be no
code which does anything special on OS X for 64-bit builds.
I've raised this as bug:
http://tr
On 05/23/10 04:18 PM, leif wrote:
The more evil thing is that currently *all* warnings in the
compilation of C/C++ Sage library files are suppressed by a *trailing*
"-w", so nobody will see any warning unless he/she edits setup.py
Unfortunately, this is all too common in many components of Sag
On 05/23/10 04:52 PM, Minh Nguyen wrote:
Hi David,
On Mon, May 24, 2010 at 12:50 AM, Dr. David Kirkby
wrote:
If someone has a minute or two.
http://trac.sagemath.org/sage_trac/ticket/9009
The changes look harmless enough. But I wanted to test building that
updated spkg as 64-bit. It hardly
On 23 Mai, 15:30, geep999 wrote:
> Anyway, all 2.1 Gb of Sage is now built, documentation created and
> notebook seems OK with Firefox.
Fine.
If you find the time, you could try running "./sage -testall", "./sage
-testall -long" or e.g. "make testlong"/"make ptestlong" (the latter
runs tests in
Hi David,
On Mon, May 24, 2010 at 12:50 AM, Dr. David Kirkby
wrote:
> If someone has a minute or two.
>
> http://trac.sagemath.org/sage_trac/ticket/9009
The changes look harmless enough. But I wanted to test building that
updated spkg as 64-bit. It hardly ever occurred to me to build Sage as
64-
On 23 Mai, 14:29, "Dr. David Kirkby" wrote:
> On 05/23/10 01:27 PM, Dr. David Kirkby wrote:
>
> > *Both* -ansi and -pedantic should be used for the best conformance to
> > standards, though it will not be perfect. But I doubt the Sage library
> > would build with those. If Cython could generate co
If someone has a minute or two.
http://trac.sagemath.org/sage_trac/ticket/9009
needs review. The only change it the removal of
if [ `uname` = "Darwin" -a "$SAGE64" = "yes" ]; then
echo "64 bit MacIntel"
to
if [ "x$SAGE64" = xyes ]; then
echo "Compiling Mercurial as 64-bit"
which ensure
On 05/23/10 02:30 PM, geep999 wrote:
Mea culpa.
I hadn't got into the Sage way of doing things and didn't realize that
the build would be alongside the Sage source tree created from
sage-4.4.2.tar. Maybe README.txt should mention this. Or it's
somewhere and I haven't noticed it.
I don't feel RE
Mea culpa.
I hadn't got into the Sage way of doing things and didn't realize that
the build would be alongside the Sage source tree created from
sage-4.4.2.tar. Maybe README.txt should mention this. Or it's
somewhere and I haven't noticed it.
For some reason I thought it was going to build under $
On 05/23/10 01:27 PM, Dr. David Kirkby wrote:
*Both* -ansi and -pedantic should be used for the best conformance to
standards, though it will not be perfect. But I doubt the Sage library
would build with those. If Cython could generate code that works with
those options, there is some hope the l
On 05/22/10 01:59 PM, Nathan O'Treally wrote:
On 22 Mai, 13:17, "Dr. David Kirkby" wrote:
On 05/22/10 03:24 AM, Nathan O'Treally wrote:
On 21 Mai, 19:42, Robert Bradshaw
wrote:
Please let us know if you run into *any* examples of this--our goal is
to always produce standard compliant C89 or C
Hi folks,
On Sun, May 23, 2010 at 5:02 PM, Minh Nguyen wrote:
> Hi folks,
>
> I'm getting a report on IRC that wiki.sagemath.org is returning an IOError:
>
> [Errno 28] No space left on device
>
> On the virtual machine sagemath, the root partition is 100% full.
Harald Schilly has resolved this
On May 23, 12:50 am, Robert Bradshaw
wrote:
> That's almost certainly testing your system Python.
>
> Try the above using the python inside $SAGE_ROOT/local/bin and see if
> it gives anything different. The interesting part will be the
> traceback it gives (or not).
>
> - Robert
>
It was usin
Hi folks,
I'm getting a report on IRC that wiki.sagemath.org is returning an IOError:
[Errno 28] No space left on device
On the virtual machine sagemath, the root partition is 100% full.
--
Regards
Minh Van Nguyen
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsu
On 23 Mai, 08:15, Rob Beezer wrote:
> Based on some limited testing - just editing the text version of a
> worksheet - would indicate that jsMath does not want to deal with
> \newline or \\ to break lines. With no better idea, I was able to use
> HTML paragraph tags to get two chunks of text on d
32 matches
Mail list logo
