Hello Alexandre,
the Flame definition (toolchains/linalg/flame.py) expects a "LAPACK" module
besides the "FLAME" module,
TC_CONSTANT_FLAME = 'FLAME'
class Flame(Lapack):
"""Less trivial module, provides FLAME support."""
LAPACK_MODULE_NAME = ['FLAME'] + Lapack.LAPACK_MODULE_NAME # no super()
LAPACK_LIB = ['lapack2flame', 'flame'] + Lapack.LAPACK_LIB # no super()
LAPACK_FAMILY = TC_CONSTANT_FLAME
When I defined a similar toolchain a while back I copied it to a
separate toolchains/linalg/libflame.py definition and changed it to
TC_CONSTANT_LIBFLAME = 'libFLAME'
class libFLAME(Lapack):
"""Less trivial module, provides libFLAME support."""
LAPACK_MODULE_NAME = ['libFLAME']
LAPACK_LIB = ['flame'] # includes lapack2flame, as long as libFLAME is
configured with --enable-lapack2flame
LAPACK_FAMILY = TC_CONSTANT_LIBFLAME
and then used "libFLAME" in the toolchain definition and easyconfigs.
But I don't think the original toolchains/linalg/flame.py is actually used
anywhere (?), so maybe that one could be updated instead...
Hope this helps,
Miguel
On Tue, Oct 6, 2020 at 1:32 AM Strube, Alexandre <[email protected]>
wrote:
> Hello EasyBuilders,
>
> I’m having difficulty with creating a new toolchain based on BLIS and
> libFLAME, for AMD machines (our new JUWELS-BOOSTER).
>
> When I try so, I get this:
>
> == FAILED: Installation ended unsuccessfully (build directory:
> /dev/shm/strube1/SciPyStack/2020-gcccoreblis/gcccoreblis-9.3.0-2.2-amd-amd-Python-3.8.5):
> build failed (first 300 chars): List of toolchain dependency modules and
> toolchain definition do not match (found ['GCCcore/.9.3.0',
> 'BLIS/.2.2-amd', 'FLAME/2.2-amd'] vs expected {'LAPACK', 'GCCcore',
> 'FLAME', 'BLIS'}) (took 7 sec)
>
> With the files attached.
>
> Any hints?
>
>
>
