How to Install and Uninstall mpiP_3_5-gnu-openmpi1-hpc Package on openSuSE Tumbleweed
Last updated: December 25,2024
Deprecated! Installation of this package may no longer be supported.
1. Install "mpiP_3_5-gnu-openmpi1-hpc" package
Please follow the guidelines below to install mpiP_3_5-gnu-openmpi1-hpc on openSuSE Tumbleweed
$
sudo zypper refresh
Copied
$
sudo zypper install
mpiP_3_5-gnu-openmpi1-hpc
Copied
2. Uninstall "mpiP_3_5-gnu-openmpi1-hpc" package
Here is a brief guide to show you how to uninstall mpiP_3_5-gnu-openmpi1-hpc on openSuSE Tumbleweed:
$
sudo zypper remove
mpiP_3_5-gnu-openmpi1-hpc
Copied
3. Information about the mpiP_3_5-gnu-openmpi1-hpc package on openSuSE Tumbleweed
Information for package mpiP_3_5-gnu-openmpi1-hpc:
--------------------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : mpiP_3_5-gnu-openmpi1-hpc
Version : 3.5-1.5
Arch : x86_64
Vendor : openSUSE
Installed Size : 4,8 MiB
Installed : No
Status : not installed
Source package : mpiP_3_5-gnu-openmpi1-hpc-3.5-1.5.src
Summary : A profiling library for MPI applications
Description :
mpiP is a profiling library for MPI applications.
It only collects statistical information about MPI functions, so mpiP
generates less overhead and much less data than tracing
tools. All the information captured by mpiP is task-local. It only
uses communication during report generation, typically at the end of
the experiment, to merge results from all of the tasks into one output
file.
--------------------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : mpiP_3_5-gnu-openmpi1-hpc
Version : 3.5-1.5
Arch : x86_64
Vendor : openSUSE
Installed Size : 4,8 MiB
Installed : No
Status : not installed
Source package : mpiP_3_5-gnu-openmpi1-hpc-3.5-1.5.src
Summary : A profiling library for MPI applications
Description :
mpiP is a profiling library for MPI applications.
It only collects statistical information about MPI functions, so mpiP
generates less overhead and much less data than tracing
tools. All the information captured by mpiP is task-local. It only
uses communication during report generation, typically at the end of
the experiment, to merge results from all of the tasks into one output
file.