On Tue, Feb 23, 2010 at 5:03 PM, Nick Alexander wrote:
>> $ git grep Sage
>
> I think that "git grep sage" (really, case insensitive) is probably
> necessary too, since we have changed cases many times.
The capitalization "SAGE" was also used previously before the switch to "Sage".
--
Regards
M
$ git grep Sage
I think that "git grep sage" (really, case insensitive) is probably
necessary too, since we have changed cases many times.
Nick
--
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...@goo
Hi,
some FEMhub users are confused by seeing the name "Sage" in
warnings and error messages, and in various installation scripts
and messages. They are there because FEMhub uses some
functionality of Sage (as Ubuntu uses some functionality of
Debian). However, the word "Debian" does not appear in
On Mon, Feb 22, 2010 at 7:10 PM, Dima Pasechnik wrote:
> Dave,
> Is it possible to install screen on t2?
> Even if I run screen on boxen and ssh to t2, the connection is still a
> bit flaky.
I just put a screen executable in /scratch/mhansen/bin that you can use.
--Mike
--
To post to this grou
Dave,
Is it possible to install screen on t2?
Even if I run screen on boxen and ssh to t2, the connection is still a
bit flaky.
Thanks,
Dima
On Feb 22, 7:52 pm, "Dr. David Kirkby"
wrote:
> I've just added a note to
>
> http://wiki.sagemath.org/devel/Building-Sage-on-the-T5240-t2
>
> which might
On Mon, 22 Feb 2010 14:50:09 -0800 (PST), zieglerk
wrote:
> Alex's tip was correct.
Glad to hear it worked for you.
> After installing the package gcc-c++ everything compiled smoothly.
> The problem was, that with OpenSUSE installing the package gcc (as
> mentioned on http://www.sagemath.org/do
zieglerk wrote:
Alex's tip was correct.
After installing the package gcc-c++ everything compiled smoothly.
The problem was, that with OpenSUSE installing the package gcc (as
mentioned on http://www.sagemath.org/doc/installation/source.html)
does not automatically install gcc-c++, too. (This is
Alex's tip was correct.
After installing the package gcc-c++ everything compiled smoothly.
The problem was, that with OpenSUSE installing the package gcc (as
mentioned on http://www.sagemath.org/doc/installation/source.html)
does not automatically install gcc-c++, too. (This is possibly
trivial f
Bill Hart wrote:
Actually, this is really silly. The must be a multitude of packages
for Solaris which are distributed with binaries and which need these
libraries. How do they deal with this issue?
Is there a package installation system like apt-get or yum or rpm on
Solaris? They must surely de
Any comments from Robert Miller?
John
On 22 February 2010 19:39, Robert Bradshaw wrote:
> On Feb 21, 2010, at 12:53 PM, Dr. David Kirkby wrote:
>
>> The addition of
>>
>> http://trac.sagemath.org/sage_trac/ticket/6583 (implement 2-isogeny
>> descent over QQ natively in Sage using ratpoints)
>>
>
Actually, this is really silly. The must be a multitude of packages
for Solaris which are distributed with binaries and which need these
libraries. How do they deal with this issue?
Is there a package installation system like apt-get or yum or rpm on
Solaris? They must surely deal with this issue
-1 from me to including these libraries.
Q1. Are there any other well-known packages which do this? If not, it
is not a standard thing to do, probably for good reason.
Cython uses the C compiler (if I understand correctly). I think this
kills the idea dead.
Q2. Would building Sage with the Sun C
On 22 Feb, 13:09, "Dr. David Kirkby" wrote:
> Bill Hart wrote:
> > I don't understand the syntax here:
>
> > export LD_LIBRARY_PATH=/usr/local/gcc-4.4.1-sun-linker/lib:=/usr/local/
> > gcc-4.4.1-sun-linker/lib/sparcv9:/usr/local/lib
>
> > Why is there an extra := in the middle of that?
>
> A typ
This is a yasm issue (yasm is a prereq for MPIR and is included in the
tarball).
I haven't ever seen yasm not build on an Opteron before.
Can you download MPIR 1.3.1 from http://www.mpir.org/ and verify it
builds on your machine outside of the Sage context.
Is there anything else potentially unu
On 22 Feb., 12:27, "Dr. David Kirkby" wrote:
> This came up on the thread "mercurial on t2" but I thought I'd start a new
> thread on it.
>
> I'd propose that we include in any binary distribution gcc's C, C++ and
> Fortran
> shared libraries. They would be placed in $SAGE_LOCAL/lib. Then we ca
Robert Bradshaw wrote:
On Feb 21, 2010, at 12:53 PM, Dr. David Kirkby wrote:
The addition of
http://trac.sagemath.org/sage_trac/ticket/6583 (implement 2-isogeny
descent over QQ natively in Sage using ratpoints)
sage-4.3.1 broke the build of Sage on Solaris. I suspect this was the
ticket, b
On Feb 21, 2010, at 12:53 PM, Dr. David Kirkby wrote:
The addition of
http://trac.sagemath.org/sage_trac/ticket/6583 (implement 2-isogeny
descent over QQ natively in Sage using ratpoints)
sage-4.3.1 broke the build of Sage on Solaris. I suspect this was
the ticket, but Minh had proved thi
On Feb 21, 2010, at 3:26 PM, David Roe wrote:
Currently mod and Mod are the same function. I think that this
should remain true, if only for backward compatibility.
There seem to be plenty of ways to construct elements of Z/nZ
quickly. I would say that the only thing in question is what t
Harald Schilly wrote:
On Feb 22, 1:12 pm, "Dr. David Kirkby"
wrote:
http://www.sagemath.org/doc/tutorial/interfaces.html
says:
"Maxima is included with Sage, as is clisp (a version of the Lisp language)."
that should be a trac ticket, component "documentation". I suggest to
replace it more
On Feb 22, 2010, at 4:01 AM, Martin Raum wrote:
Hi all,
I just reviewed #8276 based on the discussion in
http://groups.google.com/group/sage-devel/browse_frm/thread/1042edd11b3854b2
.
For me a great problem arises with this change, though the majority
voted for it. I think about it as follows.
On Feb 22, 2010, at 3:27 AM, Dr. David Kirkby wrote:
This came up on the thread "mercurial on t2" but I thought I'd start
a new thread on it.
I'd propose that we include in any binary distribution gcc's C, C++
and Fortran shared libraries. They would be placed in $SAGE_LOCAL/
lib. Then we
On Feb 22, 1:49 pm, Willem Jan Palenstijn wrote:
> This text describes RedHat's policy on libgcc_s and
> libstdc++:http://kbase.redhat.com/faq/docs/DOC-8313
> It seems to suggest that if we want to include libstdc++ or libgcc_s, we
> should
> include both.
Well it literally says:
"Both libgcc
Ooops! Too many group algebras lying around. Just ignore my previous
post.
Sorry for the noise.
Cheers
J
--
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
I've cleaned and retried this a few times but without any luck. I'm
happy to provide more detailed information or try a debug session over
IRC. Any help is greatly appreciated.
Thanks!
$ uname -a
Linux myhostname 2.6.29-2 #1 SMP Tue May 19 12:56:32 EDT 2009 x86_64
x86_64 x86_64 GNU/Linux
$ cat
Hi all,
I am getting some weird errors doing computations with groups
algebras. Here is an example:
I create an element of the group algebra:
sage: G = SymmetricGroup(3)
sage: A = GroupAlgebra(G, QQ)
sage: c = sum(1/x.order()*A(x) for x in G)
sage: c
() + 1/2*(2,3) + 1/2*(1,2) + 1/3*(1,2,3) + 1/
Dima Pasechnik wrote:
Dave,
The libraries are OK to include--- I was under impression is that you
propose to include basically the whole toolchain...
Sorry for a misunderstanding.
Dima
No, that was not my intension.
But I think William has given serious consideration to including the whole of
On Feb 22, 7:16 pm, "Dr. David Kirkby"
wrote:
> Dima Pasechnik wrote:
> > On t2, can we please follow he Skynet's /usr/local/skynet_bash_profile
> > mechanism to have a ready setup for building sage there?
>
> We do. The message was in /etc/motd, but I've made it clearer.
Thanks.
The motd was n
Dave,
The libraries are OK to include--- I was under impression is that you
propose to include basically the whole toolchain...
Sorry for a misunderstanding.
Dima
On Feb 22, 6:41 pm, "Dr. David Kirkby"
wrote:
> Dima Pasechnik wrote:
>
> > On Feb 22, 4:15 am, "Dr. David Kirkby"
> > wrote:
> > [.
Hi,
Typesetting conjugates of variables (that has been passed to
Maxima and back?) is strange. In e.g. Sage 4.2 this did not
happen.
--
| Sage Version 4.3.3, Release Date: 2010-02-21 |
| Type notebook() for
On Feb 22, 5:30 am, Minh Nguyen wrote:
> Sage 4.3.3 was released ...
I just finished compiling on my core duo /w ubuntu 9.04 and got some
doctest failures:
http://boxen.math.washington.edu/home/schilly/sage/sage-4.3.3-ubuntu9.04-intel_core_duo-doctest-failures.txt
h
--
To post to this group,
Harald Schilly writes:
> On Feb 22, 1:12 pm, "Dr. David Kirkby"
> wrote:
>> http://www.sagemath.org/doc/tutorial/interfaces.html
>> says:
>>
>> "Maxima is included with Sage, as is clisp (a version of the Lisp language)."
>>
>
> that should be a trac ticket, component "documentation". I suggest
Volker Braun wrote:
If you want to go that route you probably want to include glibc
(contains standard math library) as well.
While a viable possibility,
there are two obvious arguments against it:
On Feb 22, 11:27 am, "Dr. David Kirkby"
wrote:
* Always have the libraries.
Instead, che
On Mon, Feb 22, 2010 at 11:27:40AM +, Dr. David Kirkby wrote:
> This came up on the thread "mercurial on t2" but I thought I'd start a
> new thread on it.
>
> I'd propose that we include in any binary distribution gcc's C, C++ and
> Fortran shared libraries. They would be placed in $SAGE_LOCA
Bill Hart wrote:
On 22 Feb, 11:27, "Dr. David Kirkby" wrote:
This came up on the thread "mercurial on t2" but I thought I'd start a new
thread on it.
I'd propose that we include in any binary distribution gcc's C, C++ and Fortran
shared libraries. They would be placed in $SAGE_LOCAL/lib. Then
If you want to go that route you probably want to include glibc
(contains standard math library) as well. While a viable possibility,
there are two obvious arguments against it:
On Feb 22, 11:27 am, "Dr. David Kirkby"
wrote:
> * Always have the libraries.
Instead, check on first startup that a
Its a good thing that we already make available binaries for those
people with less Linux experience
Whatever we can do to make Sage "work out of the box" is good
(i.e. I know its 99% there but it will be even better if we can avoid
asking people to ensure certain things are installed and are certa
Bill Hart wrote:
I don't understand the syntax here:
export LD_LIBRARY_PATH=/usr/local/gcc-4.4.1-sun-linker/lib:=/usr/local/
gcc-4.4.1-sun-linker/lib/sparcv9:/usr/local/lib
Why is there an extra := in the middle of that?
A typo. Fortunately one which had not caused any harm, but I will correc
I don't understand the syntax here:
export LD_LIBRARY_PATH=/usr/local/gcc-4.4.1-sun-linker/lib:=/usr/local/
gcc-4.4.1-sun-linker/lib/sparcv9:/usr/local/lib
Why is there an extra := in the middle of that?
Also, why the extra dot at the start of:
. /usr/local/gcc-4.4.1-sun-linker/gcc441sun
W
Are we sure this would work? Won't those libraries depend on what
kernel is installed, etc, etc?
I'm completely ignorant on this, so may be talk out my proverbial.
Bill.
On 22 Feb, 11:27, "Dr. David Kirkby" wrote:
> This came up on the thread "mercurial on t2" but I thought I'd start a new
> th
On Feb 22, 1:12 pm, "Dr. David Kirkby"
wrote:
> http://www.sagemath.org/doc/tutorial/interfaces.html
> says:
>
> "Maxima is included with Sage, as is clisp (a version of the Lisp language)."
>
that should be a trac ticket, component "documentation". I suggest to
replace it more general with "to
http://www.sagemath.org/doc/tutorial/interfaces.html
says:
"Maxima is included with Sage, as is clisp (a version of the Lisp language)."
Dave
--
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...@googlegro
Hi all,
I just reviewed #8276 based on the discussion in
http://groups.google.com/group/sage-devel/browse_frm/thread/1042edd11b3854b2
.
For me a great problem arises with this change, though the majority
voted for it. I think about it as follows.
The categories framework has introduced a function
I've just added a note to
http://wiki.sagemath.org/devel/Building-Sage-on-the-T5240-t2
which might make setting up a build environment on 't2' simpler.
Just add this to the end of your $HOME/.profile
if [ `uname -n` = t2 ] ; then
. /usr/local/gcc-4.4.1-sun-linker/gcc441sun
fi
It will set P
This came up on the thread "mercurial on t2" but I thought I'd start a new
thread on it.
I'd propose that we include in any binary distribution gcc's C, C++ and Fortran
shared libraries. They would be placed in $SAGE_LOCAL/lib. Then we can ensure
that people will run Sage with what libraries S
Dima Pasechnik wrote:
On t2, can we please follow he Skynet's /usr/local/skynet_bash_profile
mechanism to have a ready setup for building sage there?
We do. The message was in /etc/motd, but I've made it clearer.
Add this to your .profile:
if [ `uname -n` = t2 ] ; then
. /usr/local/gcc-4.4
Dima Pasechnik wrote:
On Feb 22, 4:15 am, "Dr. David Kirkby"
wrote:
[...]
I think once again, it shows that gcc's C, C++ and Fortran libraries should all
be included with Sage. Otherwise, the build relies on the end user having a
similar setup. This is not specific to Solaris, but one can prob
Hi Dima,
On Mon, Feb 22, 2010 at 8:10 PM, Dima Pasechnik wrote:
> Could you please fix this?
Done.
--
Regards
Minh Van Nguyen
--
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
Hi Minh,
http://trac.sagemath.org/sage_trac/ticket/8076
requires database_gap to be bumped up to
http://boxen.math.washington.edu/home/dima/packages/database_gap-4.4.12.spkg
But http://www.sagemath.org/packages/optional/
only has http://www.sagemath.org/packages/optional/database_gap-4.4.10.spkg
48 matches
Mail list logo
