What can we do about it? Is there an upstream tracker? Are they aware at all?
2.6.0 is supposed to have support for >=6.0? https://github.com/Cantera/cantera/commit/0706ab32c4f6577b4d12055a6daad8116bc2aab9 git master even dropped support for 2.x already: https://github.com/Cantera/cantera/commit/7510abe4b0ca09b368026d287b6870a514666af1
It's actualy supports sundials-6. The restriction is for cantera[lapack] only: on cantera-2.6.0 I don't remember any problems but then I found that cantera[lapack] fail tests with >sundials-5.3. The fastest resolution is drop USE=lapack from sci-libs/cantera. With python3.11 and EAPI8 bump maybe together I have old build.log files with failed tests but there are too many failures so I didn't summarize them that time to report to upstream.
It doesn't have to be solved *fast*, it should be eventually. And for that matter I was asking if there actually is an upstream report to track, or if the same test failure was actually reproduced with 2.6.0 (as said, upstream even dropped 2.x support meanwhile so possibly they already fixed something in git master).
Agree. I will report it after retesting. Lapack support is optional while sundials is permanent dependency. I currently retest build and encountered the pyhon interface build problem due to pip version checking :( It's used to install only.
I was wrong with `sci-libs/cantera2.6.0-r1[python] `- it's was just warning (about pip version check - I mislead myself) and compilation is successfully done. But the problem for `sci-libs/cantera2.6.0-r1[lapack]` is presented if built against `dev-libs/sundials-6.2.0` due to CVodesIntegrator::step error. All tests are passed if `dev-libs/sundilas-5.2.0` is used. All tests are passed for `sci-libs/cantera2.6.0-r1[-lapack]` built against `dev-libs/sundials-6.2.0` like with `dev-libs/sundials-5.2.0`. The last issue is reported now: https://github.com/Cantera/cantera/issues/1419 I can't check current upstream-main build due to other issue: https://github.com/Cantera/cantera/issues/1418 - i.e. shared libcantera.so.3.0.0 library tries to be linked against static /usr/lib64/liblapack.a. It's strange that early for Cantera 2.6.0 even static libcantera.a didn't require static liblapack.a on built (static libs are removed in src_install).
It's seem that issue is related Sundials built with gcc 11.x: if sundials 5.2, 5.8 or 6.2 (presented in repo) are built with USE="lapack int64XL" then it's lapack tests are failed. And there are no test failures if built it with gcc 12.x and cantera[lapack] tests are passed too this case. The sundials 6.5.0 isn't affected this issue for me both gcc 11.x and gcc 12.x (with cantera too). I will collect appropreate build.log files and will open the issue for sci-libs/sundials. The sundials 6.5.0 bump will resolve the issue both for sundials[laoack,int64] and cantera[lapack].
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=bfc20ea17c60b59183334f78da824b39077ebcae commit bfc20ea17c60b59183334f78da824b39077ebcae Author: Sergey Torokhov <torokhov-s-a@yandex.ru> AuthorDate: 2022-12-27 21:32:46 +0000 Commit: Andrew Ammerlaan <andrewammerlaan@gentoo.org> CommitDate: 2023-01-30 09:59:56 +0000 sci-libs/cantera: 2.6.0-r2 revision bump 1. EAPI8 bump 2. Add Python 3.11 compat, rm deprecated open U option (upstream patch) 3. Rectrict USE=lapack with >=sci-libs/sundials-6.5.0[lapack?] 4. Set std=c++14 to avoid build fail with upcoming dev-libs/boost-1.82 and sci-libs/sundials-6.5.0 detection (the last is strange). Bug: https://bugs.gentoo.org/888667 Closes: https://bugs.gentoo.org/888527 Closes: https://bugs.gentoo.org/890427 Signed-off-by: Sergey Torokhov <torokhov-s-a@yandex.ru> Signed-off-by: Andrew Ammerlaan <andrewammerlaan@gentoo.org> sci-libs/cantera/cantera-2.6.0-r2.ebuild | 151 +++++++++++++++++++++ ...ntera-2.6.0_drop_deprecated_open_U_option.patch | 49 +++++++ 2 files changed, 200 insertions(+)
