-
-
Notifications
You must be signed in to change notification settings - Fork 482
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
FPLLL 5.4.0 and FPyLLL 0.5.4 #31025
Comments
Commit: |
Author: Martin Albrecht |
New commits:
|
This comment has been minimized.
This comment has been minimized.
comment:4
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:6
Ta. Fixed. |
Changed keywords from none to sd111 |
This comment has been minimized.
This comment has been minimized.
comment:11
On
|
comment:12
Works fine in Gentoo. I must I never know where to find the appropriate logs in your runs. Sometimes it is easy and sometimes I just get lost. I found the good stuff in the raw logs.
I have a feeling |
comment:13
Is there perhaps a race condition that FPyLLL is built before the new FPLLL? |
comment:14
Replying to @malb:
Looking at the log again, I'd say it looks like it! |
comment:15
This build is accepting a system package
If the new |
comment:16
Same failure also on |
comment:17
If practical at all, I would suggest to upstream to allow the Python bindings to accept a range of fplll versions... |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:19
Updated accordingly, I don't think we can commit to supporting a range of FPLLL versions in FPyLLL |
comment:20
Perhaps then an upper bound for the version needs to be set as well? |
comment:21
Likewise, should we set a range of acceptable |
comment:30
Based on your explanations, I think fpylll's |
comment:32
This doesn't look like an FPLLL issue: https://github.com/mkoeppe/sage/runs/1566871595?check_suite_focus=true#step:7:65 |
comment:33
No, that's not related to this ticket |
comment:34
Replying to @mkoeppe:
As in:
|
comment:35
I would also suggest to add some comments:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
Changed reviewer from https://github.com/mkoeppe/sage/actions/runs/426748847 to Matthias Koeppe |
comment:39
Marking it as critical because some rolling distributions are already picking up 5.4.0 |
Changed branch from u/malb/fplll_5_4_0_and_fpylll_0_5_3_dev0 to |
comment:41
For some reason, even after make distclean, configure is unable to find homebrew install of fplll 5.4.0 (on macOS). Then, the compilation fails on After modifying Should we open a ticket for that ? |
Changed commit from |
comment:42
Replying to @dcoudert:
Yes please. What version of fplll does pkg-config report? |
comment:43
not sure how to get that, but inside config.log, I see:
and I have fplll 5.4.0 installed by homebrew. Follow-up on #31127 |
comment:44
Another follow up in #31146: |
Tarball URLs - see
checksums.ini
CC: @kiwifb
Component: packages: standard
Keywords: sd111
Author: Martin Albrecht
Branch:
29fcb34
Reviewer: Matthias Koeppe
Issue created by migration from https://trac.sagemath.org/ticket/31025
The text was updated successfully, but these errors were encountered: