Drop ILP64 from lapacke in 2025b as flexiblas doesn't support it#24231
Conversation
|
Test report by @Thyre |
|
@boegelbot please test @ jsc-zen3 |
|
Test report by @Thyre |
|
@Thyre: Request for testing this PR well received on jsczen3l1.int.jsc-zen3.fz-juelich.de PR test command '
Test results coming soon (I hope)... Details- notification for comment with ID 3400605652 processed Message to humans: this is just bookkeeping information for me, |
|
Test report by @boegelbot |
|
@boegelbot please test @ jsc-zen3 |
|
@Thyre: Request for testing this PR well received on jsczen3l1.int.jsc-zen3.fz-juelich.de PR test command '
Test results coming soon (I hope)... Details- notification for comment with ID 3402180211 processed Message to humans: this is just bookkeeping information for me, |
|
Test report by @boegelbot |
|
Going in, thanks @Micket! |
…asyconfigs into 20251014005116_new_pr_FlexiBLAS345
(created using
eb --new-pr)LAPACK sneakily added a massive update in the 3.12.1 "bugfix" release. This made LAPACKE get build with requirement on
_64suffixed ilp64 symbols.Flexiblas doesn't support these at all, so, which means LAPACKE from this flexiblas is completely useless; linking to flexiblas isn't sufficient.
This is currently breaking testing in my LAPACK++ PR #24135 because of these unresolved symbols, rendering -llapacke linking broken.