-
-
Notifications
You must be signed in to change notification settings - Fork 481
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
spkg-configure for fplll #29245
Comments
Author: Michael Orlitzky |
Commit: |
This comment has been minimized.
This comment has been minimized.
Branch: u/mjo/ticket/29245 |
New commits:
|
comment:2
Could you add |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:4
Sure. I'll add the others if people can tell me what to stick in the text files. For example I'm pretty sure you need both the main package and -dev on Debian, but who knows. I'm also pretty sure that someone is going to tell me the pc file is missing somewhere and make me do a header/library search... |
comment:5
https://repology.org/ has the info you need |
comment:6
And this all can be tested using tox. |
comment:7
on debian one needs
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
Reviewer: Dima Pasechnik |
comment:9
Debian fplll package is broken - fplll/pruner/ headers are missing.
I propose to include a check for this header in the macro. |
comment:10
In fact, fplll-5.2.1 does not have that header, they only appear in fplll-5.3 so, just updating the minimal version will do. |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:12
Replying to @dimpase:
Thanks, fixed. |
Changed branch from u/mjo/ticket/29245 to |
fplll ships a pkg-config file, is slow to build, and has only one dependency that was already spkg-configurified.
It is packaged for a few distros, so let's use it.
CC: @embray @dimpase @mkoeppe @isuruf @kiwifb
Component: build: configure
Author: Michael Orlitzky
Branch/Commit:
7fc917b
Reviewer: Dima Pasechnik
Issue created by migration from https://trac.sagemath.org/ticket/29245
The text was updated successfully, but these errors were encountered: