Comments (14)
In particular, this fails on v3.1.3
(but works on main
)
./configure --host core2-linux-gnu
checking build system type... x86_64-apple-darwin21.6.0
checking host system type... Invalid configuration `core2-linux-gnu': machine `core2-unknown' not recognized
configure: error: /bin/sh ./config/config.sub core2-linux-gnu failed
from flint.
and in v3.1.3
we can do
./configure --enable-arch=core2
from flint.
Not sure why the branches have diverged, but why would that be bad?
from flint.
In particular, this fails on
v3.1.3
(but works onmain
)./configure --host core2-linux-gnu checking build system type... x86_64-apple-darwin21.6.0 checking host system type... Invalid configuration `core2-linux-gnu': machine `core2-unknown' not recognized configure: error: /bin/sh ./config/config.sub core2-linux-gnu failed
Yes, because I changed the build system to be more GMP-like. I think it is better to push everything into --host
instead of some non-standard option --enable-arch
.
from flint.
Not sure why the branches have diverged, but why would that be bad?
It leads to several inconsistencies:
- different options for ./configure
- different workflows
I would expect the release versions to be tagged on the main branch, not on some other branch.
But perhaps, what I am struggling with is what is the purpose of the branch flint-3.1
?
from flint.
I would expect the release versions to be tagged on the main branch, not on some other branch. But perhaps, what I am struggling with is what is the purpose of the branch
flint-3.1
?
Bill made new branches for each minor version, which is why we still do it today. I am all for removing those branches.
It leads to several inconsistencies:
- different options for ./configure
This is because I have changed the options in configure.ac
. If you go back two years ago, the options are very much different. I have tried my best to streamline them (if you remember, it used to be a single shell-script that did not have a lot of checks or logging features), but I would still class it is a working project which is why we have these inconsistencies between the releases.
from flint.
I would expect the release versions to be tagged on the main branch, not on some other branch. But perhaps, what I am struggling with is what is the purpose of the branch
flint-3.1
?
We have spun off such branches so that we can do the final release polish (and post-release bug patching) without interference from unstable development on the main branch. I'd be happier with having a strictly linear history where releases are just tags on the main branch (this is what I did with Arb), but this is difficult as long as patch releases are wanted/needed.
from flint.
I think we are all aligned, then.
I agree that a linear history can be hard.
Do you think it is possible or desirable to aim at updating the release branch flint-3.x
when patch releases are wanted/needed through cherry-pick?
At the end of the day, I am just aiming for some consistency, as for me it was quite confusing why we were still running old workflows and supporting different options for ./configure
in the releases.
from flint.
I think we are all aligned, then. I agree that a linear history can be hard. Do you think it is possible or desirable to aim at updating the release branch
flint-3.x
when patch releases are wanted/needed through cherry-pick?
I cannot recall doing anything other than cherry-picking. Could the divergence be explained by conflicts or something when cherry-picking?
At the end of the day, I am just aiming for some consistency, as for me it was quite confusing why we were still running old workflows and supporting different options for
./configure
in the releases.
What do you mean by old workflows?
from flint.
git diff --stat upstream/flint-3.1..upstream/main
.github/codecov.yml | 4 +
.github/workflows/CI.yml | 175 ++++++++++--
.github/workflows/push_CI.yml | 65 +----
.github/workflows/release.yml | 124 +++++++--
.gitignore | 10 +-
AUTHORS | 4 +-
CMake/FindCBLAS.cmake | 33 ++-
CMake/Findgmp.cmake | 66 +++++
CMake/Findmpfr.cmake | 57 ++++
CMake/cmake_config.h.in | 5 +-
CMakeLists.txt | 166 +++++++++---
...
https://gist.github.com/edgarcosta/1f6f7b9638a39e9b33f0e03dd5cf75a1
from flint.
We are in 3.2.0-dev though
from flint.
I do not follow. Can you elaborate a bit more? Are you referring to the VERSION file?
from flint.
I believe next version we will release is 3.2.0, so comparing against 3.1.X doesn't really make sense I believe.
from flint.
I finally understood where I misunderstood the whole thing ๐
I am used to the old schedule release where "minor versions" like 2.x
were released at the pace of major versions, and thus I still think of "3.1.x" as minor versions, instead of just patches on top of 3.1
, and thus why it is has a minimal number of commits on top of the previous version.
from flint.
Related Issues (20)
- fmpz_mpoly_pfrac_init: internal error HOT 7
- Worklist for nfloat HOT 3
- SIMD abstraction layers HOT 5
- Problems with Riemann theta functions HOT 44
- 3.1.3 isn't in the Downlioads section of the website: https://flintlib.org/downloads.html HOT 2
- Document need for libtool
- Improve parallel Schรถnhage-Strassen multiplication
- file padic_types.h not getting installed HOT 2
- Test failures when compiled with GCC graphite flags HOT 5
- #error machine_vector.h not implemented on AMD Ryzen 7 without forcing --enable-avx HOT 14
- Segmentation Fault in Fortran-C Interoperability when Using Arb Library for Complex Integration HOT 2
- Error finding PkgConfig while installing Flint package using CMake on Windows HOT 1
- Add a function to compute b/sqrt(a)
- Multivariate rational functions over the integers mod n HOT 3
- AVX and nmod HOT 8
- FLINT license should be stated on the FLINT website HOT 1
- Gentoo Linux: sci-mathematics/flint-3.1.3_p1 QA Notice: Package triggers severe warnings which indicate that it may exhibit random runtime failures. HOT 1
- Missing functions in `fq_default` HOT 1
- `fq_default_poly_evaluate_fq_default` with context type `FMPZ_MOD` segfaults
- `make check` failing at `sub_dddmmmsss` under macOS (aarch64-apple-darwin22.6.0)
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. ๐๐๐
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google โค๏ธ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from flint.