Install this package:
emerge -a dev-libs/libffi-compat
If the package is masked, you can unmask it using the autounmask tool or standard emerge options:
autounmask dev-libs/libffi-compat
Or alternatively:
emerge --autounmask-write -a dev-libs/libffi-compat
| Version | EAPI | Keywords | Slot |
|---|---|---|---|
| 3.3-r2 | 7 | ~alpha amd64 ~arm ~arm64 ~hppa ~m68k ~ppc ~ppc64 ~riscv ~s390 ~sparc x86 ~x64-macos ~x64-solaris | 7 |
| 3.2.1-r3 | 7 | ~alpha amd64 ~arm ~arm64 ~hppa ~m68k ~ppc ~ppc64 ~s390 ~sparc x86 ~x64-macos ~x64-solaris | 6 |
<pkgmetadata> <maintainer type="project"> <email>toolchain@gentoo.org</email> <name>Gentoo Toolchain Project</name> </maintainer> <longdescription lang="en"> 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 essentially 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. </longdescription> <use> <flag name="pax-kernel">Use PaX emulated trampolines, for we can't use PROT_EXEC</flag> </use> <upstream> <remote-id type="cpe">cpe:/a:libffi_project:libffi</remote-id> <remote-id type="github">libffi/libffi</remote-id> </upstream> </pkgmetadata>
Manage flags for this package:
euse -i <flag> -p dev-libs/libffi-compat |
euse -E <flag> -p dev-libs/libffi-compat |
euse -D <flag> -p dev-libs/libffi-compat
| Flag | Description | 3.3-r2 | 3.2.1-r3 |
|---|---|---|---|
| debug | Enable extra debug codepaths, like asserts and extra output. If you want to get meaningful backtraces see https://wiki.gentoo.org/wiki/Project:Quality_Assurance/Backtraces | ✓ | ✓ |
| pax-kernel | Use PaX emulated trampolines, for we can't use PROT_EXEC | ✓ | ✓ |
| test | Enable dependencies and/or preparations necessary to run tests (usually controlled by FEATURES=test but can be toggled independently) | ✓ | ✓ |
| Type | File | Size | Versions |
|---|
| Type | File | Size |
|---|---|---|
| DIST | libffi-3.2.1.tar.gz | 940837 bytes |
| DIST | libffi-3.3.tar.gz | 1305466 bytes |