several fixes for SimNIBS 4.6.0 easyconfig - #26579
Conversation
…on in SimNIBS 4.6.0 easyconfig
|
@pavelToman Do you remember why you didn't use a source tarball instead of a pre-built wheel for |
|
@boegel No strict technical requirement. It was used because PyTorch pins |
I'm checking if that works right now (installing |
And of course there's one failing tests... At least that's a known issue, with a fix: I'll try applying a patch to the |
1054ab8 to
b92b2ec
Compare
…ce sanity check for SimNIBS 4.6.0
|
@boegelbot please test @ jsc-zen3 |
|
@boegel: 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 5169752266 processed Message to humans: this is just bookkeeping information for me, |
|
Test report by @boegel |
|
Test report by @boegelbot |
(created using
eb --new-pr)Part 1: Make sure that vendored Eigen is used when building ml-dtypes extension in SimNIBS 4.6.0 easyconfig
fix for problem that manifests like:
This didn't happen before because
$CPLUS_INCLUDE_PATHwas being updated by theEigeneasyblock to include the location to the Eigen header files, but this was changed in:Note: another fix for this
SimNIBSeasyconfig will be required, because later on theteststep for thesympyextension is failing with:That happens because
sympyis being installed from awhlfile, so there's no unpacked source tarball forsympy, as expected by thetest_stepmethod of thesympyeasyblock...This issue went under the radar before because of a bug in the
sympyeasyblock, which got fixed in:test_stepnot failing in sympy easyblock easybuild-easyblocks#4172Part 2: Fix failing test for
sympydue to incompatibility withllvmlite0.45+fixed via patch that was applied upstream:
Part 3: RPATH sanity check fails for
lib/libgmsh.so.4.14(WIP)This occurs because
gmshextension in SimNIBS is installed through binary wheel:I'm not sure how this wasn't a problem before, since the easyconfigs was contributed pretty recently ( #26091)There's a
patchelfcommand listed inpostinstallcmdsthat works around this, but it was accidentally "disables" by the changes in a follow-up PR (#26181), because of a missing,after thepatchelfcommand...