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.
>
>
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
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
OK, the answer is below:
The file splay.c is actually taken from Nauty, so that issue should be
resolved there. The most obvious solution is to not compile this as C99,
but as C89 since that is what buckygen was written in.
So, I can mail this to Brendan McKay to ask to solve this, but since
Well, upstream sits at another desk in my office, so I will ask when he
gets in.
Nico
Op di 29 okt. 2019 09:29 schreef Dima Pasechnik :
> clang is unhappy about C standards violations. E.g. this is what I get
> with clang 7:
>
> cc -O4 buckygen.c -o buckygen
> cc: warning: -O4 is equivalent to
clang is unhappy about C standards violations. E.g. this is what I get
with clang 7:
cc -O4 buckygen.c -o buckygen
cc: warning: -O4 is equivalent to -O3 [-Wdeprecated]
In file included from buckygen.c:272:
./splay.c:139:6: warning: implicit declaration of function
'outputnode' is invalid in C99
buckygen is a pure C package, so I doubt that this has anything to do with
the switch to Python 3. Do you have any more information about the fail
build, because here it built fine.
Nico
Op ma 28 okt. 2019 om 23:02 schreef John H Palmieri :
> With a Python 3 build of Sage on OS X 10.14.6, I
With a Python 3 build of Sage on OS X 10.14.6, I decided to install as many
optional and experimental packages as I could. The results:
*Optional:*
- the following packages failed to build, and the reason wasn't completely
obvious:
awali
buckygen
cbc
gambit
gdb
mpi4py
- the following
