Python error after installing libboost-all-dev on debian

A close friend of mine desired the libboost collections mounted on our shared computer system so after mounting libboost - all - dev 1.49.0.1 (a Debian wheezy equipment), I get this mistake when making use of the "pydoc modules" command on the commandline. It spews out the adhering to mistake - -

[email protected]:/usr/include/c++/4.7# pydoc modules

Please wait a moment while I gather a list of all available modules...

**[debian:49065] [[INVALID],INVALID] ORTE_ERROR_LOG: A system-required executable either could not be found or was not executable by this user in file ../../../../../../orte/mca/ess/singleton/ess_singleton_module.c at line 357
[debian:49065] [[INVALID],INVALID] ORTE_ERROR_LOG: A system-required executable either could not be found or was not executable by this user in file ../../../../../../orte/mca/ess/singleton/ess_singleton_module.c at line 230
[debian:49065] [[INVALID],INVALID] ORTE_ERROR_LOG: A system-required executable either could not be found or was not executable by this user in file ../../../orte/runtime/orte_init.c at line 132
--------------------------------------------------------------------------
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_set_name failed
  --> Returned value A system-required executable either could not be found or was not executable by this user (-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: orte_init failed
  --> Returned "A system-required executable either could not be found or was not executable by this user" (-127) instead of "Success" (0)
--------------------------------------------------------------------------
*** The MPI_Init() function was called before MPI_INIT was invoked.
*** This is disallowed by the MPI standard.
*** Your MPI job will now abort.
[debian:49065] Abort before MPI_INIT completed successfully; not able to guarantee that all other processes were killed!**
[email protected]:/usr/include/c++/4.7# 

I attempted checking into the trouble and also wound up uninstalling the complying with to get it to function once more.

openmpi common all 1.4.5-1
libibverbs-dev amd64 1.1.6-1                                   
libopenmpi-dev amd64 1.4.5-1                                   
mpi-default-dev amd64 1.0.1
libboost-mpi-python1.49.0

Although pydoc functions once more, I'm thinking the plans I got rid of are mosting likely to injure another thing down the track? As you presumed I'm not a C/C+npls designer. So I presume my inquiry is, will this injure something later on? Exists a means to install those plans without injuring Python?

0
2022-07-25 20:42:13
Source Share
Answers: 0