On Wednesday, August 19, 2015 at 12:36:07 PM UTC+2, vdelecroix wrote:
On 19/08/15 12:31, Jean-Pierre Flori wrote:
On Wednesday, August 19, 2015 at 12:21:36 PM UTC+2, vdelecroix wrote:
Note that all the solutions given will *copy* the mpz_t to the Integer.
Is that what you
On Wednesday, August 19, 2015 at 11:19:30 AM UTC+2, Ralf Stephan wrote:
Given an mpz_t, how to most effectively create an Integer?
The best I can come up with is through the string representation.
Or, of course, by patching integer.pyx.
Am I missing something?
From Cython you can use the
OK cool ! Thanks again !
On Friday, July 31, 2015 at 10:40:46 PM UTC+2, Justin C. Walker wrote:
On Jul 31, 2015, at 08:36 , Pierre wrote:
Hi,
I have asked a version of this question here:
https://groups.google.com/forum/#!topic/sage-support/2KJQhOf-N7Y
However I now have
about computations
over ZZ, using singular, not being trustworthy. Sage 6.2 doesn't have that.
Could it have an effect on the speed?
Anyway, just wanted to point this out. It would be lovely if this could be
fixed as some point. I'm really enjoying the cloud !
Thanks,
Pierre
--
You received
takes about 92ms on my laptop (Sage 6.8.rc1, core i7-4600 @ 2.10
GHz).
So if it's a Sage 6.7-thing, it's fixed again :-)
Johan
William Stein writes:
On Fri, Jul 31, 2015 at 8:36 AM, Pierre pierre@gmail.com
javascript: wrote:
Hi,
I have asked a version of this question
Your plan does look good to me Martin.
Just note it wont be trivial.
--
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
sage-devel or sage-support (or sage-install or sage-apple or sage-osx :)
--
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
OS X in VM's? Is that legal? Maybe only on OS X hardware?
--
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 post to this
Le lundi 8 juin 2015 13:54:01 UTC+2, Stefan Auracher a écrit :
In the past I had the same experience. I did it but in the last years, but
it was really difficult. But recently I tried an install of cygwin with the
setup-x86_64.exe --no-admin switch and it worked very well wihout any
Le lundi 8 juin 2015 14:22:20 UTC+2, Jean-Pierre Flori a écrit :
Le lundi 8 juin 2015 13:54:01 UTC+2, Stefan Auracher a écrit :
In the past I had the same experience. I did it but in the last years,
but it was really difficult. But recently I tried an install of cygwin with
the setup
Le lundi 8 juin 2015 18:02:46 UTC+2, Stefan Auracher a écrit :
How to do this ?
I found in ~/sage-6.7/src/module_list.py
Extension('sage.rings.polynomial.pbori',
sources = ['sage/rings/polynomial/pbori.pyx'],
libraries=['polybori-' + polybori_major_version,
On Friday, June 5, 2015 at 2:49:40 PM UTC+2, Stefan Auracher wrote:
the logfile
~/sage-6.7/logs/pkgs/python-2.7.8.log
at the very end after make[3]: Leaving directory
'/home/XX/sage-6.7/local/var/tmp/sage/build/python-2.7.8/src'
failed with:
Installing valgrind suppression
It seems the trac/git failure was not caused by the lack of space on /tmp
as it is still dysfunctional.
--
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
Dear all,
In case the one in charge was not aware, it seems the trac git interface is
half broken.
For instance,
http://git.sagemath.org/sage.git/diff/?id=2341c22ee7ce66cd1cf80949b1a7c9a4f6e5431f
shows no diff.
Best,
JP
--
You received this message because you are subscribed to the Google
Thanks.
On Thursday, May 21, 2015 at 9:29:18 PM UTC+2, Eric Gourgoulhon wrote:
Le jeudi 21 mai 2015 19:22:53 UTC+2, Volker Braun a écrit :
fixed
Thanks!
Eric.
--
You received this message because you are subscribed to the Google Groups
sage-devel group.
To unsubscribe from this
In http://trac.sagemath.org/ticket/18027, Jeroen would like to drop
(partly) drop suppor for such CPUs when signals are received.
I guess what would happen is that an additional SIGILL or something like
that will happen because of the unsupported MMX-only FPU reset asm
instruciton, but I did
Great news!
I guess we can finally have a make donwload target which only downloads
standard packages now.
And maybe a simple way to cleanup the upstream directory, see #16327.
On Sunday, May 17, 2015 at 8:30:04 AM UTC+2, Nathann Cohen wrote:
We were not talking about a catalog, but an
Dear all,
My Sage 6.6 install quits after printing a depreciation warning message
when I issue:
sage: vars()
Same is true for at least globals().
Any clue on what's going on?
Best,
JP
--
You received this message because you are subscribed to the Google Groups
sage-devel group.
To
I unpacked the sage 6.6 tarball and ran make.
I'll have some trouble posting the exact output here as the machine is not
connected to the network, but basically:
* I'm on an amd64 Ubuntu 14.04.2 LTS.
* I launch: sage
* I type at Sage's prompt: vars()
* I get:
/blablabla/pretty_print.py:147:
Latest NTL releases also require C++11.
--
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 post to this group, send email
On Friday, April 24, 2015 at 10:42:12 AM UTC+2, John Cremona wrote:
On 24 April 2015 at 09:37, John Cremona john.c...@gmail.com javascript:
wrote:
Who is the author of hyperellfrob?
OK, I found it (it is actually called hypellfrob): David Harvey.
David, if you are listening -- any
Dear all,
It seems we're shifting from the original way we were building Cython
extensions where each extension was listed in module_list.py to use
wildcards in module_list.py.
See #7987 and #15410 for wide coverage tickets, and e.g. #17767 for more
focused ones.
This is problematic when some
On Tuesday, April 7, 2015 at 8:43:58 PM UTC+2, Jean-Pierre Flori wrote:
On Tuesday, April 7, 2015 at 6:56:56 PM UTC+2, vdelecroix wrote:
Hello,
We currently ship two implementations of floating point complex numbers:
- ComplexField: home made implementation based on two mpfr
On Tuesday, April 7, 2015 at 6:56:56 PM UTC+2, vdelecroix wrote:
Hello,
We currently ship two implementations of floating point complex numbers:
- ComplexField: home made implementation based on two mpfr for the
real and imaginary parts
- MPComplexField: implementation based on the
Anyways, somewhat limited is an understatement.
To be fair, the french financement est pour le moins limité means
something like funding is limited, to say the least. Don't trust google !
:-)
pierre
--
You received this message because you are subscribed to the Google Groups
sage-devel
Let's replace Python by Julia :p
http://lavieestmaloptimisee.blogspot.fr/2015/03/les-informaticiens-meprisent.html?view=classic
--
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
/articles/fog69.html
On Tuesday, March 31, 2015 at 12:11:34 PM UTC+2, Jean-Pierre Flori wrote:
Let's replace Python by Julia :p
http://lavieestmaloptimisee.blogspot.fr/2015/03/les-informaticiens-meprisent.html?view=classic
--
You received this message because you are subscribed
The few times I played with comparison functions, I found what we have
quite confusing, especially the discrpancy between Python and Cython
classes, so any simplification would be welcomed.
And if it also eases the transition towards Python 3 that would be great.
--
You received this message
Not really related but it seems ECL saw an update!
On Wednesday, February 25, 2015 at 10:43:28 PM UTC+1, François wrote:
On 02/26/15 10:30, Julien Puydt wrote:
Hi,
Le 25/02/2015 10:56, Julien Puydt a écrit :
it is a strange problem I have : using either debian's ecl or
upstream's
On Monday, February 23, 2015 at 3:34:08 PM UTC+1, Dima Pasechnik wrote:
On 2015-02-23, Julien Puydt julien...@laposte.net javascript: wrote:
Le 23/02/2015 15:05, Julien Puydt a écrit :
Le 23/02/2015 14:27, Julien Puydt a écrit :
That will take some time though : this box isn't fast.
On Saturday, February 21, 2015 at 5:25:07 PM UTC+1, Volker Braun wrote:
The atlas build script just aborts with SAGE_ATLAS_ARCH=base, nothing else
to see here.
Pointing to a specific location for the atlas library isn't going to be
much use in a binary that we distribute.
On
On Friday, February 20, 2015 at 4:29:38 PM UTC+1, John Cremona wrote:
On 20 February 2015 at 15:10, Vincent Delecroix
20100.d...@gmail.com javascript: wrote:
Hello,
We do have two very serious critical bug with the new version 6.5,
namely
* #17806 (MPIR compilation)
*
Dear all,
Is this still a problem?
Best,
JP
--
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 post to this group, send
GMP was added as an optional package in
http://trac.sagemath.org/ticket/12661.
Who should I CC?
--
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
Thanks!
I also added Volker just in case.
On Tuesday, January 13, 2015 at 4:15:09 PM UTC+1, Dima Pasechnik wrote:
On 2015-01-13, Jean-Pierre Flori jpf...@gmail.com javascript: wrote:
GMP was added as an optional package in
http://trac.sagemath.org/ticket/12661.
Who should I CC
Thanks!
On Tuesday, January 13, 2015 at 4:30:48 PM UTC+1, Volker Braun wrote:
Done!
On Tue, Jan 13, 2015 at 4:20 PM, Jean-Pierre Flori jpf...@gmail.com
javascript: wrote:
Thanks!
I also added Volker just in case.
On Tuesday, January 13, 2015 at 4:15:09 PM UTC+1, Dima Pasechnik
On Thursday, January 8, 2015 at 4:34:22 PM UTC+1, William wrote:
Hi,
Would anybody be interested in helping me to organize a bug days
workshop sometime in the next few months?
I have plenty of funding for this for US people and can scrounge up
some funds for some non-US people.
Hi,
On Friday, January 9, 2015 at 12:30:16 PM UTC+1, Jean-Pierre Flori wrote:
On Friday, January 9, 2015 at 9:49:52 AM UTC+1, Sebastien Gouezel wrote:
The webpage http://trac.sagemath.org/wiki/Cygwin64Port indicates that
sage can now be built under cygwin64 almost out of the box. So, I tried
On Friday, January 9, 2015 at 9:49:52 AM UTC+1, Sebastien Gouezel wrote:
The webpage http://trac.sagemath.org/wiki/Cygwin64Port indicates that
sage can now be built under cygwin64 almost out of the box. So, I tried,
but I failed...
Here are the problems I encountered, maybe someone with
On Wednesday, January 7, 2015 5:02:31 AM UTC+1, Nathan Dunfield wrote:
I agree: Tkinter works out-of-the box on OS X with any recent source or
binary release of Sage.
Can you review that ticket, then? I have no experience with Tkinter
myself.
Sure, but what does that mean given
Sorry, I meant the milestone.
--
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 post to this group, send email to
On Tuesday, January 6, 2015 3:51:29 PM UTC+1, John Cremona wrote:
By the way, there is discussion of building Pari under Cygwin 64 on
the pari-dev list; bugs are being discovered and fixed as I type.
Great news!
My last findings were that PARI behaved very badly on Cygwin64.
For example
On Tuesday, January 6, 2015 4:02:45 PM UTC+1, Jean-Pierre Flori wrote:
On Tuesday, January 6, 2015 3:51:29 PM UTC+1, John Cremona wrote:
By the way, there is discussion of building Pari under Cygwin 64 on
the pari-dev list; bugs are being discovered and fixed as I type.
Great news
I would also be nice to be able to pass GF(3,3).
If I ever find some time to implement it, I'll do it, but anyone can feel
free to do it before I do.
--
You received this message because you are subscribed to the Google Groups
sage-devel group.
To unsubscribe from this group and stop receiving
Anyhow, the above looks ugly. How about
sage: F.z5 = GF(3, 5)
and the following should also lead to the same thing:
sage: F.z5 = GF(3^5)
We already have that, or am I missing something?
Dima
Peter
Op dinsdag 30 december 2014 12:35:30 UTC+1 schreef Dima Pasechnik:
On Tuesday, December 30, 2014 1:40:29 PM UTC+1, Bruno Grenet wrote:
Le 30/12/2014 13:31, Jean-Pierre Flori a écrit :
Anyhow, the above looks ugly. How about
sage: F.z5 = GF(3, 5)
and the following should also lead to the same thing:
sage: F.z5 = GF(3^5)
We already have
Thanks to Travis, only the ATLAS patch needs review!
http://trac.sagemath.org/ticket/17365
http://www.google.com/url?q=http%3A%2F%2Ftrac.sagemath.org%2Fticket%2F17365sa=Dsntz=1usg=AFQjCNHvTmGm10lUGkMxeJuWeXDU1cA2Hg
--
You received this message because you are subscribed to the Google Groups
Nathann, if you're still tens of kilometers away from the nearest pub, you
might want to turn all the info here into proper documentation?
On Sunday, December 28, 2014 1:45:26 AM UTC+1, Nils Bruin wrote:
On Saturday, December 27, 2014 3:13:37 PM UTC-8, Simon King wrote:
That's exactly what I
On Friday, December 26, 2014 9:07:06 PM UTC+1, Dima Pasechnik wrote:
On 2014-12-26, Volker Braun vbrau...@gmail.com javascript: wrote:
--=_Part_5531_1685050387.1419616059330
Content-Type: multipart/alternative;
boundary==_Part_5532_1775001320.1419616059330
, Jean-Pierre Flori wrote:
On Thursday, November 27, 2014 6:39:13 PM UTC+1, Jean-Pierre Flori wrote:
And I forgot http://trac.sagemath.org/ticket/17365
http://www.google.com/url?q=http%3A%2F%2Ftrac.sagemath.org%2Fticket%2F17365sa=Dsntz=1usg=AFQjCNHvTmGm10lUGkMxeJuWeXDU1cA2Hg
and http
On Friday, December 19, 2014 4:03:44 PM UTC+1, Bruno Grenet wrote:
I've changed recently the status of a ticket to needs review since I
think it is not relevant anymore, and I wanted it to be closed. I now
guess it is not the right approach... What should I do in such a case?
Put it to
I guess this is:
https://groups.google.com/forum/#!searchin/sage-devel/complex.h/sage-devel/iA3K1T8lPlQ/hyACRbExOkMJ
On Wednesday, December 17, 2014 2:33:46 PM UTC+1, Simon King wrote:
Hi!
I just have now installed openSUSE 13.2 64bit on my laptop (it has
previously
been 12.3), and now
On Wednesday, December 17, 2014 3:10:36 PM UTC+1, Simon King wrote:
Hi Jean-Pierre,
On 2014-12-17, Jean-Pierre Flori jpf...@gmail.com javascript: wrote:
I guess this is:
https://groups.google.com/forum/#!searchin/sage-devel/complex.h/sage-devel/iA3K1T8lPlQ/hyACRbExOkMJ
Yes
On Thursday, November 27, 2014 6:39:13 PM UTC+1, Jean-Pierre Flori wrote:
And I forgot http://trac.sagemath.org/ticket/17365 and
http://trac.sagemath.org/ticket/15649 which need a little love (and as it
only affects Cygwin should be easy to review, at least if you trust me
Do we have anything about that in our dev guide?
Or at least a pointer to the rest/sphinx doc? e.g.
http://docutils.sourceforge.net/docs/ref/rst/restructuredtext.html
Every time I have to add doc I wonder whether I should use one or two
backticks and so on and cannot find anything in our docs...
On Tuesday, December 9, 2014 6:25:56 PM UTC+1, William wrote:
On Tue, Dec 9, 2014 at 9:20 AM, mmarco mma...@unizar.es javascript:
wrote:
Yes we do, but not as completely as x86. For instance the last version
that
has an arm binary in the download page is 5.13.
The Wolfram
On Monday, December 8, 2014 9:53:51 PM UTC+1, mmarco wrote:
Maybe support for arm architecture would be relevant in that respect.
We do support ARM, don't we?
At least I'm able to compile Sage from scratch on a Raspberry Pi and on
armv7+ as well.
--
You received this message because you
On Thursday, December 4, 2014 3:38:18 PM UTC+1, Dima Pasechnik wrote:
On 2014-12-01, Volker Braun vbrau...@gmail.com javascript: wrote:
--=_Part_3157_1040776803.1417466369538
Content-Type: multipart/alternative;
boundary==_Part_3158_1081423206.1417466369539
I, just downloaded the Sage.app (OSX 10.9) from 2 different server and the
resulting downloads didn't give the Sage.app, but simply the src
Maybe theres a problems?
--
You received this message because you are subscribed to the Google Groups
sage-devel group.
To unsubscribe from this group and
On Tuesday, November 25, 2014 10:46:56 PM UTC+1, mmarco wrote:
The result of the compilation is relocatable? I mean, would it be
eventually possible to have something that windows users just unzip and
runs? Or would they always need to compile it?
I would say so, i dont really know if any
And I forgot http://trac.sagemath.org/ticket/17365 and
http://trac.sagemath.org/ticket/15649 which need a little love (and as it
only affects Cygwin should be easy to review, at least if you trust me)!!!
--
You received this message because you are subscribed to the Google Groups
sage-devel
On Wednesday, November 26, 2014 9:17:27 PM UTC+1, François wrote:
Hi,
A bit of a shot in the dark but could you try it from a folder with
only ascii characters? Telechargements instead of Téléchargement.
It is possible that the ecl bootstrap doesn't like those characters
very much.
Hi all,
With http://trac.sagemath.org/ticket/15649 and
http://trac.sagemath.org/ticket/17365 which need reviews and touch
Cygwin-only code we'll (almost) have support to build Sage trivially (type
make) on Cygwin (again) and Cygwin64 (for the first time).
Only the MPIR update at
Note that everything gets built, but at this point I don't promise it is
really functional.
Cygwin32 should be almost fully functional.
Cygwin64 is very far from it (e.g. PARI builds but seems completely broken:
it says 131 is not prime).
Anyway getting back to a point where just typing make
As time goes it gets bigger and bigger...
--
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 post to this group, send email
Dear all,
Anyone feeling like reviewing the updates to NTL 6.2.1
(http://trac.sagemath.org/ticket/16882) and Singular 3-1-7
(http://trac.sagemath.org/ticket/17184) ?
It would be nice to have them in before working on the much more involved
Singular 4-0-x and (surely not so hard) NTL 7.0.1
On Monday, November 17, 2014 1:45:09 PM UTC+1, Volker Braun wrote:
I would like to propose another change to SPKG.txt, and that is to NOT
document patches in there but in the patch file. As you might know, the
patch can have arbitrary text before the first diff hunk, anything that is
not
On Tuesday, November 11, 2014 10:12:33 PM UTC+1, François wrote:
I guess the compiler requirement will kill all the problems
we saw in #16882 which is a good thing TM.
Sure, but will make a lot of people have to compile GCC 4.9.2 :)
Could you review #16882 before we begin working on the
Dear all,
As you must have noticed, Victor Shoup just released a new thread safe
version of NTL.
He also took the opportunity to ask me (and surely a bunch of other people)
what would be expected from exception handling in NTL
Currently NTL just prints something and then aborts.
Note that we
. What _is_
expensive is when an exception occurs, but in C++ you are not supposed to
use exceptions for program flow like in Python.
On Tuesday, November 11, 2014 10:15:44 PM UTC, Jean-Pierre Flori wrote:
Dear all,
As you must have noticed, Victor Shoup just released a new thread safe
of (or the exception thrown
within) a thread is pretty handy.
Cheers,
Francesco.
On 12 November 2014 00:05, Jean-Pierre Flori jpf...@gmail.com
javascript: wrote:
On Tuesday, November 11, 2014 11:55:49 PM UTC+1, Volker Braun wrote:
What kind of error states are we talking about? divide
On Wednesday, November 5, 2014 2:17:29 PM UTC+1, Volker Braun wrote:
There is already a make download. If you want you can add a make
download-more (or so) to also download popular optional packages...
Doesn't make download already download everything?
Or was it fixed/changed?
--
You
On Wednesday, November 5, 2014 2:39:15 PM UTC+1, Thierry
(sage-googlesucks@xxx) wrote:
On Wed, Nov 05, 2014 at 05:22:17AM -0800, Jean-Pierre Flori wrote:
On Wednesday, November 5, 2014 2:17:29 PM UTC+1, Volker Braun wrote:
There is already a make download. If you want you can
Dear all,
Should we go on stripping down upstream tarballs from stuff we don't use
when there is some substantial gain?
See http://trac.sagemath.org/ticket/17169 (GCC) and
http://trac.sagemath.org/ticket/15015 (MPIR).
We can debate forever on when the gain becomes substantial in comparison
I agree let's get rid of this.
I've updated a bunch of packages but did not feel like filling this field
with my name as I couldn't promise I'll keep on maintaining the packages.
--
You received this message because you are subscribed to the Google Groups
sage-devel group.
To unsubscribe from
We're stuck at http://trac.sagemath.org/ticket/17184.
I've also posted on Singular forum:
http://www.singular.uni-kl.de/forum/viewtopic.php?f=10t=2466sid=01f281c0cfb23e8e420dbe49dc1a85cb
Help from someone knowing Singular internals would be welcome.
Best,
JP
--
You received this message
There used to be Itanium machines on the GCC Compile Farm, and I have
access there, in particular for testing/developing Sage stuff.
I don't now the current situation though.
Actually, I am supposed to write a laius about the need for Sage
portability on exotic archs/porting somehow on Windows
Relevant?
https://groups.google.com/d/msg/sage-devel/-sm2ejzcjY8/x27G0nMRdY4J
On Friday, October 17, 2014 6:58:16 PM UTC+2, Volker Braun wrote:
I upgraded my OSX buildbot, now it doesn't compile Sage any more ;-)
Checking multilib configuration for libgcc...
Configuring stage 1 in
I think it would also be a good idea to get in contact with the matroids
folk who got a lot of code integrated into Sage some time ago.
Or even better with Eric Gourgoulhon whos currently writing a lot of code
for his project and getting it integrated into Sage piece by piece.
On top of that
I also agree with the removal, with the issue of ATLAS.
Maybe we should switch to openblas (IIRC Clément Pernet said it is more
state of the art nowadays) :)
On Tuesday, September 30, 2014 9:15:59 AM UTC+2, Jeroen Demeyer wrote:
See http://trac.sagemath.org/ticket/17072
--
You received
On Tuesday, September 30, 2014 10:51:05 AM UTC+2, Jeroen Demeyer wrote:
On 2014-09-30 08:24, Jeroen Demeyer wrote:
I certainly agree with this, but it should be said that make will take
a longer time when changing packages. For example, you will see ATLAS
being rebuilt very frequently
2. Dima -- do we specifically use bash features in the build scripts of
Sage?
Sage scripts have !/usr/bin/env bash all over the place.
I don't know about 'bashisms' though - one should test on a Debian system,
where bash is not essential, as they have a push to move to dash years
It seems to me it is the case.
Can this be fixed?
It's not really important as the commit is still linked in the branch field
and that's the only place a human can clic.
--
You received this message because you are subscribed to the Google Groups
sage-devel group.
To unsubscribe from this
And maybe I spoke too fast.
The build system of Sage the distribution is not smart enough for sure.
But I seem to remember you may be able to cross compile using lmonade.
--
You received this message because you are subscribed to the Google Groups
sage-devel group.
To unsubscribe from this
On Monday, September 15, 2014 12:30:06 PM UTC+2, mmarco wrote:
I have purchased one of these boards:
https://www.olimex.com/Products/OLinuXino/A20/A20-OLinuXino-LIME/open-source-hardware
And plan to plug in it a ssd drive to allow fast swap space. I would like
to use it to compile sage
On Friday, September 12, 2014 11:15:19 AM UTC+2, bluescarni wrote:
What you want is called cross-compilation, and in general is a
non-trivial thing to do. You have to set up a toolchain on your x86 boxes
able to compile for ARM, use it to compile SAGE and finally move the binary
over to
Hi all,
Here are a few suggestions:
(1) permutations have a to_matrix() method; permuting the rows of M
according to the permutation sigma can be done by
M= M * sigma.to_matrix()
and for the rows:
M= sigma.to_matrix().transpose() * M
Of course there is a debate about the behaviour of
sorry some keyboard shortcut has sent the post. I was saying:
def C(*args): #C for cycle
return Permutation([ args ])
and then for (1, 2, 3)(4, 5) I type C(1, 2, 3) * C(4, 5). I got very used
to it.
cheers
Pierre
On Thursday, September 11, 2014 2:12:21 PM UTC+2, Pierre wrote:
Hi all
this does not remind me of anything except
http://trac.sagemath.org/ticket/3603 which is surely unrelated (different
backend) and http://trac.sagemath.org/ticket/13447 but not so related
either.
On Wednesday, September 10, 2014 1:03:15 AM UTC+2, Volker Braun wrote:
I was dabbling in
Does it also leak with older version of Sage?
--
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 post to this group, send
Indeed it should basically work out of the box if you make some swap space
available (let's say 1 gbyte).
At least it used to do, possibly with a few trivial fixes (and I surely
opened tickets on trac for them, also see
On Friday, September 5, 2014 11:42:21 AM UTC+2, Jori Mantysalo wrote:
On Fri, 5 Sep 2014, Volker Braun wrote:
So it seems that we don't link libf77blas against libgfortran. Whats the
output of
sage -sh -c ldd local/lib/libf77blas.so
linux-vdso.so.1 =
On Friday, September 5, 2014 3:47:53 PM UTC+2, Volker Braun wrote:
I don't know of a ticket, feel free to fix it. All relevant files are in
build/pkgs/singular. It seems that the debug patches conflict with the
cygwin patch. Also, the debug patches should probably be applied strictly
On Wednesday, September 3, 2014 4:57:19 PM UTC+2, Simon King wrote:
Dear all,
I just installed the valgrind spkg, did make, and then started ./sage
--valgrind, in order to run a stress test for what I call biseq
(bounded integer sequences) at #15820. Eventually, I want to use biseqs
On Tuesday, September 2, 2014 3:13:09 PM UTC+2, mmarco wrote:
You mean like using SAGE_ATLAS_LIB to avoid shipping a too optimized
version of that lib?
My comment was more in the line of making sure that the resulting compiled
code does not use instructions that are not available at
Cool.
IIRC different kind of ARM boards have already been used by a bunch of
users with success.
At least I had quite no problems building Sage on a Raspberry Pi and on a
Cortex A9 based board.
On Monday, September 1, 2014 2:49:06 PM UTC+2, Volker Braun wrote:
I'm proposing to make ARM a
Hi Snark,
Did you CC Harald?
I thought he was in charge of this kind of stuff...
--
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
I don't know for sure, but I think linbox does not link to LAPACK
(anymore?).
Maybe that make a small difference already.
I opened a ticket about that some monthes ago.
--
You received this message because you are subscribed to the Google Groups
sage-devel group.
To unsubscribe from this group
On Wednesday, August 27, 2014 9:11:47 PM UTC+2, Jeroen Demeyer wrote:
On 2014-08-27 21:01, Julien Puydt wrote:
but on a general basis people are quite welcoming of
sensible contributions.
Depends on the project. Whenever I think a patch is good for upstream, I
do submit it upstream.
I think one of lmonade's GSoC project was about that.
But I don't think it was picked up
--
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
201 - 300 of 942 matches
Mail list logo
