I ran the compile again after shutting down several services. I also shut
down a swap file so that it would only have swap disk partitions to use.
I started getting read and write errors on the swap drive which is a SDHC
card in a reader. Eventually the kernel oopsed/crashed. Maybe it is the
As mentioned on the ticket it might be good to still post your "broken"
patch. Not every patch needs to be perfect the first time. By posting your
code it is easier for people to see exactly what is broken by your faster
code (probably it is because there are some functions that directly modify
On 1/1/13 2:45 PM, Jernej Azarija wrote:
This can of course be improved by storing a hash map for each vertex and
updating its neighbouring vertices on each addition/deletion of an edge
and deletion of a vertex.
IIRC, this is exactly how networkx works, as a dict of vertices/neighbors.
Thanks,
Thanks everyone for you replies.
Indeed one can obviously name graphic files as they want, but the point was
not to have to tinker with the filename argument every time I use the plot
method of some Sage class.
So the good/easy fix is to configure my image viewer to sort files by date.
Le lund
Hello!
By profiling Sage scripts involving graphs one can easily see that the
bottleneck is usually in computing the list of neighbours
(Graph.neighbours). This is somehow to be expected since most
graph-theoretical algorithms perform operations on neighbours of vertices.
Currently it appear
Can you do another build where you replace the old mercurial with this one:
http://www.stp.dias.ie/~vbraun/Sage/spkg/mercurial-2.2.2.p1.spkg
This is now http://trac.sagemath.org/13898
On Tuesday, January 1, 2013 8:31:41 PM UTC, Robert Zeier wrote:
>
> /usr/bin/xcodebuild -version
> Xcode 4.5.2
I do not see how this would be possible as
I did upgrade Xcode to the latest version some time ago
and I have never installed a "second" version of Xcode:
/usr/bin/xcodebuild -version
Xcode 4.5.2
Build version 4G2008a
I did find some strange files but I do not think that they are the problem:
1
The following ticket says that this was fixed in XCode 4.5. Are you sure
you don't have an old version floating around?
http://trac.sagemath.org/sage_trac/ticket/13309
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To post to this group, send e
On Dec 31 2012, 9:36 am, Nils Bruin wrote:
> It might by cython, not python:
This is now
http://trac.sagemath.org/sage_trac/ticket/13896
--
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
How could I figure this out?
Am Dienstag, 1. Januar 2013 19:05:12 UTC+1 schrieb Volker Braun:
>
> Somebody with a Mac should try to figure out if we only need it for
> mercurial or whether its needed globally...
>
--
You received this message because you are subscribed to the Google Groups
"sa
I ran the tests again and this time only one test failed -
sage -t --long -force_lib "devel/sage/sage/modular/modform/find_generators.py"
There was a segmentation fault for this test. Sorry for the noise
about other tests earlier.
Rajeev
--
You received this message because you are subscribed
Le 01/01/2013 18:06, Don Harter a écrit :
My compile has gotten to m4rie/conversion.c.
Oh, that one file is such a pain, see my recent ramblings on this list.
Snark on #sagemath
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To post to this g
This is Apple in their infinite wisdom relying on non-standard C extensions
in the system headers.
Somebody with a Mac should try to figure out if we only need it for
mercurial or whether its needed globally...
On Tuesday, January 1, 2013 4:47:47 PM UTC, Robert Zeier wrote:
>
> Yes, everythin
On Mon, Dec 31, 2012 at 5:42 PM, Nils Bruin wrote:
> On Dec 31, 5:35 pm, Robert Bradshaw
> wrote:
> > Yeah, sticking an untrack there certainly seems safe. It looks
> > like PyObject_GC_UnTrack is idempotent, so we don't have to track it
> before
> > going up the dealloc stack. If this fixes it,
On the same machine sage-5.4.1 fails only one test -
sage -t --long -force_lib "devel/sage/sage/misc/package.py"
because I have installed some optional packages.
Rajeev
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To post to this group, send
I just got through shutting down a lot of stuff. It seems that if you
install it, it gets started up.
My problem now is that I am getting read-errors on my swap device. I
bought the card reader at big lot for $6.
I am not sure if it is the reader or the SDHC card. Some SDHC cards don't
work
Yes, everything compiles with this flag.
Thanks!
Am Montag, 31. Dezember 2012 11:08:37 UTC+1 schrieb Volker Braun:
>
> Does it work if you set
>
> CFLAGS="-DOS_OBJECT_USE_OBJC=0"
> export CFLAGS
> make
>
--
You received this message because you are subscribed to the Google Groups
"sage-devel" g
Le 01/01/2013 15:22, Don Harter a écrit :
Maybe rtkit-daemon is the problem. I found this link:
http://askubuntu.com/questions/4/why-is-rtkit-daemon-eating-100-of-my-cpu
It is required by pulse-audio.
I suggest you shut down as many things as you can (pulseaudio, rtkit, X
of course) -- the
I took a backup 16G SDHC card and made it a swap file. The compile then
proceeded farther. Now the whole raspberry pi is locking up. I don't get
a response and the screen is suspended/saved. I don't know if it crashes
or if the processor is overloaded. It just doesn't respond. I ran it
ag
machine: AMD Athlon 64 X2 Dual Core Processor 5000+
operating system: Mandriva linux 2010.2 (32 bit)
i hope i have succeeded in finding the relevant part of the log:
pulling from /home/kosamarton/sage/sage-5.4.1/spkg/build/sage-5.5
searching for changes
no changes found
abort: merging with a wor
On 2013-01-01 05:07, Rajeev Singh wrote:
> Hi,
>
> I have compiled sage-5.5 from source on my ubuntu machine and the
> following tests fail on running 'make ptestlong' -
>
> sage -t --long -force_lib devel/sage/sage/interacts/debugger.py # Time
> out
> sage -t --long -force_lib dev
Le 01/01/2013 05:07, Rajeev Singh a écrit :
I have compiled sage-5.5 from source on my ubuntu machine and the
following tests fail on running 'make ptestlong' -
sage -t --long -force_lib devel/sage/sage/interacts/debugger.py # Time
out
sage -t --long -force_lib devel/sage/sage
Somebody please review
http://trac.sagemath.org/sage_trac/ticket/13887
Currently, the fortran.eval() function compiles a Fortran file in the
current working directory. This should be changed to a temporary
directory instead.
Thanks,
Jeroen.
--
You received this message because you are subscribe
23 matches
Mail list logo
