Re: [RFC] sagemath: update to 10.0.rc3.

[tornaria <tornaria@users.noreply.github.com>]

[-- Attachment #1: Type: text/plain, Size: 2113 bytes --]

New comment by tornaria on void-packages repository

https://github.com/void-linux/void-packages/pull/43659#issuecomment-1548642773

Comment:
> With `sage -t --long`, there are only two failures: [fail1.log](https://github.com/void-linux/void-packages/files/11482001/fail1.log) [fail2.log](https://github.com/void-linux/void-packages/files/11482005/fail2.log) while `structure/coerce_actions.pyx` passes all tests [fail3.log](https://github.com/void-linux/void-packages/files/11482011/fail3.log)

Can you try building python3 natively? When built in cross, the configure step gives:
```
checking for broken sem_getvalue... yes
```
which then causes this `NotImplementedError`.

Please have a look at this configure check --- if you get "no" there I expect your natively built python3 will work ok.

If this works then the fix for cross building python3 is adding  `ac_cv_broken_sem_getvalue=no` to `configure_args` (you could try building python3 cross on a x86_64 with this change, then see if the resulting pkg works, then submit a PR for python3 so the pkg in void repos works out of the box). The problem is that this is checked by compiling and running a program which won't work in cross -- but if we know sem_gevalue is ok in all of our arches, we can always force it (otherwise, force it in the arches that are known to work).

----

What about the failures in `structure/coerce_actions.pyx`? Is this passing with `--long` and failing without it? Is it failing only for a particular value of `--random-seed`?

BTW: you can use xbps-src to run checks in selected files and/or with a chosen random seed. Just create a file `sagemath-check` in your `void-packages` root directory. You can add filenames and options for the sage check step. E.g.
```
--random-seed=278209243980132307357977126905193403766
src/sage/parallel/map_reduce.py
src/sage/sets/recursively_enumerated_sets.pyx
src/sage/structure/coerce_actions.pyx
```

Add `--long` if you want, etc. You can use `#` to comment. If the file is "empty" (as in not existent or everything is commented out) then checks run normally.