1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
|
<!-- $Id: install-compile.html,v 1.17 2004/01/16 14:20:42 rjs3 Exp $ -->
<HTML>
<HEAD>
<TITLE>Compiling the IMAP Server
</title>
</head>
<h1>Compiling the IMAP Server
</h1>
<body>
Once you have unpacked the files by extracting the tar archive,
"<TT>cd</TT>" to the "<tt>cyrus-imapd-<i>NNNN</i></tt>" directory
where <i>NNNN</i> is the version number. The configuration files and
various subdirectories are stored there. In the directory that the
<TT>configure</TT> file is in, type "<kbd>./configure</kbd>" to
configure the software. Please continue to read this document as there
are switches to <kbd>./configure</kbd> that may apply to you.
<h2><kbd>configure</kbd> Overview</h2>
<P>The "<TT>configure</TT>" shell script attempts to guess correct
values for various system-dependent variables used during compilation.
It uses those values to create a "<TT>Makefile</TT>" in each directory
of the package. Finally, it creates a shell script
"<TT>config.status</TT>" that you can run in the future to recreate
the current configuration, a file "<TT>config.cache</TT>" that saves
the results of its tests to speed up reconfiguring, and a file
"<TT>config.log</TT>" containing compiler output (useful mainly for
debugging "<TT>configure</TT>").
<P>Running "<tt>configure</tt>" takes awhile. While running, it
prints some messages telling which features it is checking for.
<P>You can compile the package in a different directory from the one
containing the source code. Doing so allows you to compile it on more
than one kind of computer at the same time. To do this, you must use
a version of "<TT>make</TT>" that supports the "<tt>VPATH</tt>"
variable, such as GNU "<TT>make</TT>". "<TT>cd</TT>" to the directory
where you want the object files and executables to go and run the
"<tt>configure</tt>" script. "<tt>configure</tt>" automatically
checks for the source code in the directory that "<tt>configure</tt>"
is in and in "<tt>..</tt>".
<P>By default, "<TT>make install</TT>" will install files (other than
server-specific programs) in "<TT>/usr/local/bin</TT>",
"<TT>/usr/local/man</TT>", etc. You can specify an installation
prefix other than "<TT>/usr/local</TT>" by giving "<TT>configure</TT>"
the option "<TT>--prefix=PATH</TT>".
<P>You can specify separate installation prefixes for
architecture-specific files and architecture-independent files. If
you give "<TT>configure</TT>" the option
"<TT>--exec-prefix=PATH</TT>", the package will use <TT>PATH</TT> as
the prefix for installing programs and libraries. Documentation and
other data files will still use the regular prefix.
<P>By default, "<TT>make install</TT>" will install the
server-specific programs in "<TT>/usr/cyrus/bin</TT>". You can
specify a server-specific installation prefix other than
"<TT>/usr/cyrus</TT>" by giving "<TT>configure</TT>" the option
"<TT>--with-cyrus-prefix=PATH</TT>".
<h2>Options to <kbd>configure</kbd></h2>
<p>Here are a list of switches that can be used with "<A
NAME="configure"><tt>configure</tt></A>".
<dl>
<dt><tt>--help</tt>
<dd>Print a summary of the options to "<tt>configure</tt>", and exit. <P>
<dt><tt>--with-auth=METHOD</tt>
<dd>Specifies the authorization (group membership) module to use.
Currently implemented authorization modules are:
<dl compact>
<DT><tt>unix</tt>
<DD>Unix <tt>/etc/passwd</tt> and <tt>/etc/group</tt> file
<DT><tt>krb</tt>
<DD>Kerberos principals (requires Kerberos libraries). Optionally,
specify where to find Kerberos v4 with "<tt>--with-krb=DIR</tt>"
<B>IMPORTANT:</B> The Kerberos v4 support requires the DES library.
Some vendor distributions of Kerberos, including the one with Solaris,
do not have this support and cannot be used.
<DT><tt>krb_pts</tt>
<DD>Kerberos principals with AFS PTserver groups (requires Kerberos
and AFS libraries). Optionally, specify where the AFS libraries are
found with "<tt>--with-afs=PATH</tt>". Also requires krb support as above.
</dl>
Any method of authenticating with SASL can be used with any
authorization module.<P>
<dt><tt>--with-krb=PATH</tt>
<dd>Specifies where to find the Kerberos library.<P>
<dt><tt>--with-com_err=PATH</tt>
<dd>Specifies where to find the com_err environment.<P>
<dt><tt>--with-cyrus-group=USER</tt>
<dd>Specifies the group used for installing setguid programs. By default,
configure uses "<TT>mail</TT>". <P>
<dt><tt>--with-cyrus-prefix=PATH</tt>
<dd>Change the location of the server software. By default, the
<tt>cyrus-prefix</tt> is <tt>/usr/cyrus</tt>.<p>
<dt><tt>--with-cyrus-user=USER</tt>
<dd>Specifies the userid that the Cyrus IMAP server will run as. By
default, configure uses "<TT>cyrus</TT>". <P>
<dt><tt>--with-dbdir=PATH</tt>
<dd>Specifies where to find the Berkeley DB library.<P>
<dt><tt>--with-duplicate-db=DB</tt>
<dd>Specifies which database backend to use for the duplicate delivery
database. By default, configure uses "<TT>berkeley_nosync</TT>".<P>
<dt><tt>--with-mboxlist-db=DB</tt>
<dd>Specifies which database backend to use for the mailbox list. By
default, configure uses "<TT>berkeley</TT>".<P>
<dt><tt>--with-seen-db=DB</tt>
<dd>Specifies which database backend to use for the seen state. By
default, configure uses "<TT>flat</TT>".<P>
<dt><tt>--with-subs-db=DB</tt>
<dd>Specifies which database backend to use for the subscriptions
list. By default, configure uses "<TT>flat</TT>".<P>
<dt><tt>--with-tls-db=DB</tt>
<dd>Specifies which database backend to use for the TLS cache. By
default, configure uses "<TT>berkeley_nosync</TT>".<P>
<dt><tt>--with-idle=METHOD</tt>
<dd>Specifies the IMAP IDLE method to use.
Currently implemented IDLE methods are:
<dl compact>
<DT><tt>idled</tt>
<DD>Use the IDLE daemon. The IDLE daemon listens on a UNIX socket for
messages from lmtpd/imapd/pop3d that a mailbox has been updated. The
daemon then signals those (if any) imapd that are idling on the
mailbox to check for the changes.
<DT><tt>poll</tt>
<DD>Periodically poll the mailbox for changes.
<DT><tt>no</tt>
<DD>Disable IMAP IDLE.
</dl>
By default, configure uses "<TT>poll</TT>".<P>
<dt><tt>--with-lock=METHOD</tt>
<dd>Specifies the locking method to use. Currently implemented locking
methods are:
<DL compact>
<DT><TT>flock</TT>
<DD><TT>flock()</TT> locking
<DT><TT>fcntl</TT>
<DD><TT>fcntl()</TT> locking
</DL>
By default, configure uses "<tt>fcntl</tt>" if the "<tt>fcntl()</tt>"
function exists, "<tt>flock</tt>" otherwise.<P>
<dt><tt>--with-openssl=PATH</tt>
<dd>Specifies where to find the OpenSSL library.<P>
<dt><tt>--with-egd-socket=FILE</tt>
<dd>Specifies which socket to use to connect to the Entropy Gathering
Daemon.<P>
<dt><tt>--with-perl=PATH</tt>
<dd>Specifies where to find the Perl binary (full path, including
name of binary).<P>
<dt><tt>--with-sasl=PATH</tt>
<dd>Specifies the path to the directories containing the library
(<tt>.../lib</tt>) and include (<tt>.../include</tt>)
files for libsasl. <P>
<dt><tt>--with-statedir=PATH</tt>
<dd>Specifies the directory used for communicating with various
daemons. By default, configure uses "<TT>/var</TT>". <P>
<dt><tt>--with-libwrap=PATH</tt>
<dd>Specifies where to find the TCP wrappers library.<P>
<dt><tt>--with-ucdsnmp=PATH</tt>
<dd>Specifies where to find the SNMP library.<P>
<dt><tt>--with-zephyr=PATH</tt>
<dd>Specifies where to find the Zephyr library (for notifyd).<P>
<dt><tt>--enable-listext</tt>
<dd>Enables support for LISTEXT extension.<p>
<dt><tt>--enable-murder</tt>
<dd>Enables support for IMAP Murder.<p>
<dt><tt>--enable-netscapehack</tt>
<dd>Enables support for X-NETSCAPE extension (administration URLs).<p>
<dt><tt>--disable-sieve</tt>
<dd>By default, Sieve support is enabled. Use
<tt>--disable-sieve</tt> to disable compiling the Sieve library and to
disable all Sieve support.<p>
<dt><tt>--disable-cyradm</tt>
<dd>Do not compile the <TT>cyradm</TT> administrative client.<P>
<dt><tt>--disable-server</tt>
<dd>Do not compile the IMAP server programs.<p>
</dl>
Run <tt>configure --help</tt> for further configuration options.
<P>Some systems require unusual options for compilation or linking
that the "<TT>configure</TT>" script does not know about. You can
give "<TT>configure</TT>" initial values for variables by setting them
in the environment. Using a Bourne-compatible shell, you can do that
on the command line like this:
<pre>
CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure
</pre>
Or on systems that have the "<TT>env</TT>" program, you can do it like this:
<pre>
env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure
</pre>
The "<tt>make</tt>" variables that you might want to override with
environment variables when running "<tt>configure</tt>" are:
<DL compact>
<DT><TT>CC</TT>
<DD>C compiler program.<br>
Default is "<tt>cc</tt>", or "<tt>gcc</tt>" if "<tt>gcc</tt>" is in
your <tt>PATH</tt>.<br> (For "<tt>CC</tt>", any value given in the
environment <strong>overrides</strong> the value that
"<tt>configure</tt>" would choose.)
<DT><TT>CFLAGS</TT>
<DD>Debugging and optimization options for the C compiler.<br>
<DT><TT>CPPFLAGS</TT>
<DD>Header file search directory ("<tt>-IDIR</tt>") and any other
miscellaneous options for the C preprocessor and compiler. If it is
not set in the environment when "<tt>configure</tt>" runs, the default value is
empty.<br>
<DT><TT>LDFLAGS</TT>
<DD>Stripping ("<TT>-s</TT>") and any other miscellaneous options for the
linker. If it is not set in the environment when "<tt>configure</tt>" runs,
the default value is empty.
<DT><TT>DEFS</TT>
<DD>Configuration options, in the form "<tt>-Dfoo -Dbar ...</tt>"<br>
<DT><TT>LIBS</TT>
<DD>Libraries to link with, in the form "<tt>-lfoo -lbar ...</tt>"<br>
(For "<tt>DEFS</tt>" and "<tt>LIBS</tt>", any value given in the
environment is <strong>added</strong> to the value that
"<tt>configure</tt>" chooses.)
</DL>
If you need to do unusual things to compile the package, we encourage
you to figure out how "<tt>configure</tt>" could check whether to do
them. After doing so, please send us a patch! Instructions for doing
so can be found on the <a href="feedback.html">feedback</a> page.
<p>The file "<tt>configure.in</tt>" is used as a template to create
"<tt>configure</tt>" by a program called "<tt>autoconf</tt>". You
will only need it if you want to regenerate "<tt>configure</tt>" using
a newer version of "<tt>autoconf</tt>".
<p>Once you have successfully run "<tt>configure</tt>", execute the
following commands:
<pre>
<kbd> make depend
make all CFLAGS=-O
</kbd></pre>
If you want, you can override the "<tt>make</tt>" variables
<tt>CFLAGS</tt> and <tt>LDFLAGS</tt> by entering the following:
<pre>
<kbd> make all CFLAGS=-O2 LDFLAGS=-s
</kbd></pre>
<P><HR>
last modified: $Date: 2004/01/16 14:20:42 $
</BODY></HTML>
|
