Your message dated Mon, 05 Sep 2022 11:49:52 +0000
with message-id <e1ovabw-008k94...@fasolo.debian.org>
and subject line Bug#1017356: fixed in pmix 4.2.0+really.4.1.2-3
has caused the Debian Bug report #1017356,
regarding cp2k: FTBFS: symbol lookup error: 
/usr/lib/x86_64-linux-gnu/openmpi/lib/openmpi3/mca_pmix_ext3x.so: undefined 
symbol: pmix_value_load
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1017356: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017356
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cp2k
Version: 9.1-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs

Hello,

cp2k fails to build on amd64:

cd tools/manual && \
        /home/merkys/cp2k-9.1/exe/*/cp2k.psmp --xml && \
        saxonb-xslt -o index.html -ext:on cp2k_input.xml cp2k_input.xsl
orted: symbol lookup error:
/usr/lib/x86_64-linux-gnu/openmpi/lib/openmpi3/mca_pmix_ext3x.so:
undefined symbol: pmix_value_load
[barriere:463328] [[INVALID],INVALID] ORTE_ERROR_LOG: Unable to start a
daemon on the local node in file
../../../../../../orte/mca/ess/singleton/ess_singleton_module.c at line 716
[barriere:463328] [[INVALID],INVALID] ORTE_ERROR_LOG: Unable to start a
daemon on the local node in file
../../../../../../orte/mca/ess/singleton/ess_singleton_module.c at line 172
--------------------------------------------------------------------------
It looks like orte_init failed for some reason; your parallel process is
likely to abort.  There are many reasons that a parallel process can
fail during orte_init; some of which are due to configuration or
environment problems.  This failure appears to be an internal failure;
here's some additional information (which may only be relevant to an
Open MPI developer):

  orte_ess_init failed
  --> Returned value Unable to start a daemon on the local node (-127)
instead of ORTE_SUCCESS
--------------------------------------------------------------------------
--------------------------------------------------------------------------
It looks like MPI_INIT failed for some reason; your parallel process is
likely to abort.  There are many reasons that a parallel process can
fail during MPI_INIT; some of which are due to configuration or environment
problems.  This failure appears to be an internal failure; here's some
additional information (which may only be relevant to an Open MPI
developer):

  ompi_mpi_init: ompi_rte_init failed
  --> Returned "Unable to start a daemon on the local node" (-127)
instead of "Success" (0)
--------------------------------------------------------------------------
*** An error occurred in MPI_Init_thread
*** on a NULL communicator
*** MPI_ERRORS_ARE_FATAL (processes in this communicator will now abort,
***    and potentially your MPI job)
[barriere:463328] Local abort before MPI_INIT completed completed
successfully, but am not able to aggregate error messages, and not able
to guarantee that all other processes were killed!

Andrius

--- End Message ---
--- Begin Message ---
Source: pmix
Source-Version: 4.2.0+really.4.1.2-3
Done: Alastair McKinstry <mckins...@debian.org>

We believe that the bug you reported is fixed in the latest version of
pmix, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1017...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Alastair McKinstry <mckins...@debian.org> (supplier of updated pmix package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Mon, 05 Sep 2022 12:26:30 +0100
Source: pmix
Architecture: source
Version: 4.2.0+really.4.1.2-3
Distribution: unstable
Urgency: medium
Maintainer: Alastair McKinstry <mckins...@debian.org>
Changed-By: Alastair McKinstry <mckins...@debian.org>
Closes: 1017356 1017730
Changes:
 pmix (4.2.0+really.4.1.2-3) unstable; urgency=medium
 .
   * Drop B-D on pandoc. Closes: #1017356, #1017730
Checksums-Sha1:
 7093e37e3cb8f0c145fcdb05c69aebc90ecaba2d 2401 pmix_4.2.0+really.4.1.2-3.dsc
 539e871f8f7badb3620b518e74e8187d62963ae6 10372 
pmix_4.2.0+really.4.1.2-3.debian.tar.xz
Checksums-Sha256:
 a57ceaf0368ce756e50317ab070e314db8ca4f8936488cfc1709ca1162f14121 2401 
pmix_4.2.0+really.4.1.2-3.dsc
 e537b15de13c1ad98be797758c57176b1de6a5b30617dd1d6255b489c812512e 10372 
pmix_4.2.0+really.4.1.2-3.debian.tar.xz
Files:
 709181c7df829e57ca71315cf75e3621 2401 net optional 
pmix_4.2.0+really.4.1.2-3.dsc
 195c62dcde1d42697272ce4b1b5303a0 10372 net optional 
pmix_4.2.0+really.4.1.2-3.debian.tar.xz

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAmMV3vMACgkQy+a7Tl2a
06X3pw//ReYPV45uoA/DxLuVt4P1ERuRVwisBRcHQMYh2DU+Y/IGIhVra9yT+Sn+
ZrPQa7xfxpiPFXH7ald/hJ2bYEyFZxqzLpU9ONJ+MXZseDVlGccOSA9N4bwyngOM
5L9ido+MHlFcv3oo8aoRNZMIUAewFfKzuV4cpHI7BwnqMBURXcfw7EGW7S+JOQPS
+x9ke972zp0xNHLTY5bmnpj3nb0Ls9f2JNvSFLUcfovP11t1u0aBGtDsxf3eJgPm
1bcoI5pxpmwJGe0YDp5aDzmx5LPP/879gLpaphXcvYCTEPEo3TgWEqQ3Ykb8l1Wd
5xkCsIDKHXOAH0EIZGzUG4qN3dkKEIWdjNlhZhfKp3GECa8e342Es4YTNopO19yJ
FK113QPXYzOjg5He51hrPx2YjOhYresUQbsW6k+Tjx9YHcRBPebduX1AKDVcDCqy
qZlVkqo/qfJ+3vaOJAUFr1VafMq/RKGWOKGW/utt8jiHUEwHnSLRvgx4JWKfbrGN
9Fh1xR7mHspkci2ZbRXpsoIw/cE8/pBH4mqGQd4CbuTsA9uLVysuzRmyn62e14OP
PD2t9k6i5dikKnePb2/6GUhC36hqJ1PXnuWyAw9GPaDkvUbyQzpqGZfG2YBxGzcj
+MlNHqlMCW1LNR/xHhd/e+KQhDhwxYYarYRaZfjZIdn5M2WdQhI=
=M5hO
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to