Le 21/05/2013 21:57, William Stein a écrit :
Sage is by default built with any GUI support.
Is there a non-default and easy way to get a working
matplotlib-on-bare-python?
Snark on #sagemath
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To
Hi
That is a wrapper around gcc I use a lot. It has never caused problems
before.
In this case, unsetting it the build seems to continue.
Regards,
Jan
On 21 May 2013 22:00, leif wrote:
> leif wrote:
>
>> Jan Groenewald wrote:
>>
>>> And the whole output from make:
>>>
>>> 0 jan@kontiki:~/src
leif wrote:
leif wrote:
ghm...@mst.edu wrote:
p11 and p10 both fail to resolve the problem. dpkg-dev installed and
fully updated.
Use the .p11, which works for me (Ubuntu 12.04.2 x86_64, Ubuntu GCC
4.6.3), and was supposed to fix exactly that issue.
Prior to that, install OpenSSL: sudo apt
leif wrote:
ghm...@mst.edu wrote:
p11 and p10 both fail to resolve the problem. dpkg-dev installed and
fully updated.
Use the .p11, which works for me (Ubuntu 12.04.2 x86_64, Ubuntu GCC
4.6.3), and was supposed to fix exactly that issue.
Prior to that, install OpenSSL: sudo apt-get install
ghm...@mst.edu wrote:
p11 and p10 both fail to resolve the problem. dpkg-dev installed and
fully updated.
Use the .p11, which works for me (Ubuntu 12.04.2 x86_64, Ubuntu GCC
4.6.3), and was supposed to fix exactly that issue.
Prior to that, install OpenSSL: sudo apt-get install libssl-dev
Do you have libcrypto installed on the system at all. I think it would
trigger this particular module build to fail.
It is a bit of a shot in the dark I'll admit.
Francois
On Tue, 21 May 2013 15:57:58 ghm...@mst.edu wrote:
> p11 and p10 both fail to resolve the problem. dpkg-dev installed and f
p11 and p10 both fail to resolve the problem. dpkg-dev installed and fully
updated.
Thank you for the suggestion though!
On Tuesday, May 21, 2013 2:44:29 PM UTC-5, leif wrote:
>
> kcrisman wrote:
> > On May 21, 1:57 pm, ghm...@mst.edu wrote:
> >> Just checking in, I replaced the python instal
leif wrote:
Jan Groenewald wrote:
And the whole output from make:
0 jan@kontiki:~/src/sage-5.9$make
cd spkg && \
"../spkg/pipestatus" \
"env SAGE_PARALLEL_SPKG_BUILD='' ./install all 2>&1" \
"tee -a ../logs/install.log"
/home/jan/src/sage-5.9/spkg/bin/testcc.sh: 134:
/hom
Sage is by default built with any GUI support.
On May 21, 2013 12:52 PM, "Julien Puydt" wrote:
> Hi,
>
> the following lines of python:
> from pylab import *
> xs = range(20)
> ys = [x*x for x in xs]
> plot(xs,ys)
> show()
>
> have a different outcome depending on where I type them:
>
> - at the
Hi,
the following lines of python:
from pylab import *
xs = range(20)
ys = [x*x for x in xs]
plot(xs,ys)
show()
have a different outcome depending on where I type them:
- at the system python's prompt (just run 'python' then type them), I
get a window with the expected graph ;
- at sage's py
Hi Sage Devel,
Some group is doing a case study on software projects for the NSF,
including Sage.
They interviewed me over the phone for a few minutes and came up with
a two-page document
about Sage.
https://docs.google.com/file/d/0B_106LC6joGYVUowQ1gtVy1SRGs/edit?usp=sharing
Just looking at
kcrisman wrote:
On May 21, 1:57 pm, ghm...@mst.edu wrote:
Just checking in, I replaced the python install retrieved by Sage with the
downloaded Python spkg, with no change in error message. Any other ideas?
I'm not sure what you mean by this. What you'd have to do is remove
the python-x.y.z
Jan Groenewald wrote:
And the whole output from make:
0 jan@kontiki:~/src/sage-5.9$make
cd spkg && \
"../spkg/pipestatus" \
"env SAGE_PARALLEL_SPKG_BUILD='' ./install all 2>&1" \
"tee -a ../logs/install.log"
/home/jan/src/sage-5.9/spkg/bin/testcc.sh: 134:
/home/jan/src/sag
On May 21, 1:57 pm, ghm...@mst.edu wrote:
> Just checking in, I replaced the python install retrieved by Sage with the
> downloaded Python spkg, with no change in error message. Any other ideas?
>
I'm not sure what you mean by this. What you'd have to do is remove
the python-x.y.z.spkg in spkg
Just checking in, I replaced the python install retrieved by Sage with the
downloaded Python spkg, with no change in error message. Any other ideas?
Thank you!
On Tuesday, May 21, 2013 12:24:39 PM UTC-5, kcrisman wrote:
>
>
>
> On May 21, 12:45 pm, ghm...@mst.edu wrote:
> > You say "relatively
On May 21, 12:45 pm, ghm...@mst.edu wrote:
> You say "relatively trivial" and I feel increasingly unintelligent. I
Sorry, I meant relatively trivial for someone who knows how spkgs work
- I was thinking someone might cook one up.
Try replacing your spkg with
http://boxen.math.washington.edu/h
You say "relatively trivial" and I feel increasingly unintelligent. I
downloaded the python-2.6.4.p10, extracted it, and copied it in place of
the p9 that was in the sage spkg directory, with no change in results.
Is this the proper procedure or does something else needed to be modified?
Agai
I think I mentioned this on a previous thread, but I was searching for
the unescaped regular expression "..." which matches a whole bunch of
things :). Whence http://trac.sagemath.org/sage_trac/ticket/14622
On Tue, May 21, 2013 at 4:19 AM, Simon King wrote:
> Hi!
>
> I am wondering about the beha
Thats me testing the newest patchbot spkg... Ignore these plugin failures.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com
On 2013-05-21, Jeroen Demeyer wrote:
> Perhaps add a reference to the ticket and the patchbot results page...
http://patchbot.sagemath.org/ticket/14249/, the
Fedora/18/x86_64/3.8.11-200.fc18.x86_64/desktop
patchbot.
--
You received this message because you are subscribed to the Google Groups
And the whole output from make:
0 jan@kontiki:~/src/sage-5.9$make
cd spkg && \
"../spkg/pipestatus" \
"env SAGE_PARALLEL_SPKG_BUILD='' ./install all 2>&1" \
"tee -a ../logs/install.log"
/home/jan/src/sage-5.9/spkg/bin/testcc.sh: 134:
/home/jan/src/sage-5.9/spkg/bin/testcc.sh: /
Hi
I don't seem to have that option sent. I did not set it manually.
I think you mean this?
~/src/sage-5.9/spkg/build/prereq-1.2/config.log
Regards,
Jan
On 20 May 2013 02:55, leif wrote:
> Jan Groenewald wrote:
>
>> Just for fun, I started a build on the ubuntu development release.
>>
>> It
> http://trac.sagemath.org/sage_trac/ticket/11243
>
> and it looks like
>
> http://boxen.math.washington.edu/home/kirkby/patches/python-2.6.4.p10...
>
> might be what you want. This issue went away in Python 2.7 so it is no
> longer an issue.
And it's possible that this won't work with Ubuntu 12
On Tuesday, May 21, 2013 1:24:08 AM UTC-4, ghm...@mst.edu wrote:
>
> Alright, here's all of the information that seems relevant:
>
> I'm running Ubuntu 12.04 as a Virtual Machine (More than enough memory -
> up to 100 GB if needed for everything!) hosted on a Windows 8 laptop. I
> inherited a
Dear all,
After some years of work, Burcin and others have finally managed to get
#9880 into a state where we can hope to merge it quite soon.
The problem solved there is that the order used by pynac internally (and
for printing) was not a Strict Weak Ordering and caused segfaults and
incoheren
On 21 May 2013 15:49, Jeroen Demeyer wrote:
> On 05/21/2013 03:01 PM, John Cremona wrote:
>>
>> Then I have to do something slightly complicated
No -- is that what I am missing? If so I can do that.
Sorry I missed the follow-up to my brief enquiry, I was called away
and just pressed send. You
On 05/21/2013 03:01 PM, John Cremona wrote:
Then I have to do something slightly complicated
Did that "something complicated" involve running ldconfig?
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop rece
I am assuming this is on fermat.
The problem seems to be that libmpfr.so.4 is found in /usr/local/lib,
but that libgmp.so.11 which also lives in /usr/local/lib, is not found:
jdemeyer@fermat:~$ ldd /usr/lib/gcc/x86_64-linux-gnu/4.6/cc1
linux-vdso.so.1 => (0x7fff55c41000)
l
On 05/21/2013 03:01 PM, John Cremona wrote:
This is something which hit me when I built sage-5.10.beta4 but it is
not specific to that release.
I upgraded my systems's version of mpir, mpfr, flint and ntl, and
installed them all in /usr/local/. When building mpir I use the
--enable-gmpcompat op
I would just make sure that the unpickling old matrices still works.
--Mike
--Mike
On Tue, May 21, 2013 at 2:02 PM, Jean-Pierre Flori wrote:
>
>
> On Tuesday, May 21, 2013 2:47:07 PM UTC+2, Martin Albrecht wrote:
>>
>> Sounds like a good idea to me.
>
> Sounds good to me too.
>>
>>
>> On Tuesda
On Tuesday, May 21, 2013 2:47:07 PM UTC+2, Martin Albrecht wrote:
>
> Sounds like a good idea to me.
>
Sounds good to me too.
>
> On Tuesday 21 May 2013, Volker Braun wrote:
> > Reposted at the top to increase visiblitiy (see
> > https://groups.google.com/d/msg/sage-devel/5PdRIUic2Es/l0yDYLG
This is something which hit me when I built sage-5.10.beta4 but it is
not specific to that release.
I upgraded my systems's version of mpir, mpfr, flint and ntl, and
installed them all in /usr/local/. When building mpir I use the
--enable-gmpcompat option so that the library which gets inslatted
Sounds like a good idea to me.
On Tuesday 21 May 2013, Volker Braun wrote:
> Reposted at the top to increase visiblitiy (see
> https://groups.google.com/d/msg/sage-devel/5PdRIUic2Es/l0yDYLG_8qIJ)
>
> The sage matrices use unsigned long for the mod_int datatype. This does not
> fit into a (signed)
Reposted at the top to increase visiblitiy (see
https://groups.google.com/d/msg/sage-devel/5PdRIUic2Es/l0yDYLG_8qIJ)
The sage matrices use unsigned long for the mod_int datatype. This does not
fit into a (signed) python int, so whenever it reaches Python (assigning to
a Python variable, or pass
Perhaps add a reference to the ticket and the patchbot results page...
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To
Hi!
I am wondering about the behaviour of two plugins.
The first is plugins.doctest_continuation.
It complains about lines such as the following:
+action = self.discover_action(R, sageS, op, r=r)$
This not even is part of a doc string, and it does not even contain
continuation
On Monday, 20 May 2013 22:36:58 UTC+8, William wrote:
>
> On Mon, May 20, 2013 at 2:06 AM, Dima Pasechnik
> >
> wrote:
> > M2 spkg in Sage is so old (ver 1.1, as opposed to just released 1.6:
> > https://github.com/Macaulay2/M2/tree/release-1.6)
> > that it's better to completely remove it f
Will do. I have a few other things on hand right now though but I'll
definitely get to it eventually. In the meantime, anyone else feel free to
review this.
On Thursday, May 9, 2013 8:17:30 PM UTC-7, Kenneth Lin wrote:
>
> Hey everyone,
>
> So I'm not sure if I discovered two bugs in random_matr
Dear Sage developers,
If you know about LaTeX: there is a *blocker* ticket needing review
which deals with removing the deprecated utf8x package:
http://trac.sagemath.org/sage_trac/ticket/14571
Thanks,
Jeroen.
--
You received this message because you are subscribed to the Google Groups
"sag
39 matches
Mail list logo
