commit: 758e532b21964bf06622414a13efe2439b108723 Author: Marek Szuba <marecki <AT> gentoo <DOT> org> AuthorDate: Fri Jul 16 11:31:49 2021 +0000 Commit: Marek Szuba <marecki <AT> gentoo <DOT> org> CommitDate: Fri Jul 16 11:43:31 2021 +0000 URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=758e532b
profiles/base: remove USE="int64 metis" mask from sci-libs/pastix Signed-off-by: Marek Szuba <marecki <AT> gentoo.org> profiles/base/package.use.mask | 10 +--------- 1 file changed, 1 insertion(+), 9 deletions(-) diff --git a/profiles/base/package.use.mask b/profiles/base/package.use.mask index af41a8e0062..925b60a9c4d 100644 --- a/profiles/base/package.use.mask +++ b/profiles/base/package.use.mask @@ -10,20 +10,12 @@ # Several known issues (possibly with older pastix versions as well but # in v6 they result in clear errors): # * CUDA support needs testing, may or may not work as it is; -# * All sci-libs/scotch ebuilds currently in the tree seem to always use -# 32-bit integer representation, even when built USE=int64. Seeing as -# metis ordering has got more complicated issues (see below), just -# stick with 32 bits for now; -# * sci-libs/metis currently always uses whatever integer representation -# is native to the target architecture even though upstream allows for -# using 32-bit integers on 64-bit arches, this will have to be implemented -# so that pastix can pass int64? to it; # * With MPI enabled two tests fail (when linked against openmpi, at least) # due to incorrect implementation of either MPI support itself or # said tests - example_drv_facto0_d_reentrant tries to initialise MPI # more than once, test_bvec_gemv_tests calls MPI_Query_thread() after # invocation of MPI_FINALIZE. ->=sci-libs/pastix-6.0.0 cuda int64 metis mpi +>=sci-libs/pastix-6.0.0 cuda mpi # Alfredo Tupone <[email protected]> (2021-06-27) # lto does not work on dev-lang/gnat-gpl-2021
