1 | <?xml version="1.0" encoding="UTF-8"?>
|
---|
2 | <!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
|
---|
3 | "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
|
---|
4 | <!ENTITY % general-entities SYSTEM "../general.ent">
|
---|
5 | %general-entities;
|
---|
6 | ]>
|
---|
7 |
|
---|
8 | <sect1 id="ch-system-libffi" role="wrap">
|
---|
9 | <?dbhtml filename="libffi.html"?>
|
---|
10 |
|
---|
11 | <sect1info condition="script">
|
---|
12 | <productname>libffi</productname>
|
---|
13 | <productnumber>&libffi-version;</productnumber>
|
---|
14 | <address>&libffi-url;</address>
|
---|
15 | </sect1info>
|
---|
16 |
|
---|
17 | <title>Libffi-&libffi-version;</title>
|
---|
18 |
|
---|
19 | <indexterm zone="ch-system-libffi">
|
---|
20 | <primary sortas="a-libffi">libffi</primary>
|
---|
21 | </indexterm>
|
---|
22 |
|
---|
23 | <sect2 role="package">
|
---|
24 | <title/>
|
---|
25 |
|
---|
26 | <para>The Libffi library provides a portable, high level programming
|
---|
27 | interface to various calling conventions. This allows a programmer to call
|
---|
28 | any function specified by a call interface description at run time.</para>
|
---|
29 |
|
---|
30 | <para>FFI stands for Foreign Function Interface. An FFI allows a program written
|
---|
31 | in one language to call a program written in another language. Specifically,
|
---|
32 | Libffi can provide a bridge between an interpreter like Perl, or Python, and
|
---|
33 | shared library subroutines written in C, or C++.</para>
|
---|
34 |
|
---|
35 | <segmentedlist>
|
---|
36 | <segtitle>&buildtime;</segtitle>
|
---|
37 | <segtitle>&diskspace;</segtitle>
|
---|
38 |
|
---|
39 | <seglistitem>
|
---|
40 | <seg>&libffi-fin-sbu;</seg>
|
---|
41 | <seg>&libffi-fin-du;</seg>
|
---|
42 | </seglistitem>
|
---|
43 | </segmentedlist>
|
---|
44 |
|
---|
45 | </sect2>
|
---|
46 |
|
---|
47 | <sect2 role="installation">
|
---|
48 | <title>Installation of Libffi</title>
|
---|
49 |
|
---|
50 | <note>
|
---|
51 | <para>Like GMP, Libffi builds with optimizations specific
|
---|
52 | to the processor in use. If building for another system, change the
|
---|
53 | value of the <parameter>--with-gcc-arch=</parameter> parameter in the
|
---|
54 | following command to an architecture name fully implemented by the
|
---|
55 | CPU on that system.
|
---|
56 | If this is not done, all applications that link to
|
---|
57 | <filename class='libraryfile'>libffi</filename> will trigger
|
---|
58 | Illegal Operation Errors.</para>
|
---|
59 | </note>
|
---|
60 |
|
---|
61 | <para>Prepare Libffi for compilation:</para>
|
---|
62 |
|
---|
63 | <screen><userinput remap="configure">./configure --prefix=/usr \
|
---|
64 | --disable-static \
|
---|
65 | --with-gcc-arch=native</userinput></screen>
|
---|
66 |
|
---|
67 | <variablelist>
|
---|
68 | <title>The meaning of the configure option:</title>
|
---|
69 |
|
---|
70 | <varlistentry>
|
---|
71 | <term><parameter>--with-gcc-arch=native</parameter></term>
|
---|
72 | <listitem>
|
---|
73 | <para>Ensure GCC optimizes for the current system. If this
|
---|
74 | is not specified, the system is guessed and the code generated
|
---|
75 | may not be correct. If the generated code
|
---|
76 | will be copied from the native system to a less capable
|
---|
77 | system, use the less capable system as a parameter. For details
|
---|
78 | about alternative system types, see <ulink
|
---|
79 | url='https://gcc.gnu.org/onlinedocs/gcc-&gcc-version;/gcc/x86-Options.html'>
|
---|
80 | the x86 options in the GCC manual</ulink>.</para>
|
---|
81 | </listitem>
|
---|
82 | </varlistentry>
|
---|
83 | </variablelist>
|
---|
84 |
|
---|
85 | <para>Compile the package:</para>
|
---|
86 |
|
---|
87 | <screen><userinput remap="make">make</userinput></screen>
|
---|
88 |
|
---|
89 | <para>To test the results, issue:</para>
|
---|
90 |
|
---|
91 | <screen><userinput remap="test">make check</userinput></screen>
|
---|
92 |
|
---|
93 | <para>Install the package:</para>
|
---|
94 |
|
---|
95 | <screen><userinput remap="install">make install</userinput></screen>
|
---|
96 |
|
---|
97 | </sect2>
|
---|
98 |
|
---|
99 | <sect2 id="contents-libffi" role="content">
|
---|
100 | <title>Contents of Libffi</title>
|
---|
101 |
|
---|
102 | <segmentedlist>
|
---|
103 | <segtitle>Installed library</segtitle>
|
---|
104 |
|
---|
105 | <seglistitem>
|
---|
106 | <seg>libffi.so</seg>
|
---|
107 | </seglistitem>
|
---|
108 | </segmentedlist>
|
---|
109 |
|
---|
110 | <variablelist>
|
---|
111 | <bridgehead renderas="sect3">Short Descriptions</bridgehead>
|
---|
112 | <?dbfo list-presentation="list"?>
|
---|
113 | <?dbhtml list-presentation="table"?>
|
---|
114 |
|
---|
115 | <varlistentry id="libffi">
|
---|
116 | <term><filename class="libraryfile">libffi</filename></term>
|
---|
117 | <listitem>
|
---|
118 | <para>Contains the foreign function interface API functions</para>
|
---|
119 | <indexterm zone="ch-system-libffi">
|
---|
120 | <primary sortas="c-libffi">libffi</primary>
|
---|
121 | </indexterm>
|
---|
122 | </listitem>
|
---|
123 | </varlistentry>
|
---|
124 | </variablelist>
|
---|
125 |
|
---|
126 | </sect2>
|
---|
127 |
|
---|
128 | </sect1>
|
---|
129 |
|
---|