| Key | Value |
|---|---|
| CRC32 | 7759D604 |
| FileName | ./usr/lib/.build-id/ec/61531366b433b097b8cc1162f7503ea0a297b3 |
| FileSize | 37 |
| MD5 | F99EC2E42ACAE704AE3BAC17ACFA107A |
| OpSystemCode | {'MfgCode': '1006', 'OpSystemCode': '362', 'OpSystemName': 'TBD', 'OpSystemVersion': 'none'} |
| ProductCode | {'ApplicationType': 'Operating System', 'Language': 'English', 'MfgCode': '2194', 'OpSystemCode': '652', 'ProductCode': '214118', 'ProductName': 'Fedora Cloud Base image for Openstack', 'ProductVersion': '31'} |
| RDS:package_id | 263824 |
| SHA-1 | 4A5A1216532350ECC9B369C485390B49F0C934F5 |
| SHA-256 | 3E111D99BE7E169186FD321E4CC91E897AAE95CE0985AC99375F36931F02A03D |
| SSDEEP | 3:gCD/Wlh:X/Wlh |
| SpecialCode | |
| TLSH | |
| db | nsrl_modern_rds |
| insert-timestamp | 1654958870.5188472 |
| source | modern.db |
| hashlookup:parent-total | 13 |
| hashlookup:trust | 100 |
The searched file hash is included in 13 parent files which include package known and seen by metalookup. A sample is included below:
| Key | Value |
|---|---|
| MD5 | ABF3BDF069263ECCB5D6D5FC428409FE |
| PackageArch | x86_64 |
| PackageDescription | 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. |
| PackageMaintainer | Fedora Project |
| PackageName | libffi |
| PackageRelease | 26.fc33 |
| PackageVersion | 3.1 |
| SHA-1 | 820EE5D5E1E07CD0090962E3E18C0FBE20ADF6F4 |
| SHA-256 | B877711628F940C9FAEF140A34A5227F6FB428F505A13048B786A28A16D7D24C |
| Key | Value |
|---|---|
| MD5 | FA0535D42C023CEBBAB023413C7F1CA7 |
| PackageArch | aarch64 |
| PackageDescription | 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. |
| PackageMaintainer | Fedora Project |
| PackageName | libffi |
| PackageRelease | 24.fc32 |
| PackageVersion | 3.1 |
| SHA-1 | B1DCE5F781BFF24A92B687DE8EACD1F5327C4311 |
| SHA-256 | 291DF16C0AE66FA5685CD033C84AE92765BE4F4E17CE4936E47DC602AC6FF93E |
| Key | Value |
|---|---|
| MD5 | 59CBC6873F0D398EDACF711A2DA3ECAA |
| PackageArch | ppc64le |
| PackageDescription | 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. |
| PackageMaintainer | CentOS Buildsys <bugs@centos.org> |
| PackageName | libffi |
| PackageRelease | 22.el8 |
| PackageVersion | 3.1 |
| SHA-1 | ECA7E158BC54A5E432D342B24C7AF68345CB2F66 |
| SHA-256 | 12696F5638AD2068C5C8940495D15C3BB1C57990000DBDA7428B008E9E63AB5B |
| Key | Value |
|---|---|
| MD5 | FCDAB84AFC5C2C6ECE2124A9A8284C38 |
| PackageArch | aarch64 |
| PackageDescription | 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. |
| PackageMaintainer | Fedora Project |
| PackageName | libffi |
| PackageRelease | 26.fc33 |
| PackageVersion | 3.1 |
| SHA-1 | 1F5818E97E800E7F4A43F3FF666984411729259A |
| SHA-256 | AEB3AD6CEA3959372B60CCC543E9B48E007D8E4FD66E911269E971BA5D00529B |
| Key | Value |
|---|---|
| MD5 | 62814716AF06BFFBDD5A5C820628FD9F |
| PackageArch | x86_64 |
| PackageDescription | 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. |
| PackageMaintainer | Fedora Project |
| PackageName | libffi |
| PackageRelease | 28.fc34 |
| PackageVersion | 3.1 |
| SHA-1 | 69AB12FE8201A33F5409004F64E0B1A48EC5FF83 |
| SHA-256 | AC6DBB4D55388F795B15F0339116978BCA4FC0231EAA7FA7FAADDC77BB9AA74A |
| Key | Value |
|---|---|
| MD5 | 785BEAE80FBB8821573EA65853D4CF05 |
| PackageArch | x86_64 |
| PackageDescription | 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. |
| PackageMaintainer | CloudLinux Packaging Team <packager@cloudlinux.com> |
| PackageName | libffi |
| PackageRelease | 22.el8 |
| PackageVersion | 3.1 |
| SHA-1 | 6540348BFEC41270974C9B6607E960B099D5B331 |
| SHA-256 | DDD7941B06F686D392B0EA2FF01B28E6317E7BA639DC992ADD5D8CFA40196D71 |
| Key | Value |
|---|---|
| MD5 | 2FF5183BFE0F1AA83D23F57E87CBA090 |
| PackageArch | aarch64 |
| PackageDescription | 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. |
| PackageMaintainer | CentOS Buildsys <bugs@centos.org> |
| PackageName | libffi |
| PackageRelease | 22.el8 |
| PackageVersion | 3.1 |
| SHA-1 | 0E02A7E1A42CFCF6C54B7AC49149678DF9A64783 |
| SHA-256 | 9D7E9A47E16B3EDD1F9CE69C44BF485E8498CB6CED68E354B4C24936CD015BB5 |
| Key | Value |
|---|---|
| MD5 | 6474465288A32074805BE80F65B57BC8 |
| PackageArch | x86_64 |
| PackageDescription | 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. |
| PackageMaintainer | CentOS Buildsys <bugs@centos.org> |
| PackageName | libffi |
| PackageRelease | 22.el8 |
| PackageVersion | 3.1 |
| SHA-1 | 6CC86746BC734901312915929377E096AC18E9EC |
| SHA-256 | 3991890C6B556A06923002B0AD511C0E2D85E93CB0618758E68D72F95676B4E6 |
| Key | Value |
|---|---|
| MD5 | E3B2A1A64AEE6AB929F54D27E514A741 |
| PackageArch | x86_64 |
| PackageDescription | 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. |
| PackageMaintainer | CentOS Buildsys <bugs@centos.org> |
| PackageName | libffi |
| PackageRelease | 23.el8 |
| PackageVersion | 3.1 |
| SHA-1 | A99FE718BFCD69E889BCC09FCECA022D48E7FF4B |
| SHA-256 | 643D1B969C7FBCD55C523F779089F3F2FE8B105C719FD49C7EDD1F142DFC2143 |
| Key | Value |
|---|---|
| MD5 | 1D3CE98EF20CCA40856B7CDBF74AF70F |
| PackageArch | aarch64 |
| PackageDescription | 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. |
| PackageMaintainer | Fedora Project |
| PackageName | libffi |
| PackageRelease | 28.fc34 |
| PackageVersion | 3.1 |
| SHA-1 | 9DF4787B5F3764EF6DEDCEC8A52B2C29D7906A21 |
| SHA-256 | 1DC9AE7ED75EA292106687B418D93A9A89EB3F6E3B2FC603919AF3D36C97E75C |
| Key | Value |
|---|---|
| MD5 | D85E760668901805BC7CB137AE561FAD |
| PackageArch | x86_64 |
| PackageDescription | 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. |
| PackageMaintainer | Fedora Project |
| PackageName | libffi |
| PackageRelease | 24.fc32 |
| PackageVersion | 3.1 |
| SHA-1 | F6CC950082E7B2AC0248B13DDB0B0C4BB8B65889 |
| SHA-256 | 86C87A4169BDF75C6D3A2F11D3A7E20B6364B2DB97C74BC7EB62B1B22BC54401 |
| Key | Value |
|---|---|
| MD5 | 61152CDC44797AB88E7920C888A4DD8B |
| PackageArch | aarch64 |
| PackageDescription | 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. |
| PackageMaintainer | CentOS Buildsys <bugs@centos.org> |
| PackageName | libffi |
| PackageRelease | 23.el8 |
| PackageVersion | 3.1 |
| SHA-1 | 2BFD40B5F99B57E7965ECD1FEAF79F45C6BC9080 |
| SHA-256 | BA34D0BB067722C37DD4367534D82AA18C659FACBFD17952F8D826E8662CB7C1 |
| Key | Value |
|---|---|
| MD5 | 1E1D1FD715E49E63753C2B2DC1D6F753 |
| PackageArch | ppc64le |
| PackageDescription | 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. |
| PackageMaintainer | CentOS Buildsys <bugs@centos.org> |
| PackageName | libffi |
| PackageRelease | 23.el8 |
| PackageVersion | 3.1 |
| SHA-1 | 7CFE727BAF7FA3C6D94803D690B5F8E85C7B35BE |
| SHA-256 | CC6DD26948F2A3B06D4FAF44B4C51EA73392ED3CBFCEBA2603BBE487405869EA |