Add option to impi easyblock to rebuild Fortran 2008 bindings#3678
Add option to impi easyblock to rebuild Fortran 2008 bindings#3678boegel merged 7 commits intoeasybuilders:developfrom
Conversation
The Fortran 2008 bindings shiped with Intel MPI can cause compilation failures when using `CLASS(*)` arguments. This bug is known, and a solution for this given in the following thread: https://community.intel.com/t5/Intel-MPI-Library/MPI-f08-with-polymorphic-argument-CLASS/m-p/1590421 However, this bug is not yet included in Intel MPI releases to preserve backwards compatibility. Instead, one needs to rebuild the bindings themselves and replace them. Add an option for this, and leave it disabled by default. EasyConfigs can then decide if they want to rebuild these modules, or preserve the backwards compatibility. Signed-off-by: Jan André Reuter <j.reuter@fz-juelich.de>
Signed-off-by: Jan André Reuter <j.reuter@fz-juelich.de>
Signed-off-by: Jan André Reuter <j.reuter@fz-juelich.de>
…ethod of impi easyblock
move code to rebuild Fortran 2008 bindings to separate method in impi easyblock + use variables for paths used multiple times
|
@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 2790614807 processed Message to humans: this is just bookkeeping information for me, |
|
Test report by @boegelbot Overview of tested easyconfigs (in order)
Build succeeded for 2 out of 2 (2 easyconfigs in total) |
The Fortran 2008 bindings shiped with Intel MPI can cause
compilation failures when using
CLASS(*)arguments.This bug is known, and a solution for this given in the following
thread:
https://community.intel.com/t5/Intel-MPI-Library/MPI-f08-with-polymorphic-argument-CLASS/m-p/1590421
However, this bug is not yet included in Intel MPI releases to
preserve backwards compatibility. Instead, one needs to
rebuild the bindings themselves and replace them.
Add an option for this, and leave it disabled by default.
EasyConfigs can then decide if they want to rebuild these modules,
or preserve the backwards compatibility.