New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix flintxx development #20281
Comments
Branch: u/rws/fix_flintxx_development |
New commits:
|
Commit: |
Author: Ralf Stephan |
comment:3
pynac doesn't use flint. |
Branch pushed to git repo; I updated commit sha1. New commits:
|
Reviewer: Jeroen Demeyer |
comment:7
Thanks. |
comment:8
I personally don't think the fix you submitted upstream is any good. You are probably configuring with |
comment:9
Possibly, depending on your includes it should have been |
comment:10
It is a complete mystery to me how you get the idea that I submitted anything upstream. I merely reported the issue at flintlib/flint#217. Consequently your remarks should be added there. |
comment:11
Right I saw "reported by Ralph Stephan and fixed by ..." and I have conflated things a little bit. I guess I thought you worked together. But right it is just that I don't think it is a good solution in my opinion. |
Changed branch from u/rws/fix_flintxx_development to |
Current flint-2.5.2 is from last year and lacks a recent fix from git master addressing compile errors of flintxx headers. This ticket patches Sage's flint to enable Pynac development with flintxx, the C++ API of flint.
flintlib/flint@c0768dc
Component: packages: standard
Author: Ralf Stephan
Branch/Commit:
45ebadb
Reviewer: Jeroen Demeyer
Issue created by migration from https://trac.sagemath.org/ticket/20281
The text was updated successfully, but these errors were encountered: