After the latest update of spack tree, I am failing to build openmpi on ppc64le system. I am pretty sure that this has not been occurring before, but I am struggling to find any changes in packages or my own environment which might be causing this. The issue is binuitls, libiconv and gettext.
My initial intention was to fix openmpi build for ppc64le, as the default setting weren't working as expected in comparison with manually built variant, but now I am stuck much earlier on.
Please advise.
Steps to reproduce the issue
$ spack install openmpi@3.1.4 schedulers=lsf fabrics=verbs,mxm,ucx
...
==> No patches needed for binutils
==> Building binutils [AutotoolsPackage]
==> Executing phase: 'autoreconf'
==> Executing phase: 'configure'
==> Executing phase: 'build'
==> Error: ProcessError: Command exited with status 2:
'make' '-j16'
14 errors found in build log:
...
>> 4723 /usr/bin/ld: /gpfs/users/shared/spack/opt/spack/linux-rhel7-power8le/gcc-9.2.0/gettext-0.20.1-y6akw7puzlfgbsffvajtlqvhldovl6gi/lib/libintl.so: undefined reference to symbol 'libiconv
'
>> 4724 /gpfs/users/shared/spack/opt/spack/linux-rhel7-power8le/gcc-9.2.0/libiconv-1.16-mnukz37aj2mv7nk4s6w3233y5u5met6b/lib/libiconv.so.2: error adding symbols: DSO missing from command lin
e
>> 4725 collect2: error: ld returned 1 exit status
>> 4726 make[4]: *** [dwp] Error 1
...Platform and user environment
$ uname -a
Linux sandbox01 3.10.0-957.21.2.el7.ppc64le #1 SMP Tue May 28 09:29:10 UTC 2019 ppc64le ppc64le ppc64le GNU/Linuxu
$ lsb_release -d
Description: Red Hat Enterprise Linux Server release 7.6 (Maipo)
After the latest update of spack tree, I am failing to build openmpi on ppc64le system. I am pretty sure that this has not been occurring before, but I am struggling to find any changes in packages or my own environment which might be causing this. The issue is binuitls, libiconv and gettext.
My initial intention was to fix openmpi build for ppc64le, as the default setting weren't working as expected in comparison with manually built variant, but now I am stuck much earlier on.
Please advise.
Steps to reproduce the issue
Platform and user environment