Parents (Total: 73)

The searched file hash is included in 73 parent files which include package known and seen by metalookup. A sample is included below:

Key	Value
MD5	4DA5F0FC670E2F350238AC5F98C3E1F6
PackageArch	armv5tel
PackageDescription	The libffi-devel package contains libraries and header files for developing applications that use libffi.
PackageMaintainer	Fedora Project
PackageName	libffi-devel
PackageRelease	1.fc14
PackageVersion	3.0.10
SHA-1	01180B421510F051442B5C1701A1BC464B944694
SHA-256	E7021193A30C9A1A5BC3C5E64242D2AF577546C319E6696800FA6D51F23387AB

Key	Value
MD5	F93249E2AD8E47310BC4E9009DF91431
PackageArch	s390x
PackageDescription	The libffi-devel package contains libraries and header files for developing applications that use libffi.
PackageMaintainer	Fedora Project
PackageName	libffi-devel
PackageRelease	2.fc15.dh.1
PackageVersion	3.0.9
SHA-1	078F5F57ECEC695A44369D3364EBC1733C03F8C5
SHA-256	2DD3B4B5303AA03A81846444F8201DF38A136823239BA31CD15367E3EFF88930

Key	Value
MD5	167AF9B92B074CE383BC84209D9650F0
PackageArch	ppc64
PackageDescription	This package is for compatability to old versions only, and provides no Development libraries 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	compat-libffi
PackageRelease	4.fc20
PackageVersion	3.0.10
SHA-1	092A77B567A2E5149777F8A2EC2F360D8B06BF2B
SHA-256	FF879F5D8D568C0074961073C758EE6C8CC4C8C08B201F2178FDA4832EF6971B

Key	Value
MD5	183D8B877DF9C66289D7A3A0A9E579F3
PackageArch	s390
PackageDescription	This package is for compatability to old versions only, and provides no Development libraries 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	compat-libffi
PackageRelease	4.fc20
PackageVersion	3.0.10
SHA-1	0F6A107D7D530E6D15A138B36AFBEFA27E8FDBEA
SHA-256	1100EAF7398A7C71D832725CBCFA1B74CA1F5B71EDEDF298F9C88FFF98F5CCA7

Key	Value
MD5	B39391837698713C67671DF97AE13559
PackageArch	sparcv9
PackageDescription	The libffi-devel package contains libraries and header files for developing applications that use libffi.
PackageMaintainer	Fedora Project
PackageName	libffi-devel
PackageRelease	1.fc17
PackageVersion	3.0.10
SHA-1	12DDC320A617FF1FB92690E6F83A6167E4862D0A
SHA-256	9760DDC0A38DA2F19117EC02805C7C8063663311A9E524F309B4BEF6727444BD

Key	Value
MD5	1C5A51B9FD31755B6364553F8377387C
PackageArch	s390x
PackageDescription	This package is for compatability to old versions only, and provides no Development libraries 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	compat-libffi
PackageRelease	6.fc22
PackageVersion	3.0.10
SHA-1	172C62F89B8FACB350ECB983B8872FE3499AE96C
SHA-256	91A1DF3136112A5639260021188BCF2D5D2F40A7F62AFD7D504AB5B3E1821F14

Key	Value
MD5	0731A0E78EA2D71DC57A1FA29B553FCE
PackageArch	ppc64
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	Koji
PackageName	libffi
PackageRelease	3.fc18
PackageVersion	3.0.10
SHA-1	17DB461217F7F89BD87F72C94C7232C4413D0D2C
SHA-256	AA4DBF435A164A0C090E0110583C5A94854910A57205A919145DCF17BC92CA5F

Key	Value
MD5	C435BBB60925D9BDCA374C85A8AAB397
PackageArch	ppc64
PackageDescription	The libffi-devel package contains libraries and header files for developing applications that use libffi.
PackageMaintainer	Koji
PackageName	libffi-devel
PackageRelease	3.fc18
PackageVersion	3.0.10
SHA-1	189C2C38A8A5B82206AF745FB364698E0F0BF58B
SHA-256	796A6BC737C9E05538BBEB1B5FAE9657D229D8136D83E889C9968BAE6E7D97C4

Key	Value
MD5	B98AF4672F3A0CD08BD4B58F0A877C51
PackageArch	armv5tel
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	3.fc18
PackageVersion	3.0.10
SHA-1	19B758E7E828132D063847C8CE3A4C0139FEEDAE
SHA-256	97F0AF34B9CBAE5E8CDC9F1223F8C44E05459F85EF7FFDB51D3A16DBD3829D43

Key	Value
MD5	3F815DE9C8BF34E6AFAE45DB5B5863F8
PackageArch	armv5tel
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	1.fc15
PackageVersion	3.0.10
SHA-1	25BC5C311FD43570E59DED48F5F45AAE1DF5088C
SHA-256	66F19B21B1324BD1F397D95DC3FA54F263FDDCC1CBC41BE33B68D6688BF62F94