Package: metis
Followup-For: Bug #961183
Hi Fred, I guess the simple reason why there's no pkgconfig for Metis
is that upstream does not provide one.
We could add one ourselves easily enough. But SCOTCH-Metis
compatibility would want to be taken into consideration. Historically
SCOTCH-Metis nev
Hello,
why there is no pkgconfig files provided with metis and metis64.
this simplify the configuration of packages depending on these libraries.
Cheers
Fred
On 2021-06-13 07:02, Anton Gladky wrote:
Hi Drew,
Would you like me to push to salsa (experimental branch) for
inspection?
Yes, please.
OK, pushed to experimental branch.
Bring the question of REALTYPEWIDTH to mind (the size of floating point
numbers). The "64-bit support" in other packa
Hi Drew,
> Would you like me to push to salsa (experimental branch) for inspection?
Yes, please.
Anton
Am So., 13. Juni 2021 um 01:24 Uhr schrieb Drew Parsons :
> Package: metis
> Followup-For: Bug #961183
>
> Hi Anton, I've prepared packaging for a 64-bit that I'm happy to push
> (and upload
Package: metis
Followup-For: Bug #961183
Hi Anton, I've prepared packaging for a 64-bit that I'm happy to push
(and upload).
Would you like me to push to salsa (experimental branch) for inspection?
Drew
Package: metis
Followup-For: Bug #961183
Control: affects -1 libscotchmetis-dev
Also scotch-metis will need to be updated to match.
Package: metis
Followup-For: Bug #961183
Control: affects -1 libdeal.ii-dev libparmetis-dev src:suitesparse src:deal.ii
src:freefem++ src:gmsh src:netgen src:parmetis src:superlu-dist src:syrthes
Here is the list of affected packages identified by
apt-rdepends -r libmetis-dev libmetis5
libme
Doing it through a formal transition request is sensible. There's a
backlog of numerical library upgrades (some still in the NEW queue)
waiting for bullseye to get released. Perhaps we can run this transition
at the same time as the others, process them all as a bulk transition.
We'll set it u
Well, theoretically we can do it. But we need to do some kind
of a transition for all dependencies.
Regards
Anton
Am Sa., 5. Juni 2021 um 13:36 Uhr schrieb Drew Parsons :
> ...
> I think the best solution is to "break" the builds of client
> applications by moving the standard header from /usr
Package: metis
Followup-For: Bug #961183
64-bit integers are now available for several libraries.
64-bit PETSc is able to use 64-bit SuperLU-Dist, which we don't
currently have.
64-bit SuperLU-Dist requires 64-bit metis.
In principle 64-bit metis is simple to configure: set IDXTYPEWIDTH to
64 i
Should add a caveat on the urgency: this bug report is Wishlist, really.
That's because mumps uses scotch rather than metis. This is because
parmetis is not available (not-free).
If the licence for parmetis became free, then we would use it with mumps
(and would be looking for a 64-bit build)
Source: metis
Severity: normal
We're discussing introducing a 64 bit-build for the computational
stack. This refers to 64-bit addressing to cells in meshes, etc.
c.f. Bug#953116 (petsc)
Bug#961108 (openmpi)
https://lists.debian.org/debian-science/2020/05/msg00051.html
BLAS is already 64-bit enab
12 matches
Mail list logo
