On 2012-11-13, at 10:49 , Jeroen Demeyer wrote:
> On 2012-11-13 16:43, Kevin Horton wrote:
>> sage/groups/perm_gps/permgroup_element.c:12434: error: ‘__pqx_clineno’
>> undeclared (first use in this function)
> It's a hardware problem, a bit got flipped in that file. The string
> should be __pyx_
Hey Sebastien,
This is what worked for me:
For patchbot:
Apply: name_of_patch-author.patch
For multiple patches, I've seen commas separate patches and also explicitly
stating "then".
Best,
Travis
On Tuesday, November 13, 2012 3:04:42 PM UTC-8, Sébastien Labbé wrote:
>
> Hi sage-devel,
>
>
On Monday, November 12, 2012 9:18:26 PM UTC-6, yomcat wrote:
>
> On 13/11/2012, at 4:16 PM, Nils Bruin >
> wrote:
> >
> > Incidentally: Are PPC-OSX4 (or where-ever the problem earlier arose)
> > and i686 both 32 bit platforms?
>
> Yes.
>
I'll try to setup a 32 bits (on i686) install of the
Hi sage-devel,
I have two examples of tickets having problems speaking the language of the
buildbot. In #12083, the last patchbot test was made in January 2012 on
sage-4.8 [2]. In #12996, there was never any patchbot test and we are not
able to say to the patchbot that only 3 of the six patches
I don't have the bandwidth right now to try it myself, but the VM build
script ran fine. The adventurous can find the virtual machine image here:
http://www.stp.dias.ie/~vbraun/Sage/sage-5.4.ova
I'm also pretty sure that automatic login to the notebook is still broken,
requiring you to make a n
Thierry, I find your message to be great in all parts, but I would like to
point out a thing...
2012/11/13 Thierry
> bios not able to boot on USB
Again, this is not a big problem. :P You can build a CD or even a floppy
disk with PLOP boot manager and even boot a Pentium II from USB. :D I did
t
On 2012-11-13 16:43, Kevin Horton wrote:
> sage/groups/perm_gps/permgroup_element.c:12434: error: ‘__pqx_clineno’
> undeclared (first use in this function)
It's a hardware problem, a bit got flipped in that file. The string
should be __pyx_clineno instead of __pqx_clineno. You should run memtest
to
Sage 5.4 fails to build for me on Ubuntu 10.04 32 bit:
gcc -fno-strict-aliasing -fwrapv -DNDEBUG -g -fwrapv -O3 -Wall
-Wstrict-prototypes -fPIC -I/home/kwh/sage-5.4/local/include
-I/home/kwh/sage-5.4/local/include/csage
-I/home/kwh/sage-5.4/devel/sage/sage/ext
-I/home/kwh/sage-5.4/local/includ
The openssl and gfortran issues should be solved in sage-5.4, they are
no longer needed.
--
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@googlegroups.com.
To unsubscribe from this group, send email t
>
>
> I know very little about all the technicalities of these reports but want
> to echo that it is VERY valuable to have these real-life experiences - what
> a great thread.
>
> I recommend that several of these analyses be put on a wiki page linked to
> http://wiki.sagemath.org/#Hosting_a_
On Tuesday, November 13, 2012 9:53:34 AM UTC-5, sage-goo...@lma.metelu.net
wrote:
>
> Hi,
>
> thanks Nicolas for this exhaustive report. I would like to witness this
> adventure it in a more pessimistic way, so that people willing to host
> such a sage days know what kind of problems will app
Hi,
thanks Nicolas for this exhaustive report. I would like to witness this
adventure it in a more pessimistic way, so that people willing to host
such a sage days know what kind of problems will appear, and which
workarounds are realistic.
Being free software is definitely not a sufficient condi
Hi
No, I am talking about buildbot slaves -- the upstream sage mechanism for
testing and building binaries.
( I simply repackage these for Ubuntu packages, and can use pbuilder and
launchpad for that )
Regards,
Jan
On 13 November 2012 13:40, Timo Kluck wrote:
> Hi Jan,
>
> You're talking abo
>I could hope for 4-5 that will use Sage in the long run, and 20 that
> definitely see the point but will get stuck by lack of infrastructure
> and expertise.
These sound like great numbers.
>>I think to break the barrier and make a true sage days really
>>productive, I think that you
Hi Jan,
You're talking about building debian packages, right? Maybe it's helpful if
you have a look at pbuilder and pbuilder-dist. Those tools allow you to
build packages for other versions of Debian and Ubuntu than the machine
you're building on. Then you don't need to have dedicated installs
Thanks for all the reply.
I hope that anyone know a good way to debug cython "Python-like" code
without using insert print statements.
> I should have googled before I replied:
>
> http://docs.cython.org/src/userguide/debugging.html
Before I post the question I had take a look it the link above
On 13 November 2012 03:25, Dima Pasechnik wrote:
> On 2012-11-13, Nils Bruin wrote:
>> On Nov 12, 6:06 pm, Dima Pasechnik wrote:
>>> sage: e.cremona_label()
>>> '457532830151317a1'
>>> sage: e.analytic_rank(leading_coefficient=True)
>>> (4, -2.50337480324368498e-9)
>>>
>>> here is what I got aft
please see http://trac.sagemath.org/sage_trac/ticket/13705
Apparenly, PARI(?) runs out of memory.
--
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@googlegroups.com.
To unsubscribe from this group, se
18 matches
Mail list logo
