A minor typo in the Constructions documentation. The
Constructions documentation says to send corrections
to sage-devel.
# HG changeset patch
# User Mariah Lenox
# Date 1253652415 14400
# Node ID bd65499b09ca9c88108908a609648850433dda8a
# Parent 40fe66e6c2b07677706fd983a6be6f3eb86060c5
user
in a sage subshell.
# ./sage -sh
Starting subshell with Sage environment variables set.
Be sure to exit when you are done and do not do anything
with other copies of Sage!
Bypassing shell configuration files ...
/home/mariah/sage/sage-4.1.1-x86_64-Linux-core2-fc
sage subshell$ echo hi
hi
/home/m
Minh,
The patch may have been merged into sage-4.1.2.
But it is NOT in sage-4.2.1.
Just do (in sage-4.2.1) "./sage -sh".
I expect to see (at the end)
*****
/home/mariah/sage/sage-4.2.1-x86_64-Linux-core2-fc
sage subshell$
*
Yet what I see is just
*
Bypassing shell configura
echo "Unknown shell: $SHELL!"
echo "Exiting Sage."
exit 1
esac
$SHELL_NAME $SHELL_OPTS "$@"
echo Exited Sage subshell.
exit $?
fi
This does NOT have the patch applied.
Have I found a bug in the sage distribution process?
Mar
not working for
me, but
working for everyone else!
I am seriously confused. Apologies for being so dense.
I will investigate.
Mariah
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel-unsubscr...@googlegroups.com
For m
Volker,
I am trying to understand what goes wrong by having the build compiler
in a non-standard place. (I am the sys admin for the particular
build machine in question.) Can you give me an example of
what Sage command or sequence of commands fails?
Mariah
On Jan 26, 7:43 am, Volker Braun
es?
Sorry to be dense. I am just not grasping how you want
to use Sage.
Mariah
On Jan 26, 12:44 pm, Volker Braun wrote:
> Hi Mariah,
>
> The problem is that no program can dlink the (C++-using) libraries.
> All existing spkgs apparently link statically which works but suffers
>
say that Sage binaries
are just for running Sage commands. If you want
to do development work, you should build from source
(in which case Sage will find where the compiler
libraries are on your particular machine).
If I have things wrong, I hope someone will
enlighten me!
Mariah
On Jan 26, 2
ceptable, let me know and
I will change the inputs.
The primary purpose of the Skynet machines is for Sage research.
However I have a responsibility to the people who paid for these
machines (the US taxpayers) to not have the machines sitting around
idle. I hope you understand.
Mariah
--
To po
memory is the minimum
requirement to test Sage?
Mariah
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
Would a kind person explain to me (or point me at documentation that
explains) what the following two spkgs contain and are supposed to do:
examples-4.4.3.spkg
extcode-4.4.3.spkg
(I am trying to get a better understanding of Sage by looking at
each of the spkgs.)
Mariah
--
To post to this
David,
I just finished building sage-4.4.4.1 as a regular user (not root)
on many of the Skynet Linux machines.
I do not see the error message that you are reporting.
Perhaps this is a problem only on Solaris machines?
Mariah
On Jun 28, 5:50 pm, "Dr. David Kirkby"
wrote:
> I
Kwankyu,
This is now trac #9377.
sage-support is a better place to report bugs.
sage-devel is for discussions about development.
Mariah
On Jun 28, 10:45 pm, Kwankyu Lee wrote:
> Hi,
>
> On Sage 4.4.4, I have the following bug.
>
> sage: F.=GF(4)
> sage: m=matrix(2,[F
Thanks! I needed something simple to learn how
to review. Someone tell me if I did anything wrong.
Mariah
On Jul 1, 8:52 am, David Kirkby wrote:
> If someone wants an easy patch to review,
>
> http://trac.sagemath.org/sage_trac/ticket/9399
>
> should come pretty easy. Currentl
This is now trac #12580.
Mariah
On Feb 22, 4:46 pm, William Stein wrote:
> Hi Sage-Devel,
>
> I was very surprised by this just now:
>
> sage: import random
> sage: random.randint(0,20)
> 0
> sage: set_random_seed(0)
> sage: random.randint(0,20)
> 0
>
This is now trac ticket #10981.
On Mar 21, 12:46 pm, Pierre wrote:
> noone really? shall I create a ticket?
>
> can anyone reproduce that bug?
>
> On 18 mar, 12:14, Pierre wrote:
>
> > sage: x= AA['x'].gen()
> > sage: P= 1/(1+x^4)
> > sage: P.partial_fraction_decomposition()
> > ...
> > ...
> >
0.16 secs, Magma: 1.45 secs
200 x 201 -- Sage: 0.35 secs, Magma: 3.44 secs
250 x 251 -- Sage: 0.54 secs, Magma: 8.26 secs
---
Mariah Lenox
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegrou
This is now ticket #11421.
On Jun 1, 10:47 am, John Cremona wrote:
> FYI
>
> John
>
> -- Forwarded message --
> From: NAKAMULA, Ken
> Date: Wed, Jun 1, 2011 at 3:13 PM
> Subject: relaese of NZMATH version 1.1
> To: nmbrt...@listserv.nodak.edu
>
> Dear number theorists,
>
> We are
/local/gcc-4.6.1/x86-Linux-pentium4-fc/bin/gfortran
buildbot@cicero ~$
Mariah Lenox
Skynet sytem administrator
On Aug 1, 7:42 am, Jeroen Demeyer wrote:
> To the sysadmin of the buildbot machine "cicero":
>
> It seems that gcc and g++ have recently been upgraded to version 4.6.
rrent directory?
If so, I will have another think about this. If not, would
a kind person please check in the patch.
Mariah
--- sage-sage.old 2009-09-25 10:52:08.278703000 -0400
+++ sage-sage.new 2009-09-25 15:11:21.214214000 -0400
@@ -374,41 +374,37 @@
echo "with other copie
Sage Developers,
trac # 4644 has a patch that I wrote to deal with
several problems with 'sage -sh'. It is listed
as fixed in 4.2.
Yet sage-4.2.1 does not seem to have the patch.
Did I miss a discussion about this issue that caused
my patch to be reverted?
--
Mariah
--
To po
I believe ticket #8700 (needs_review defect)
can be closed. It has a milestone of 4.4.4
and a patched spkg
libpng-1.2.35.p1.spkg
but libpng-1.2.35.p1.spkg is already
in 4.4.3 (and the problem mentioned in #8700
is fixed).
Can someone with the proper authority please
close #8700.
Mariah
I believe ticket #5238 can be closed.
Ticket #5238 (remove qsieve.spkg and replace it by mpQS (part of FLINT))
should be closed because qsieve.spkg is no longer part of standard.
Would someone with the proper authority please
close #5238.
Mariah
--
To post to this group, send an email to sage
trac #2048 while humorous could be closed
Mariah
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL
to put them both at
the same level with a note about the dependency
in the deps file?
Mariah
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http
Would whomever has access to the skynet buildbot please
clean up the files it is generating?
Disk space on skynet is at a dangerous 97% full. The
buildbot seems to be the biggest disk hog:
2007 101G
2008 104G
2009 136G
Mariah Lenox
skynet system administrator
--
To post to
It looks like the bottom of
http://wiki.sagemath.org/devel/UsefulSoftware
has been spammed.
Mariah
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this
27 matches
Mail list logo
