as the shell assignment. To restore the previous behavior, add a space after the exclamation mark, such
as variable! =value.
For more details and differences between the operator and the function, see the GNU make manual.
Valgrind library for MPI debugging support removed
The libmpiwrap.so wrapper library for Valgrind provided by the valgrind-openmpi package has been
removed. This library enabled Valgrind to debug programs using the Message Passing Interface (MPI).
This library was specific to the Open MPI implementation version in previous versions of Red Hat
Enterprise Linux.
Users of libmpiwrap.so are encouraged to build their own version from upstream sources specific to
their MPI implementation and version. Supply these custom-built libraries to Valgrind using the
LD_PRELOAD technique.
Development headers and static libraries removed from valgrind-devel
Previously, the valgrind-devel sub-package used to include development files for developing custom
valgrind tools. This update removes these files because they do not have a guaranteed API, have to be
linked statically, and are unsupported. The valgrind-devel package still does contain the development
files for valgrind-aware programs and header files such as valgrind.h, callgrind.h, drd.h, helgrind.h,
and memcheck.h, which are stable and well-supported.
5.2. OPTIONS FOR RUNNING A RHEL 6 OR 7 APPLICATION ON RHEL 8
To run a Red Hat Enterprise Linux 6 or 7 application on Red Hat Enterprise Linux 8, a spectrum of
options is available. A system administrator needs detailed guidance from the application developer. The
following list outlines the options, considerations, and resources provided by Red Hat.
Run the application in a virtual machine with a matching RHEL version guest OS
Resource costs are high for this option, but the environment is a close match to the application’s
requirements, and this approach does not require many additional considerations. This is the
currently recommended option.
Run the application in a container based on the respective RHEL version
Resource costs are lower than in the previous cases, while configuration requirements are stricter.
For details on the relationship between container hosts and guest user spaces, see the Red Hat
Enterprise Linux Container Compatibility Matrix.
Run the application natively on RHEL 8
This option offers the lowest resource costs, but also the most strict requirements. The application
developer must determine a correct configuration of the RHEL 8 system. The following resources
can help the developer in this task:
Red Hat Enterprise Linux 8: Application Compatibility Guide
Red Hat Enterprise Linux 7: Application Compatibility Guide
Release notes for Red Hat Enterprise Linux 8.0
Considerations in adopting RHEL 8
Note that this list is not a complete set of resources needed to determine application compatibility.
These are only starting points with lists of known incompatible changes and Red Hat policies related
to compatibility.
Additionally, the What is Kernel Application Binary Interface (kABI)? Knowledge Centered Support