Open NAThompson opened 3 years ago
I am not sure if you are supposed to build your own MPI compiler on summit. Can you build adios if you force spack to use the system's MPI compiler?
@pnorbert : I'm confused; I didn't tell spack
to build openmpi
; in addition I had an MPI loaded:
ml
Currently Loaded Modules:
1) hsi/5.0.2.p5 2) xalt/1.1.3 3) lsf-tools/2.0 4) DefApps 5) pgi/19.9 6) spectrum-mpi/10.3.0.1-20190611
Do you mean that I should add a compiler to spack?
Here's what I currently have available:
spack compilers
==> Available compilers
-- gcc rhel7-ppc64le --------------------------------------------
gcc@4.8.5
-- pgi rhel7-ppc64le --------------------------------------------
pgi@19.9
You need to point spack to a system MPI and disable building its own. By default ALL dependencies are built from scratch. You only pointed spack to the system compiler.
Here is my setting on Summit (not summitdev):
$ cat /ccs/proj/csc303/adios2-test-suite/summit/spack/etc/spack/packages.yaml
packages:
# concretization preferences
all:
compiler: [gcc/8.1.1]
providers:
mpi: [spectrum-mpi]
# system modules externals.
spectrum-mpi:
modules:
spectrum-mpi@10.3.1.2-20200121%gcc@8.1.1: spectrum-mpi/10.3.1.2-20200121
buildable: False
...
@pnorbert : I get the following when I tried your suggestion:
==> Warning: the attribute "modules" in the "packages" section of the configuration has been deprecated [entry=CommentedMap([('spectrum-mpi@10.3.0.1-20190611%pgi@19.9', 'spectrum-mpi/10.3.0.1-20190611')])]
However, with the following packages.yaml
I was able to succeed in getting a successful compilation:
[nthompson@summitdev-login1]~% cat ~/.spack/packages.yaml
packages:
all:
compiler: [gcc/4.8.5]
providers:
mpi: [spectrum-mpi]
spectrum-mpi:
modules:
spectrum-mpi@10.3.0.1-20190611%gcc@4.8.5: spectrum-mpi/10.3.0.1-20190611
buildable: False
Strangely, the spack package for adios2 succeeds without this file, even though I was unable to see any significant differences in the spack info
log.
@NAThompson system MPI libraries are required, as @pnorbert suggested, as your package might get out of sync when they do system updates on Summit.
To reproduce:
I would attach the build log, but it gives the same information as the console.