How to Install and Uninstall libffi.i686 Package on CentOS 8 / RHEL 8

Last updated: May 14,2024

1. Install "libffi.i686" package

This tutorial shows how to install libffi.i686 on CentOS 8 / RHEL 8

$ sudo dnf update $ sudo dnf install libffi.i686

2. Uninstall "libffi.i686" package

This tutorial shows how to uninstall libffi.i686 on CentOS 8 / RHEL 8:

$ sudo dnf remove libffi.i686 $ sudo dnf autoremove

3. Information about the libffi.i686 package on CentOS 8 / RHEL 8

Last metadata expiration check: 1 day, 5:33:12 ago on Sun May 9 13:03:46 2021.
Available Packages
Name : libffi
Version : 3.1
Release : 22.el8
Architecture : i686
Size : 36 k
Source : libffi-3.1-22.el8.src.rpm
Repository : baseos
Summary : A portable foreign function interface library
URL : http://sourceware.org/libffi
License : MIT
Description : Compilers for high level languages generate code that follow certain
: conventions. These conventions are necessary, in part, for separate
: compilation to work. One such convention is the "calling convention".
: The calling convention is a set of assumptions made by the compiler
: about where function arguments will be found on entry to a function. A
: calling convention also specifies where the return value for a function
: is found.
:
: Some programs may not know at the time of compilation what arguments
: are to be passed to a function. For instance, an interpreter may be
: told at run-time about the number and types of arguments used to call a
: given function. `Libffi' can be used in such programs to provide a
: bridge from the interpreter program to compiled code.
:
: The `libffi' library provides a portable, high level programming
: interface to various calling conventions. This allows a programmer to
: call any function specified by a call interface description at run time.
:
: FFI stands for Foreign Function Interface. A foreign function
: interface is the popular name for the interface that allows code
: written in one language to call code written in another language. The
: `libffi' library really only provides the lowest, machine dependent
: layer of a fully featured foreign function interface. A layer must
: exist above `libffi' that handles type conversions for values passed
: between the two languages.