Martin R. Albrecht
Martin R. Albrecht
In 5.3.3 we did a bunch of `pkg-config` stuff so that would point in the right direction.
Is there like a docker image or something with SLES 15 SP1 SuSE Linux System and some instructions of how to get to the failure? I could try to reproduce...
I think a five hour wait time for CI is asking a bit too much. Also, this should be for FPyLLL not FPLLL?
We've switched to GitHub Actions now. I'd be up for merging this triggered manually only, i.e. on `workflow_dispatch`.
That would be great!
Oh, another thing: shouldn't this be against FPyLLL? Typically, we release new versions of FPLLL and FPyLLL together and the latter depends on the former.
Looks like the failures are merely bloody clang. I'm happy to merge patch to make things work on Windows, but I'd be rather hesitant to make any claim on Windows...
I'd just skip building `sieve_main`, it's been superseeded by g6k.
We do use PRs. However, we don't have the expertise to address issues that might arise. Thus, there's a real chance we'd simply drop or ignore reports from appveyor. The...
Then, I'm happy :) Thanks!