2.6.1 released on 2024-12-15.
Thanks for reminding. It is in testing here for some days already. But due to changed test environment there I get a quite a lot of test failures and am looking to sort it out before bringing the ebuild into the tree.
Did some further investigation. See below for results. There are 285 tests in the testsuite. Running the tests as is with GCC-14 and LLVM-19 only 187 passes. The rest (98) ends 'failed' or with 'error'. - 29 tests are resulting in error due to 'dynamic exception specification' not allowed with >=ISO C++17. These can be fixed by forcing to run the tests with -std=c++14. - 18 tests failed due to handling of spaces around '<...>' pairs in templates, e.g. failed 'assert 'vector<int>' == 'vector< int >'' Seems as upstream is working on these one. - 13 tests failed and 37 with error with the same error message from the parser: 'Unable to find out actual class definition: 'type'.' It further showed that these last tests fails only with >=gcc-14 as active compiler. GCC-11 and GCC-13 was tested successful.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b7b09f9fa3636474af90e386df66f2e4609640e7 commit b7b09f9fa3636474af90e386df66f2e4609640e7 Author: Thomas Beierlein <tomjbe@gentoo.org> AuthorDate: 2025-01-10 16:38:57 +0000 Commit: Thomas Beierlein <tomjbe@gentoo.org> CommitDate: 2025-01-10 16:42:28 +0000 dev-python/pygccxml: add 2.6.1 Had to deselect 109 of 288 tests. See bug for more information. Bug: https://bugs.gentoo.org/947191 Signed-off-by: Thomas Beierlein <tomjbe@gentoo.org> dev-python/pygccxml/Manifest | 1 + .../files/pygccxml-2.6.1-xml_generator.patch | 9 +++ dev-python/pygccxml/pygccxml-2.6.1.ebuild | 70 ++++++++++++++++++++++ 3 files changed, 80 insertions(+)
