Yes pexpect. Same deal in sage-on-gentoo. I could add one of the patch from the
current spkg on top of the latest version and it would work everywhere I could
think of except the notebook. Plot would not be rendered. I don't remember
trying with the new notebook.
I would take slower too. On the
I think I got the image working with the linux app I've been using
(Complete Linux Installer), so I'll give Sage a try tomorrow or Sunday.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To post to this group, send email to sage-devel@googlegroup
On 12/21/12 2:55 PM, Paulo César Pereira de Andrade wrote:
I opened a ticket in fedora to bundle cython, ipython and pexpect
for the hopefully very close, fedora sagemath package, see
https://fedorahosted.org/fpc/ticket/238
cython hopefully should not be an issue, and I said it should
require ro
I opened a ticket in fedora to bundle cython, ipython and pexpect
for the hopefully very close, fedora sagemath package, see
https://fedorahosted.org/fpc/ticket/238
cython hopefully should not be an issue, and I said it should
require roughly 6 months to be able to use system ipython.
About pexpe
I didn't have any luck getting the scripts to work with a basic image I
built. Does the image have to be in /sdcard/ubuntu (I replaced
/sdcard/ubuntu with /data/sdext2/ubuntu in the scripts, but I'm not sure if
more has to be done)? Do the scripts need something specific to the image
you prov
Ah, that's a pity. It was too beautyful to be true: the possibility to
deliver a sage android app that does not require to hack your device.
On 21 dic, 19:36, Volker Braun wrote:
> fakechroot is a LD_PRELOAD hack that overrides glibc calls and e.g.
> redirects file open() calls. Though its not pe
fakechroot is a LD_PRELOAD hack that overrides glibc calls and e.g.
redirects file open() calls. Though its not perfect, for example no
pseudo-ttys (I think this already rules out Sage).
On Friday, December 21, 2012 6:19:48 PM UTC, mmarco wrote:
>
> I have seen that there is an android app that
I have seen that there is an android app that runs an ubuntu desktop
without the need of root access. From the web page, i see that it uses
something called fakechroot. I would like to investigate that
possibility. Maybe it could be the open door to some nice android app
that would install sage to
On 21 December 2012 06:09, Simon King wrote:
> Hi David,
>
> On 2012-12-20, David Kirkby wrote:
>> I've compiled Sage on Solaris with Sun libraries which replace
>> malloc/free with versions which check for memory leaks. Sage has
>> leaked memory before the
>>
>> sage:
>>
>> prompt has appeared.
On Friday, December 21, 2012 10:05:50 AM UTC+1, Nils Bruin wrote:
>
>
>
> On Dec 19, 12:16 am, Jeroen Demeyer wrote:
> > Just when I thought the #715 + #11521 issues were fixed in
> sage-5.5.rc1...
> >
> > Apparently, sage-5.6.beta0 has uncovered a new problem: with the current
> > sage-5.6
Le 21/12/2012 15:25, Volker Braun a écrit :
Spkg is here if you want to try it: http://trac.sagemath.org/10508
I'm now trying with 5.5.rc1 with atlas+cvxopt replaced by those in the
ticket : it looks like using SAGE_ATLAS_LIB really doesn't give a good
bdist.
Snark on #sagemath
--
You rece
On 12/21/2012 09:53 PM, Jeroen Demeyer wrote:
On 2012-12-21 14:48, Julien Puydt wrote:
Something like "export SAGE_ATLAS_DONT_OVERDO_IT=yes" would be wonderful.
I think even more stupid is that ATLAS fails to build if it cannot
perfectly tune itself.
Yes. I have had atlas-3.8.4 build fail mul
Dear all,
I just remarked (painfully) that the optional GCC 4.7.2 spkg includes all
of the GCC including gcj which depends on zip or jar for building.
Is this really useful?
As far as Sage development is concerned, I guess that gcc, g++ and gfortran
are enough.
That would make a smaller spkg wit
Spkg is here if you want to try it: http://trac.sagemath.org/10508
On Friday, December 21, 2012 2:24:15 PM UTC, Volker Braun wrote:
>
> Atlas 3.10 adds ARMv7 as machine type. Though it seems we'll never merge
> it because it doesn't work on Itanium and the Atlas dev doesn't have enough
> time t
Atlas 3.10 adds ARMv7 as machine type. Though it seems we'll never merge it
because it doesn't work on Itanium and the Atlas dev doesn't have enough
time to waste on dead architectures.
On Friday, December 21, 2012 2:04:15 PM UTC, Snark wrote:
>
> Le 21/12/2012 14:54, Jean-Pierre Flori a �cr
Le 21/12/2012 14:54, Jean-Pierre Flori a écrit :
Can't you use the SAGE_ATLAS_ARCH and set it to generic or something
like that?
Ah, I didn't know about it ; the choice seems to be one of:
ATLAS_MACHTYPE = ['UNKNOWN', 'POWER3', 'POWER4', 'POWER5', 'PPCG4', 'PPCG5',
'P5', 'P5M
On Friday, December 21, 2012 2:48:07 PM UTC+1, Snark wrote:
>
> Le 21/12/2012 14:14, Volker Braun a �crit :
> > Setting SAGE_ATLAS_LIB creates a symlink to the underlying atlas
> > install. Don't use it if you want to distribute the result.
>
> > Having said that, I'm thinking about a more f
On 2012-12-21 14:48, Julien Puydt wrote:
> Le 21/12/2012 14:14, Volker Braun a écrit :
>> Setting SAGE_ATLAS_LIB creates a symlink to the underlying atlas
>> install. Don't use it if you want to distribute the result.
>
>> Having said that, I'm thinking about a more flexible system for
>> deployin
Le 21/12/2012 14:14, Volker Braun a écrit :
Setting SAGE_ATLAS_LIB creates a symlink to the underlying atlas
install. Don't use it if you want to distribute the result.
Having said that, I'm thinking about a more flexible system for
deploying and using blas/lapack. I'll probably post to sage-d
Setting SAGE_ATLAS_LIB creates a symlink to the underlying atlas install.
Don't use it if you want to distribute the result.
Having said that, I'm thinking about a more flexible system for deploying
and using blas/lapack. I'll probably post to sage-devel about that soon.
On Friday, December
Le 21/12/2012 09:41, P Purkayastha a écrit :
On 12/21/2012 03:55 PM, Julien Puydt wrote:
Hi,
building sage on a box using SAGE_ATLAS_LIB then running sage -bdist to
get something to run on another box doesn't work: you'll have to install
atlas on the target system too.
Is it documented somewhe
On 2012-12-21 07:09, Simon King wrote:
> Can you try to install the singular spkg from #13731, after doing
> export SINGULAR_XALLOC=yes
> followed by sage -b, please?
That doesn't change anything. I still get the segmentation fault as before.
--
You received this message because you are subscri
On 2012-12-21 10:05, Nils Bruin wrote:
> Anyway, perhaps someone can replicate that this test fails on linux
> with MALLOC_CHECK_=3 as well.
I don't manage to replicate it on sage.math (Ubuntu 8.04, x86_64). The
test always succeeds.
--
You received this message because you are subscribed to the
On Dec 19, 12:16 am, Jeroen Demeyer wrote:
> Just when I thought the #715 + #11521 issues were fixed in sage-5.5.rc1...
>
> Apparently, sage-5.6.beta0 has uncovered a new problem: with the current
> sage-5.6.beta0, I get the following reproducible segfault on hawk
> (OpenSolaris i386):
>
> > sag
On 12/21/2012 03:55 PM, Julien Puydt wrote:
Hi,
building sage on a box using SAGE_ATLAS_LIB then running sage -bdist to
get something to run on another box doesn't work: you'll have to install
atlas on the target system too.
Is it documented somewhere, and if not, where should I document it?
S
25 matches
Mail list logo
