On Fri, Nov 1, 2019 at 1:15 PM John H Palmieri
wrote:
> If you have the time, could you try uninstalling Xcode and then
> reinstalling it? You might also try uninstalling and reinstalling
> homebrew's gcc and any other homebrew components that are relevant to Sage.
> There may be some remnants of
Xcode 11 contains once again broken system headers so compiling any version
of gcc/gfortran fails. This is
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90835
Xcode 11 is now also pushed to Mojave so OSX 10.14 is now broken as well.
Presumably you can work around it by manually installing Xcode
Thank you. I should have done that in my first posting. I attach the
crash report.
I have a suspicion that this is not going to be sufficient, but at least
you can tell me what I should post next.
On Saturday, November 2, 2019 at 2:19:33 AM UTC-4, Dima Pasechnik wrote:
>
> the error is not in
Could you please explain both (just high level steps, assuming my module
are standalone python scripts that imports nothing other than sage/standard
library)?
On Saturday, November 2, 2019 at 6:04:16 AM UTC-7, Dima Pasechnik wrote:
>
> there are two mostly independent tasks - how to modify/impro
Le samedi 2 novembre 2019 13:56:47 UTC+1, Keren Shao a écrit :
>
> It looks like #1 is still open (and I cannot find any implementation
> from the documentation.) Can anyone confirm its status with me?
>
> Also, I am trying understand how to contribute, say a script for
> Murnaghan-Nakayama f
there are two mostly independent tasks - how to modify/improve Sage code,
and how to contribute these changes to Sage.
which of the two would you like to be explained?
On Sat, 2 Nov 2019, 14:56 Keren Shao, wrote:
> It looks like #1 is still open (and I cannot find any implementation
> from
It looks like #1 is still open (and I cannot find any implementation
from the documentation.) Can anyone confirm its status with me?
Also, I am trying understand how to contribute, say a script for
Murnaghan-Nakayama formula without dependencies, to SageMath but this link
http://doc.sagemat
has upstream updated the package?
On Sat, 2 Nov 2019, 11:58 Nico Van Cleemput,
wrote:
> Yes, I was actually also looking at it just this morning. It's been a
> while since I did any Sage development, but I'll try to fix this. Will
> first have to reread how the packages work these days.
>
> Nico
I have opened #28688 to fix buckygen.
On Sat, 2 Nov 2019, 11:58 Nico Van Cleemput,
wrote:
> Yes, I was actually also looking at it just this morning. It's been a
> while since I did any Sage development, but I'll try to fix this. Will
> first have to reread how the packages work these days.
>
>
Yes, I was actually also looking at it just this morning. It's been a while
since I did any Sage development, but I'll try to fix this. Will first have
to reread how the packages work these days.
Nico
Op za 2 nov. 2019 om 10:50 schreef David Coudert :
> File splay.c has changed in nauty (at leas
File splay.c has changed in nauty (at least in 26r12). The main difference
is
- static SPLAYNODE*
- SPLAY_DELETE(SPLAYNODE **to_root, SPLAYNODE *p)
+ void
+ SPLAY_DELETE(SPLAYNODE **to_root, SPLAYNODE *p)
With this change, I can do gcc -O3 -std=c89 buckygen.c -o buckygen
So upstream must be u
11 matches
Mail list logo
