Commit | Line | Data |
8e07c86e |
1 | =head1 NAME |
2 | |
3 | Install - Build and Installation guide for perl5. |
4 | |
5 | =head1 SYNOPSIS |
6 | |
7f678428 |
7 | The basic steps to build and install perl5 on a Unix system are: |
8e07c86e |
8 | |
9 | rm -f config.sh |
10 | sh Configure |
11 | make |
12 | make test |
13 | make install |
36477c24 |
14 | |
aa689395 |
15 | # You may also wish to add these: |
16 | (cd /usr/include && h2ph *.h sys/*.h) |
3e3baf6d |
17 | (installhtml --help) |
aa689395 |
18 | (cd pod && make tex && <process the latex files>) |
8e07c86e |
19 | |
20 | Each of these is explained in further detail below. |
21 | |
7beaa944 |
22 | For information on non-Unix systems, see the section on |
23 | L<"Porting information"> below. |
7f678428 |
24 | |
7beaa944 |
25 | For information on what's new in this release, see the |
26 | pod/perldelta.pod file. For more detailed information about specific |
27 | changes, see the Changes file. |
c3edaffb |
28 | |
1ec51d55 |
29 | =head1 DESCRIPTION |
edb1cbcb |
30 | |
c3edaffb |
31 | This document is written in pod format as an easy way to indicate its |
32 | structure. The pod format is described in pod/perlpod.pod, but you can |
1ec51d55 |
33 | read it as is with any pager or editor. Headings and items are marked |
34 | by lines beginning with '='. The other mark-up used is |
35 | |
36 | B<text> embolden text, used for switches, programs or commands |
37 | C<code> literal code |
38 | L<name> A link (cross reference) to name |
39 | |
40 | You should probably at least skim through this entire document before |
41 | proceeding. |
c3edaffb |
42 | |
eed2e782 |
43 | If you're building Perl on a non-Unix system, you should also read |
44 | the README file specific to your operating system, since this may |
45 | provide additional or different instructions for building Perl. |
46 | |
203c3eec |
47 | If there is a hint file for your system (in the hints/ directory) you |
48 | should also read that hint file for specific information for your |
49 | system. (Unixware users should use the svr4.sh hint file.) |
50 | |
693762b4 |
51 | =head1 NOTE: This version is not binary compatible with Perl 5.004. |
52 | |
53 | For Perl 5.004 it was possible to be binary compatible with 5.003. |
54 | Starting from Perl 5.004_50 this is no longer possible because there were |
55 | many deep and far-reaching changes to the language internals. |
56 | |
57 | If you have dynamically loaded extensions that you built under perl |
58 | 5.003 or 5.004 and the so-called 'bincompat3' mode (the default mode) |
59 | and that you wish to continue to use with perl 5.005, you may need to |
60 | reinstall the extensions. If you wish to continue to support both 5.004 |
61 | and 5.005 on your system, you will have to move the 5.004 extensions |
62 | over to the 5.004 architecture-dependent library. See the discussion |
63 | below on L<"Coexistence with earlier versions of perl5."> |
64 | |
65 | The standard extensions supplied with Perl will be handled automatically. |
66 | |
67 | In a related issue, old extensions may possibly be affected by the |
68 | changes in the Perl language in the current release. Please see |
69 | pod/perldelta.pod for a description of what's changed. |
70 | |
aa689395 |
71 | =head1 Space Requirements |
eed2e782 |
72 | |
1ec51d55 |
73 | The complete perl5 source tree takes up about 7 MB of disk space. The |
74 | complete tree after completing make takes roughly 15 MB, though the |
75 | actual total is likely to be quite system-dependent. The installation |
76 | directories need something on the order of 7 MB, though again that |
77 | value is system-dependent. |
8e07c86e |
78 | |
aa689395 |
79 | =head1 Start with a Fresh Distribution |
8e07c86e |
80 | |
edb1cbcb |
81 | If you have built perl before, you should clean out the build directory |
82 | with the command |
83 | |
84 | make realclean |
c3edaffb |
85 | |
8e07c86e |
86 | The results of a Configure run are stored in the config.sh file. If |
87 | you are upgrading from a previous version of perl, or if you change |
88 | systems or compilers or make other significant changes, or if you are |
1ec51d55 |
89 | experiencing difficulties building perl, you should probably not |
8e07c86e |
90 | re-use your old config.sh. Simply remove it or rename it, e.g. |
91 | |
92 | mv config.sh config.sh.old |
4633a7c4 |
93 | |
e57fd563 |
94 | If you wish to use your old config.sh, be especially attentive to the |
95 | version and architecture-specific questions and answers. For example, |
96 | the default directory for architecture-dependent library modules |
97 | includes the version name. By default, Configure will reuse your old |
98 | name (e.g. /opt/perl/lib/i86pc-solaris/5.003) even if you're running |
99 | Configure for a different version, e.g. 5.004. Yes, Configure should |
100 | probably check and correct for this, but it doesn't, presently. |
101 | Similarly, if you used a shared libperl.so (see below) with version |
102 | numbers, you will probably want to adjust them as well. |
103 | |
104 | Also, be careful to check your architecture name. Some Linux systems |
1ec51d55 |
105 | (such as Debian) use i386, while others may use i486 or i586. If you |
106 | pick up a precompiled binary, it might not use the same name. |
e57fd563 |
107 | |
108 | In short, if you wish to use your old config.sh, I recommend running |
109 | Configure interactively rather than blindly accepting the defaults. |
8e07c86e |
110 | |
aa689395 |
111 | =head1 Run Configure |
8e07c86e |
112 | |
113 | Configure will figure out various things about your system. Some |
114 | things Configure will figure out for itself, other things it will ask |
1ec51d55 |
115 | you about. To accept the default, just press RETURN. The default |
203c3eec |
116 | is almost always ok. At any Configure prompt, you can type &-d |
117 | and Configure will use the defaults from then on. |
8e07c86e |
118 | |
119 | After it runs, Configure will perform variable substitution on all the |
1ec51d55 |
120 | *.SH files and offer to run make depend. |
8e07c86e |
121 | |
fb73857a |
122 | Configure supports a number of useful options. Run B<Configure -h> to |
123 | get a listing. See the Porting/Glossary file for a complete list of |
124 | Configure variables you can set and their definitions. |
125 | |
126 | To compile with gcc, for example, you should run |
8e07c86e |
127 | |
128 | sh Configure -Dcc=gcc |
129 | |
130 | This is the preferred way to specify gcc (or another alternative |
131 | compiler) so that the hints files can set appropriate defaults. |
132 | |
4633a7c4 |
133 | If you want to use your old config.sh but override some of the items |
134 | with command line options, you need to use B<Configure -O>. |
135 | |
8e07c86e |
136 | By default, for most systems, perl will be installed in |
137 | /usr/local/{bin, lib, man}. You can specify a different 'prefix' for |
138 | the default installation directory, when Configure prompts you or by |
139 | using the Configure command line option -Dprefix='/some/directory', |
140 | e.g. |
141 | |
25f94b33 |
142 | sh Configure -Dprefix=/opt/perl |
4633a7c4 |
143 | |
144 | If your prefix contains the string "perl", then the directories |
145 | are simplified. For example, if you use prefix=/opt/perl, |
146 | then Configure will suggest /opt/perl/lib instead of |
4fdae800 |
147 | /opt/perl/lib/perl5/. |
8e07c86e |
148 | |
84902520 |
149 | NOTE: You must not specify an installation directory that is below |
150 | your perl source directory. If you do, installperl will attempt |
151 | infinite recursion. |
152 | |
aa689395 |
153 | By default, Configure will compile perl to use dynamic loading if |
8e07c86e |
154 | your system supports it. If you want to force perl to be compiled |
56c6f531 |
155 | statically, you can either choose this when Configure prompts you or |
156 | you can use the Configure command line option -Uusedl. |
8e07c86e |
157 | |
203c3eec |
158 | If you are willing to accept all the defaults, and you want terse |
159 | output, you can run |
160 | |
161 | sh Configure -des |
162 | |
163 | For my Solaris system, I usually use |
164 | |
165 | sh Configure -Dprefix=/opt/perl -Doptimize='-xpentium -xO4' -des |
166 | |
46bb10fb |
167 | =head2 GNU-style configure |
168 | |
1ec51d55 |
169 | If you prefer the GNU-style configure command line interface, you can |
170 | use the supplied configure command, e.g. |
46bb10fb |
171 | |
693762b4 |
172 | CC=gcc ./configure.gnu |
46bb10fb |
173 | |
1ec51d55 |
174 | The configure script emulates a few of the more common configure |
46bb10fb |
175 | options. Try |
176 | |
693762b4 |
177 | ./configure.gnu --help |
46bb10fb |
178 | |
179 | for a listing. |
180 | |
aa689395 |
181 | Cross compiling is not supported. |
46bb10fb |
182 | |
693762b4 |
183 | (The file is called configugre.gnu to avoid problems on systems |
184 | that would not distinguish the files "Configure" and "configure".) |
46bb10fb |
185 | |
24b3df7f |
186 | =head2 Extensions |
187 | |
edb1cbcb |
188 | By default, Configure will offer to build every extension which appears |
189 | to be supported. For example, Configure will offer to build GDBM_File |
190 | only if it is able to find the gdbm library. (See examples below.) |
693762b4 |
191 | B, DynaLoader, Fcntl, IO, and attrs are always built by default. |
192 | Configure does not contain code to test for POSIX compliance, so POSIX |
193 | is always built by default as well. If you wish to skip POSIX, you can |
194 | set the Configure variable useposix=false either in a hint file or from |
195 | the Configure command line. Similarly, the Opcode extension is always |
196 | built by default, but you can skip it by setting the Configure variable |
c3edaffb |
197 | useopcode=false either in a hint file for from the command line. |
24b3df7f |
198 | |
1ec51d55 |
199 | You can learn more about each of these extensions by consulting the |
200 | documentation in the individual .pm modules, located under the |
201 | ext/ subdirectory. |
202 | |
56c6f531 |
203 | Even if you do not have dynamic loading, you must still build the |
204 | DynaLoader extension; you should just build the stub dl_none.xs |
205 | version. (Configure will suggest this as the default.) |
206 | |
24b3df7f |
207 | In summary, here are the Configure command-line variables you can set |
208 | to turn off each extension: |
209 | |
693762b4 |
210 | B (Always included by default) |
24b3df7f |
211 | DB_File i_db |
56c6f531 |
212 | DynaLoader (Must always be included as a static extension) |
24b3df7f |
213 | Fcntl (Always included by default) |
214 | GDBM_File i_gdbm |
9d67150a |
215 | IO (Always included by default) |
24b3df7f |
216 | NDBM_File i_ndbm |
217 | ODBM_File i_dbm |
218 | POSIX useposix |
219 | SDBM_File (Always included by default) |
c3edaffb |
220 | Opcode useopcode |
24b3df7f |
221 | Socket d_socket |
693762b4 |
222 | Threads usethreads |
223 | attrs (Always included by default) |
24b3df7f |
224 | |
225 | Thus to skip the NDBM_File extension, you can use |
226 | |
227 | sh Configure -Ui_ndbm |
228 | |
229 | Again, this is taken care of automatically if you don't have the ndbm |
230 | library. |
231 | |
232 | Of course, you may always run Configure interactively and select only |
aa689395 |
233 | the extensions you want. |
24b3df7f |
234 | |
693762b4 |
235 | Note: The DB_File module will only work with version 1.x of Berkeley |
236 | DB or newer releases of version 2. Configure will automatically detect |
237 | this for you and refuse to try to build DB_File with version 2. |
1ec51d55 |
238 | |
24b3df7f |
239 | Finally, if you have dynamic loading (most modern Unix systems do) |
240 | remember that these extensions do not increase the size of your perl |
241 | executable, nor do they impact start-up time, so you probably might as |
242 | well build all the ones that will work on your system. |
243 | |
8e07c86e |
244 | =head2 Including locally-installed libraries |
245 | |
4633a7c4 |
246 | Perl5 comes with interfaces to number of database extensions, including |
247 | dbm, ndbm, gdbm, and Berkeley db. For each extension, if |
248 | Configure can find the appropriate header files and libraries, it will |
249 | automatically include that extension. The gdbm and db libraries |
1ec51d55 |
250 | are not included with perl. See the library documentation for |
4633a7c4 |
251 | how to obtain the libraries. |
8e07c86e |
252 | |
1ec51d55 |
253 | Note: If your database header (.h) files are not in a |
8e07c86e |
254 | directory normally searched by your C compiler, then you will need to |
1ec51d55 |
255 | include the appropriate -I/your/directory option when prompted by |
8e07c86e |
256 | Configure. If your database library (.a) files are not in a directory |
257 | normally searched by your C compiler and linker, then you will need to |
1ec51d55 |
258 | include the appropriate -L/your/directory option when prompted by |
8e07c86e |
259 | Configure. See the examples below. |
260 | |
261 | =head2 Examples |
262 | |
263 | =over 4 |
264 | |
aa689395 |
265 | =item gdbm in /usr/local |
8e07c86e |
266 | |
267 | Suppose you have gdbm and want Configure to find it and build the |
1ec51d55 |
268 | GDBM_File extension. This examples assumes you have gdbm.h |
269 | installed in /usr/local/include/gdbm.h and libgdbm.a installed in |
270 | /usr/local/lib/libgdbm.a. Configure should figure all the |
8e07c86e |
271 | necessary steps out automatically. |
272 | |
273 | Specifically, when Configure prompts you for flags for |
1ec51d55 |
274 | your C compiler, you should include -I/usr/local/include. |
8e07c86e |
275 | |
276 | When Configure prompts you for linker flags, you should include |
1ec51d55 |
277 | -L/usr/local/lib. |
8e07c86e |
278 | |
279 | If you are using dynamic loading, then when Configure prompts you for |
280 | linker flags for dynamic loading, you should again include |
1ec51d55 |
281 | -L/usr/local/lib. |
8e07c86e |
282 | |
283 | Again, this should all happen automatically. If you want to accept the |
284 | defaults for all the questions and have Configure print out only terse |
285 | messages, then you can just run |
286 | |
287 | sh Configure -des |
288 | |
289 | and Configure should include the GDBM_File extension automatically. |
290 | |
291 | This should actually work if you have gdbm installed in any of |
292 | (/usr/local, /opt/local, /usr/gnu, /opt/gnu, /usr/GNU, or /opt/GNU). |
293 | |
294 | =item gdbm in /usr/you |
295 | |
296 | Suppose you have gdbm installed in some place other than /usr/local/, |
297 | but you still want Configure to find it. To be specific, assume you |
1ec51d55 |
298 | have /usr/you/include/gdbm.h and /usr/you/lib/libgdbm.a. You |
299 | still have to add -I/usr/you/include to cc flags, but you have to take |
300 | an extra step to help Configure find libgdbm.a. Specifically, when |
8e07c86e |
301 | Configure prompts you for library directories, you have to add |
1ec51d55 |
302 | /usr/you/lib to the list. |
8e07c86e |
303 | |
304 | It is possible to specify this from the command line too (all on one |
305 | line): |
306 | |
307 | sh Configure -des \ |
308 | -Dlocincpth="/usr/you/include" \ |
309 | -Dloclibpth="/usr/you/lib" |
310 | |
1ec51d55 |
311 | locincpth is a space-separated list of include directories to search. |
312 | Configure will automatically add the appropriate -I directives. |
8e07c86e |
313 | |
1ec51d55 |
314 | loclibpth is a space-separated list of library directories to search. |
315 | Configure will automatically add the appropriate -L directives. If |
316 | you have some libraries under /usr/local/ and others under |
317 | /usr/you, then you have to include both, namely |
8e07c86e |
318 | |
319 | sh Configure -des \ |
320 | -Dlocincpth="/usr/you/include /usr/local/include" \ |
321 | -Dloclibpth="/usr/you/lib /usr/local/lib" |
322 | |
323 | =back |
324 | |
aa689395 |
325 | =head2 Installation Directories |
4633a7c4 |
326 | |
327 | The installation directories can all be changed by answering the |
328 | appropriate questions in Configure. For convenience, all the |
329 | installation questions are near the beginning of Configure. |
330 | |
7beaa944 |
331 | I highly recommend running Configure interactively to be sure it puts |
332 | everything where you want it. At any point during the Configure |
333 | process, you can answer a question with &-d and Configure |
334 | will use the defaults from then on. |
1ec51d55 |
335 | |
4633a7c4 |
336 | By default, Configure uses the following directories for |
337 | library files (archname is a string like sun4-sunos, determined |
338 | by Configure) |
339 | |
46bb10fb |
340 | /usr/local/lib/perl5/archname/5.004 |
4633a7c4 |
341 | /usr/local/lib/perl5/ |
24b3df7f |
342 | /usr/local/lib/perl5/site_perl/archname |
343 | /usr/local/lib/perl5/site_perl |
4633a7c4 |
344 | |
345 | and the following directories for manual pages: |
346 | |
347 | /usr/local/man/man1 |
348 | /usr/local/lib/perl5/man/man3 |
349 | |
350 | (Actually, Configure recognizes the SVR3-style |
351 | /usr/local/man/l_man/man1 directories, if present, and uses those |
fb73857a |
352 | instead.) |
353 | |
354 | The module man pages are stuck in that strange spot so that |
4633a7c4 |
355 | they don't collide with other man pages stored in /usr/local/man/man3, |
356 | and so that Perl's man pages don't hide system man pages. On some |
357 | systems, B<man less> would end up calling up Perl's less.pm module man |
fb73857a |
358 | page, rather than the less program. (This default location will likely |
359 | change to /usr/local/man/man3 in a future release of perl.) |
1ec51d55 |
360 | |
361 | Note: Many users prefer to store the module man pages in |
362 | /usr/local/man/man3. You can do this from the command line with |
363 | |
364 | sh Configure -Dman3dir=/usr/local/man/man3 |
365 | |
366 | Some users also prefer to use a .3pm suffix. You can do that with |
367 | |
368 | sh Configure -Dman3ext=3pm |
4633a7c4 |
369 | |
370 | If you specify a prefix that contains the string "perl", then the |
aa689395 |
371 | directory structure is simplified. For example, if you Configure with |
372 | -Dprefix=/opt/perl, then the defaults are |
4633a7c4 |
373 | |
46bb10fb |
374 | /opt/perl/lib/archname/5.004 |
4633a7c4 |
375 | /opt/perl/lib |
376 | /opt/perl/lib/site_perl/archname |
377 | /opt/perl/lib/site_perl |
378 | |
379 | /opt/perl/man/man1 |
380 | /opt/perl/man/man3 |
381 | |
382 | The perl executable will search the libraries in the order given |
383 | above. |
384 | |
385 | The directories site_perl and site_perl/archname are empty, but are |
386 | intended to be used for installing local or site-wide extensions. Perl |
693762b4 |
387 | will automatically look in these directories. |
4633a7c4 |
388 | |
46bb10fb |
389 | In order to support using things like #!/usr/local/bin/perl5.004 after |
4633a7c4 |
390 | a later version is released, architecture-dependent libraries are |
391 | stored in a version-specific directory, such as |
693762b4 |
392 | /usr/local/lib/perl5/archname/5.004/. |
4633a7c4 |
393 | |
394 | Again, these are just the defaults, and can be changed as you run |
395 | Configure. |
396 | |
aa689395 |
397 | =head2 Changing the installation directory |
398 | |
399 | Configure distinguishes between the directory in which perl (and its |
400 | associated files) should be installed and the directory in which it |
401 | will eventually reside. For most sites, these two are the same; for |
402 | sites that use AFS, this distinction is handled automatically. |
1ec51d55 |
403 | However, sites that use software such as depot to manage software |
aa689395 |
404 | packages may also wish to install perl into a different directory and |
405 | use that management software to move perl to its final destination. |
406 | This section describes how to do this. Someday, Configure may support |
407 | an option -Dinstallprefix=/foo to simplify this. |
408 | |
0dcb58f4 |
409 | Suppose you want to install perl under the /tmp/perl5 directory. You |
410 | can edit config.sh and change all the install* variables to point to |
411 | /tmp/perl5 instead of /usr/local/wherever. Or, you can automate this |
412 | process by placing the following lines in a file config.over before you |
413 | run Configure (replace /tmp/perl5 by a directory of your choice): |
aa689395 |
414 | |
415 | installprefix=/tmp/perl5 |
416 | test -d $installprefix || mkdir $installprefix |
417 | test -d $installprefix/bin || mkdir $installprefix/bin |
418 | installarchlib=`echo $installarchlib | sed "s!$prefix!$installprefix!"` |
419 | installbin=`echo $installbin | sed "s!$prefix!$installprefix!"` |
420 | installman1dir=`echo $installman1dir | sed "s!$prefix!$installprefix!"` |
421 | installman3dir=`echo $installman3dir | sed "s!$prefix!$installprefix!"` |
422 | installprivlib=`echo $installprivlib | sed "s!$prefix!$installprefix!"` |
423 | installscript=`echo $installscript | sed "s!$prefix!$installprefix!"` |
424 | installsitelib=`echo $installsitelib | sed "s!$prefix!$installprefix!"` |
425 | installsitearch=`echo $installsitearch | sed "s!$prefix!$installprefix!"` |
426 | |
427 | Then, you can Configure and install in the usual way: |
428 | |
429 | sh Configure -des |
430 | make |
431 | make test |
432 | make install |
433 | |
693762b4 |
434 | Beware, though, that if you go to try to install new add-on |
435 | extensions, they too will get installed in under '/tmp/perl5' if you |
436 | follow this example. The next section shows one way of dealing with |
437 | that problem. |
438 | |
aa689395 |
439 | =head2 Creating an installable tar archive |
440 | |
441 | If you need to install perl on many identical systems, it is |
442 | convenient to compile it once and create an archive that can be |
443 | installed on multiple systems. Here's one way to do that: |
444 | |
445 | # Set up config.over to install perl into a different directory, |
446 | # e.g. /tmp/perl5 (see previous part). |
447 | sh Configure -des |
448 | make |
449 | make test |
450 | make install |
451 | cd /tmp/perl5 |
fb73857a |
452 | # Edit lib/<archname>/<version>/Config.pm to change all the |
453 | # install* variables back to reflect where everything will |
454 | # really be installed. |
aa689395 |
455 | tar cvf ../perl5-archive.tar . |
456 | # Then, on each machine where you want to install perl, |
457 | cd /usr/local # Or wherever you specified as $prefix |
458 | tar xvf perl5-archive.tar |
459 | |
693762b4 |
460 | =head2 Site-wide "Policy" settings |
461 | |
462 | After Configure runs, it stores a number of common site-wide "policy" |
463 | answers (such as installation directories and the local perl contact |
464 | person) in the Policy.sh file. If you want to build perl on another |
465 | system using the same policy defaults, simply copy the Policy.sh file |
466 | to the new system and Configure will use it along with the appropriate |
467 | hint file for your system. |
468 | |
aa689395 |
469 | =head2 Configure-time Options |
470 | |
471 | There are several different ways to Configure and build perl for your |
472 | system. For most users, the defaults are sensible and will work. |
473 | Some users, however, may wish to further customize perl. Here are |
474 | some of the main things you can change. |
475 | |
693762b4 |
476 | =head2 Threads |
aa689395 |
477 | |
693762b4 |
478 | On some platforms, perl5.005 can be compiled to use threads. To |
479 | enable this, read the file README.threads, and then try |
f7542a9d |
480 | |
693762b4 |
481 | sh Configure -Dusethreads |
aa689395 |
482 | |
693762b4 |
483 | Currently, you need to specify -Dusethreads on the Configure command |
484 | line so that the hint files can make appropriate adjustments. |
485 | |
486 | The default is to compile without thread support. |
3fe9a6f1 |
487 | |
46bb10fb |
488 | =head2 Selecting File IO mechanisms |
489 | |
490 | Previous versions of perl used the standard IO mechanisms as defined in |
1ec51d55 |
491 | stdio.h. Versions 5.003_02 and later of perl allow alternate IO |
46bb10fb |
492 | mechanisms via a "PerlIO" abstraction, but the stdio mechanism is still |
493 | the default and is the only supported mechanism. |
494 | |
495 | This PerlIO abstraction can be enabled either on the Configure command |
496 | line with |
497 | |
498 | sh Configure -Duseperlio |
499 | |
500 | or interactively at the appropriate Configure prompt. |
501 | |
502 | If you choose to use the PerlIO abstraction layer, there are two |
503 | (experimental) possibilities for the underlying IO calls. These have been |
504 | tested to some extent on some platforms, but are not guaranteed to work |
505 | everywhere. |
506 | |
507 | =over 4 |
508 | |
509 | =item 1. |
510 | |
1ec51d55 |
511 | AT&T's "sfio". This has superior performance to stdio.h in many |
aa689395 |
512 | cases, and is extensible by the use of "discipline" modules. Sfio |
46bb10fb |
513 | currently only builds on a subset of the UNIX platforms perl supports. |
514 | Because the data structures are completely different from stdio, perl |
515 | extension modules or external libraries may not work. This |
516 | configuration exists to allow these issues to be worked on. |
517 | |
518 | This option requires the 'sfio' package to have been built and installed. |
519 | A (fairly old) version of sfio is in CPAN, and work is in progress to make |
520 | it more easily buildable by adding Configure support. |
521 | |
522 | You select this option by |
523 | |
524 | sh Configure -Duseperlio -Dusesfio |
525 | |
526 | If you have already selected -Duseperlio, and if Configure detects |
527 | that you have sfio, then sfio will be the default suggested by |
528 | Configure. |
529 | |
1ec51d55 |
530 | Note: On some systems, sfio's iffe configuration script fails |
531 | to detect that you have an atexit function (or equivalent). |
33e6ee5f |
532 | Apparently, this is a problem at least for some versions of Linux |
533 | and SunOS 4. |
534 | |
535 | You can test if you have this problem by trying the following shell |
536 | script. (You may have to add some extra cflags and libraries. A |
537 | portable version of this may eventually make its way into Configure.) |
538 | |
539 | #!/bin/sh |
540 | cat > try.c <<'EOCP' |
541 | #include <stdio.h> |
542 | main() { printf("42\n"); } |
543 | EOCP |
544 | cc -o try try.c -lsfio |
545 | val=`./try` |
546 | if test X$val = X42; then |
547 | echo "Your sfio looks ok" |
548 | else |
549 | echo "Your sfio has the exit problem." |
550 | fi |
551 | |
552 | If you have this problem, the fix is to go back to your sfio sources |
553 | and correct iffe's guess about atexit (or whatever is appropriate for |
554 | your platform.) |
555 | |
556 | There also might be a more recent release of Sfio that fixes your |
557 | problem. |
558 | |
46bb10fb |
559 | =item 2. |
560 | |
561 | Normal stdio IO, but with all IO going through calls to the PerlIO |
562 | abstraction layer. This configuration can be used to check that perl and |
563 | extension modules have been correctly converted to use the PerlIO |
564 | abstraction. |
565 | |
566 | This configuration should work on all platforms (but might not). |
567 | |
aa689395 |
568 | You select this option via: |
46bb10fb |
569 | |
570 | sh Configure -Duseperlio -Uusesfio |
571 | |
572 | If you have already selected -Duseperlio, and if Configure does not |
573 | detect sfio, then this will be the default suggested by Configure. |
574 | |
575 | =back |
576 | |
aa689395 |
577 | =head2 Building a shared libperl.so Perl library |
c3edaffb |
578 | |
579 | Currently, for most systems, the main perl executable is built by |
580 | linking the "perl library" libperl.a with perlmain.o, your static |
581 | extensions (usually just DynaLoader.a) and various extra libraries, |
582 | such as -lm. |
583 | |
9d67150a |
584 | On some systems that support dynamic loading, it may be possible to |
585 | replace libperl.a with a shared libperl.so. If you anticipate building |
c3edaffb |
586 | several different perl binaries (e.g. by embedding libperl into |
587 | different programs, or by using the optional compiler extension), then |
9d67150a |
588 | you might wish to build a shared libperl.so so that all your binaries |
c3edaffb |
589 | can share the same library. |
590 | |
591 | The disadvantages are that there may be a significant performance |
9d67150a |
592 | penalty associated with the shared libperl.so, and that the overall |
aa689395 |
593 | mechanism is still rather fragile with respect to different versions |
c3edaffb |
594 | and upgrades. |
595 | |
596 | In terms of performance, on my test system (Solaris 2.5_x86) the perl |
9d67150a |
597 | test suite took roughly 15% longer to run with the shared libperl.so. |
c3edaffb |
598 | Your system and typical applications may well give quite different |
599 | results. |
600 | |
601 | The default name for the shared library is typically something like |
a6006777 |
602 | libperl.so.3.2 (for Perl 5.003_02) or libperl.so.302 or simply |
9d67150a |
603 | libperl.so. Configure tries to guess a sensible naming convention |
c3edaffb |
604 | based on your C library name. Since the library gets installed in a |
605 | version-specific architecture-dependent directory, the exact name |
606 | isn't very important anyway, as long as your linker is happy. |
607 | |
608 | For some systems (mostly SVR4), building a shared libperl is required |
609 | for dynamic loading to work, and hence is already the default. |
610 | |
611 | You can elect to build a shared libperl by |
612 | |
613 | sh Configure -Duseshrplib |
614 | |
615 | To actually build perl, you must add the current working directory to your |
aa689395 |
616 | LD_LIBRARY_PATH environment variable before running make. You can do |
c3edaffb |
617 | this with |
618 | |
619 | LD_LIBRARY_PATH=`pwd`:$LD_LIBRARY_PATH; export LD_LIBRARY_PATH |
620 | |
621 | for Bourne-style shells, or |
622 | |
623 | setenv LD_LIBRARY_PATH `pwd` |
624 | |
625 | for Csh-style shells. You *MUST* do this before running make. |
626 | Folks running NeXT OPENSTEP must substitute DYLD_LIBRARY_PATH for |
627 | LD_LIBRARY_PATH above. |
628 | |
9d67150a |
629 | There is also an potential problem with the shared perl library if you |
630 | want to have more than one "flavor" of the same version of perl (e.g. |
631 | with and without -DDEBUGGING). For example, suppose you build and |
a6006777 |
632 | install a standard Perl 5.004 with a shared library. Then, suppose you |
633 | try to build Perl 5.004 with -DDEBUGGING enabled, but everything else |
9d67150a |
634 | the same, including all the installation directories. How can you |
635 | ensure that your newly built perl will link with your newly built |
7f678428 |
636 | libperl.so.4 rather with the installed libperl.so.4? The answer is |
9d67150a |
637 | that you might not be able to. The installation directory is encoded |
56c6f531 |
638 | in the perl binary with the LD_RUN_PATH environment variable (or |
639 | equivalent ld command-line option). On Solaris, you can override that |
7beaa944 |
640 | with LD_LIBRARY_PATH; on Linux you can't. On Digital Unix, you can |
0dcb58f4 |
641 | override LD_LIBRARY_PATH by setting the _RLD_ROOT environment variable |
7beaa944 |
642 | to point to the perl build directory. |
9d67150a |
643 | |
644 | The only reliable answer is that you should specify a different |
645 | directory for the architecture-dependent library for your -DDEBUGGING |
fb73857a |
646 | version of perl. You can do this by changing all the *archlib* |
9d67150a |
647 | variables in config.sh, namely archlib, archlib_exp, and |
648 | installarchlib, to point to your new architecture-dependent library. |
649 | |
55479bb6 |
650 | =head2 Malloc Issues |
651 | |
652 | Perl relies heavily on malloc(3) to grow data structures as needed, so |
653 | perl's performance can be noticeably affected by the performance of |
654 | the malloc function on your system. |
655 | |
656 | The perl source is shipped with a version of malloc that is very fast |
657 | but somewhat wasteful of space. On the other hand, your system's |
693762b4 |
658 | malloc() function may be a bit slower but also a bit more frugal. |
55479bb6 |
659 | |
660 | For many uses, speed is probably the most important consideration, so |
661 | the default behavior (for most systems) is to use the malloc supplied |
662 | with perl. However, if you will be running very large applications |
663 | (e.g. Tk or PDL) or if your system already has an excellent malloc, or |
664 | if you are experiencing difficulties with extensions that use |
665 | third-party libraries that call malloc, then you might wish to use |
666 | your system's malloc. (Or, you might wish to explore the experimental |
667 | malloc flags discussed below.) |
668 | |
669 | To build without perl's malloc, you can use the Configure command |
670 | |
671 | sh Configure -Uusemymalloc |
672 | |
673 | or you can answer 'n' at the appropriate interactive Configure prompt. |
674 | |
aa689395 |
675 | =head2 Malloc Performance Flags |
c3edaffb |
676 | |
55479bb6 |
677 | If you are using Perl's malloc, you may add one or |
1ec51d55 |
678 | more of the following items to your cflags config.sh variable |
55479bb6 |
679 | to change its behavior in potentially useful ways. You can find out |
1ec51d55 |
680 | more about these flags by reading the malloc.c source. |
55479bb6 |
681 | In a future version of perl, these might be enabled by default. |
c3edaffb |
682 | |
aa689395 |
683 | =over 4 |
684 | |
84902520 |
685 | =item -DPERL_EMERGENCY_SBRK |
2ae324a7 |
686 | |
84902520 |
687 | If PERL_EMERGENCY_SBRK is defined, running out of memory need not be a |
2ae324a7 |
688 | fatal error: a memory pool can allocated by assigning to the special |
1ec51d55 |
689 | variable $^M. See perlvar(1) for more details. |
aa689395 |
690 | |
691 | =item -DPACK_MALLOC |
692 | |
1ec51d55 |
693 | If PACK_MALLOC is defined, malloc.c uses a slightly different |
55479bb6 |
694 | algorithm for small allocations (up to 64 bytes long). Such small |
695 | allocations are quite common in typical Perl scripts. |
aa689395 |
696 | |
1ec51d55 |
697 | The expected memory savings (with 8-byte alignment in $alignbytes) is |
55479bb6 |
698 | about 20% for typical Perl usage. The expected slowdown due to the |
699 | additional malloc overhead is in fractions of a percent. (It is hard |
700 | to measure because of the effect of the saved memory on speed). |
aa689395 |
701 | |
702 | =item -DTWO_POT_OPTIMIZE |
703 | |
1ec51d55 |
704 | If TWO_POT_OPTIMIZE is defined, malloc.c uses a slightly different |
55479bb6 |
705 | algorithm for large allocations that are close to a power of two |
706 | (starting with 16K). Such allocations are typical for big hashes and |
707 | special-purpose scripts, especially image processing. If you will be |
708 | manipulating very large blocks with sizes close to powers of two, it |
709 | might be wise to define this macro. |
aa689395 |
710 | |
55479bb6 |
711 | The expected saving of memory is 0-100% (100% in applications which |
712 | require most memory in such 2**n chunks). The expected slowdown is |
aa689395 |
713 | negligible. |
714 | |
715 | =back |
716 | |
3bf462b8 |
717 | =head2 Building a debugging perl |
718 | |
719 | You can run perl scripts under the perl debugger at any time with |
3fe9a6f1 |
720 | B<perl -d your_script>. If, however, you want to debug perl itself, |
3bf462b8 |
721 | you probably want to do |
722 | |
723 | sh Configure -Doptimize='-g' |
724 | |
203c3eec |
725 | This will do two independent things: First, it will force compilation |
726 | to use cc -g so that you can use your system's debugger on the |
727 | executable. (Note: Your system may actually require something like |
728 | cc -g2. Check you man pages for cc(1) and also any hint file for your |
729 | system.) Second, it will add -DDEBUGGING to your ccflags variable in |
1ec51d55 |
730 | config.sh so that you can use B<perl -D> to access perl's internal |
203c3eec |
731 | state. (Note: Configure will only add -DDEBUGGING by |
1ec51d55 |
732 | default if you are not reusing your old config.sh. If you want to |
733 | reuse your old config.sh, then you can just edit it and change the |
3fe9a6f1 |
734 | optimize and ccflags variables by hand and then propagate your changes |
203c3eec |
735 | as shown in L<"Propagating your changes to config.sh"> below.) |
736 | |
737 | You can actually specify -g and -DDEBUGGING independently, but usually |
738 | it's convenient to have both. |
3bf462b8 |
739 | |
740 | If you are using a shared libperl, see the warnings about multiple |
741 | versions of perl under L<Building a shared libperl.so Perl library>. |
742 | |
aa689395 |
743 | =head2 Other Compiler Flags |
744 | |
745 | For most users, all of the Configure defaults are fine. However, |
746 | you can change a number of factors in the way perl is built |
1ec51d55 |
747 | by adding appropriate -D directives to your ccflags variable in |
aa689395 |
748 | config.sh. |
749 | |
750 | For example, you can replace the rand() and srand() functions in the |
751 | perl source by any other random number generator by a trick such as the |
752 | following: |
753 | |
754 | sh Configure -Dccflags='-Drand=random -Dsrand=srandom' |
755 | |
203c3eec |
756 | or by adding -Drand=random and -Dsrand=srandom to your ccflags |
757 | at the appropriate Configure prompt. (Note: Although this worked for |
758 | me, it might not work for you if your system's header files give |
759 | different prototypes for rand() and random() or srand() and srandom().) |
760 | |
761 | You should also run Configure interactively to verify that a hint file |
762 | doesn't inadvertently override your ccflags setting. (Hints files |
763 | shouldn't do that, but some might.) |
c3edaffb |
764 | |
8e07c86e |
765 | =head2 What if it doesn't work? |
766 | |
767 | =over 4 |
768 | |
25f94b33 |
769 | =item Running Configure Interactively |
770 | |
771 | If Configure runs into trouble, remember that you can always run |
772 | Configure interactively so that you can check (and correct) its |
773 | guesses. |
774 | |
775 | All the installation questions have been moved to the top, so you don't |
aa689395 |
776 | have to wait for them. Once you've handled them (and your C compiler and |
1ec51d55 |
777 | flags) you can type &-d at the next Configure prompt and Configure |
25f94b33 |
778 | will use the defaults from then on. |
779 | |
780 | If you find yourself trying obscure command line incantations and |
781 | config.over tricks, I recommend you run Configure interactively |
782 | instead. You'll probably save yourself time in the long run. |
783 | |
aa689395 |
784 | =item Hint files |
8e07c86e |
785 | |
786 | The perl distribution includes a number of system-specific hints files |
787 | in the hints/ directory. If one of them matches your system, Configure |
788 | will offer to use that hint file. |
789 | |
790 | Several of the hint files contain additional important information. |
791 | If you have any problems, it is a good idea to read the relevant hint |
1ec51d55 |
792 | file for further information. See hints/solaris_2.sh for an |
8e07c86e |
793 | extensive example. |
794 | |
edb1cbcb |
795 | =item *** WHOA THERE!!! *** |
796 | |
797 | Occasionally, Configure makes a wrong guess. For example, on SunOS |
798 | 4.1.3, Configure incorrectly concludes that tzname[] is in the |
799 | standard C library. The hint file is set up to correct for this. You |
800 | will see a message: |
801 | |
802 | *** WHOA THERE!!! *** |
803 | The recommended value for $d_tzname on this machine was "undef"! |
804 | Keep the recommended value? [y] |
805 | |
806 | You should always keep the recommended value unless, after reading the |
807 | relevant section of the hint file, you are sure you want to try |
808 | overriding it. |
809 | |
810 | If you are re-using an old config.sh, the word "previous" will be |
811 | used instead of "recommended". Again, you will almost always want |
812 | to keep the previous value, unless you have changed something on your |
813 | system. |
814 | |
815 | For example, suppose you have added libgdbm.a to your system |
816 | and you decide to reconfigure perl to use GDBM_File. When you run |
817 | Configure again, you will need to add -lgdbm to the list of libraries. |
818 | Now, Configure will find your gdbm library and will issue a message: |
819 | |
820 | *** WHOA THERE!!! *** |
821 | The previous value for $i_gdbm on this machine was "undef"! |
822 | Keep the previous value? [y] |
823 | |
1ec51d55 |
824 | In this case, you do not want to keep the previous value, so you |
c3edaffb |
825 | should answer 'n'. (You'll also have to manually add GDBM_File to |
edb1cbcb |
826 | the list of dynamic extensions to build.) |
827 | |
8e07c86e |
828 | =item Changing Compilers |
829 | |
830 | If you change compilers or make other significant changes, you should |
1ec51d55 |
831 | probably not re-use your old config.sh. Simply remove it or |
8e07c86e |
832 | rename it, e.g. mv config.sh config.sh.old. Then rerun Configure |
833 | with the options you want to use. |
834 | |
1ec51d55 |
835 | This is a common source of problems. If you change from cc to |
836 | gcc, you should almost always remove your old config.sh. |
8e07c86e |
837 | |
c3edaffb |
838 | =item Propagating your changes to config.sh |
8e07c86e |
839 | |
1ec51d55 |
840 | If you make any changes to config.sh, you should propagate |
841 | them to all the .SH files by running |
842 | |
843 | sh Configure -S |
844 | |
845 | You will then have to rebuild by running |
9d67150a |
846 | |
847 | make depend |
848 | make |
8e07c86e |
849 | |
850 | =item config.over |
851 | |
852 | You can also supply a shell script config.over to over-ride Configure's |
853 | guesses. It will get loaded up at the very end, just before config.sh |
854 | is created. You have to be careful with this, however, as Configure |
d52d4e46 |
855 | does no checking that your changes make sense. See the section on |
7f678428 |
856 | L<"Changing the installation directory"> for an example. |
8e07c86e |
857 | |
858 | =item config.h |
859 | |
1ec51d55 |
860 | Many of the system dependencies are contained in config.h. |
861 | Configure builds config.h by running the config_h.SH script. |
862 | The values for the variables are taken from config.sh. |
8e07c86e |
863 | |
1ec51d55 |
864 | If there are any problems, you can edit config.h directly. Beware, |
865 | though, that the next time you run Configure, your changes will be |
8e07c86e |
866 | lost. |
867 | |
868 | =item cflags |
869 | |
870 | If you have any additional changes to make to the C compiler command |
1ec51d55 |
871 | line, they can be made in cflags.SH. For instance, to turn off the |
872 | optimizer on toke.c, find the line in the switch structure for |
873 | toke.c and put the command optimize='-g' before the ;; . You |
874 | can also edit cflags directly, but beware that your changes will be |
875 | lost the next time you run Configure. |
8e07c86e |
876 | |
1ec51d55 |
877 | To change the C flags for all the files, edit config.sh |
878 | and change either $ccflags or $optimize, |
879 | and then re-run |
880 | |
881 | sh Configure -S |
882 | make depend |
8e07c86e |
883 | |
aa689395 |
884 | =item No sh |
8e07c86e |
885 | |
dfe9444c |
886 | If you don't have sh, you'll have to copy the sample file Porting/config_H |
887 | to config.h and edit the config.h to reflect your system's peculiarities. |
8e07c86e |
888 | You'll probably also have to extensively modify the extension building |
889 | mechanism. |
890 | |
c3edaffb |
891 | =item Porting information |
892 | |
2ae324a7 |
893 | Specific information for the OS/2, Plan9, VMS and Win32 ports is in the |
1ec51d55 |
894 | corresponding README files and subdirectories. Additional information, |
895 | including a glossary of all those config.sh variables, is in the Porting |
c3edaffb |
896 | subdirectory. |
897 | |
7f678428 |
898 | Ports for other systems may also be available. You should check out |
1ec51d55 |
899 | http://www.perl.com/CPAN/ports for current information on ports to |
7f678428 |
900 | various other operating systems. |
901 | |
8e07c86e |
902 | =back |
903 | |
904 | =head1 make depend |
905 | |
906 | This will look for all the includes. |
1ec51d55 |
907 | The output is stored in makefile. The only difference between |
908 | Makefile and makefile is the dependencies at the bottom of |
909 | makefile. If you have to make any changes, you should edit |
910 | makefile, not Makefile since the Unix make command reads |
911 | makefile first. (On non-Unix systems, the output may be stored in |
c3edaffb |
912 | a different file. Check the value of $firstmakefile in your config.sh |
913 | if in doubt.) |
8e07c86e |
914 | |
915 | Configure will offer to do this step for you, so it isn't listed |
916 | explicitly above. |
917 | |
918 | =head1 make |
919 | |
920 | This will attempt to make perl in the current directory. |
921 | |
922 | If you can't compile successfully, try some of the following ideas. |
7f678428 |
923 | If none of them help, and careful reading of the error message and |
924 | the relevant manual pages on your system doesn't help, you can |
925 | send a message to either the comp.lang.perl.misc newsgroup or to |
926 | perlbug@perl.com with an accurate description of your problem. |
aa689395 |
927 | See L<"Reporting Problems"> below. |
8e07c86e |
928 | |
929 | =over 4 |
930 | |
1ec51d55 |
931 | =item hints |
8e07c86e |
932 | |
933 | If you used a hint file, try reading the comments in the hint file |
934 | for further tips and information. |
935 | |
1ec51d55 |
936 | =item extensions |
8e07c86e |
937 | |
1ec51d55 |
938 | If you can successfully build miniperl, but the process crashes |
c3edaffb |
939 | during the building of extensions, you should run |
940 | |
941 | make minitest |
942 | |
943 | to test your version of miniperl. |
944 | |
e57fd563 |
945 | =item locale |
946 | |
947 | If you have any locale-related environment variables set, try |
948 | unsetting them. I have some reports that some versions of IRIX hang |
949 | while running B<./miniperl configpm> with locales other than the C |
3e6e419a |
950 | locale. See the discussion under L<"make test"> below about locales |
951 | and the whole L<Locale problems> section in the file pod/perllocale.pod. |
952 | The latter is especially useful if you see something like this |
953 | |
954 | perl: warning: Setting locale failed. |
955 | perl: warning: Please check that your locale settings: |
956 | LC_ALL = "En_US", |
957 | LANG = (unset) |
958 | are supported and installed on your system. |
959 | perl: warning: Falling back to the standard locale ("C"). |
960 | |
961 | at Perl startup. |
e57fd563 |
962 | |
1ec51d55 |
963 | =item malloc duplicates |
c3edaffb |
964 | |
aa689395 |
965 | If you get duplicates upon linking for malloc et al, add -DHIDEMYMALLOC |
966 | or -DEMBEDMYMALLOC to your ccflags variable in config.sh. |
c3edaffb |
967 | |
7f678428 |
968 | =item varargs |
c3edaffb |
969 | |
970 | If you get varargs problems with gcc, be sure that gcc is installed |
971 | correctly. When using gcc, you should probably have i_stdarg='define' |
972 | and i_varargs='undef' in config.sh. The problem is usually solved by |
973 | running fixincludes correctly. If you do change config.sh, don't |
7f678428 |
974 | forget to propagate your changes (see |
975 | L<"Propagating your changes to config.sh"> below). |
976 | See also the L<"vsprintf"> item below. |
c3edaffb |
977 | |
1ec51d55 |
978 | =item croak |
c3edaffb |
979 | |
980 | If you get error messages such as the following (the exact line |
981 | numbers will vary in different versions of perl): |
982 | |
983 | util.c: In function `Perl_croak': |
984 | util.c:962: number of arguments doesn't match prototype |
985 | proto.h:45: prototype declaration |
986 | |
987 | it might well be a symptom of the gcc "varargs problem". See the |
7f678428 |
988 | previous L<"varargs"> item. |
c3edaffb |
989 | |
9d67150a |
990 | =item Solaris and SunOS dynamic loading |
c3edaffb |
991 | |
992 | If you have problems with dynamic loading using gcc on SunOS or |
993 | Solaris, and you are using GNU as and GNU ld, you may need to add |
1ec51d55 |
994 | -B/bin/ (for SunOS) or -B/usr/ccs/bin/ (for Solaris) to your |
c3edaffb |
995 | $ccflags, $ldflags, and $lddlflags so that the system's versions of as |
6877a1cf |
996 | and ld are used. Note that the trailing '/' is required. |
997 | Alternatively, you can use the GCC_EXEC_PREFIX |
c3edaffb |
998 | environment variable to ensure that Sun's as and ld are used. Consult |
1ec51d55 |
999 | your gcc documentation for further information on the -B option and |
c3edaffb |
1000 | the GCC_EXEC_PREFIX variable. |
1001 | |
7beaa944 |
1002 | One convenient way to ensure you are not using GNU as and ld is to |
1003 | invoke Configure with |
1004 | |
1005 | sh Configure -Dcc='gcc -B/usr/ccs/bin/' |
1006 | |
1007 | for Solaris systems. For a SunOS system, you must use -B/bin/ |
1008 | instead. |
1009 | |
84902520 |
1010 | Alternatively, recent versions of GNU ld reportedly work if you |
1011 | include C<-Wl,-export-dynamic> in the ccdlflags variable in |
1012 | config.sh. |
1013 | |
9d67150a |
1014 | =item ld.so.1: ./perl: fatal: relocation error: |
1015 | |
1016 | If you get this message on SunOS or Solaris, and you're using gcc, |
7f678428 |
1017 | it's probably the GNU as or GNU ld problem in the previous item |
1018 | L<"Solaris and SunOS dynamic loading">. |
9d67150a |
1019 | |
1ec51d55 |
1020 | =item LD_LIBRARY_PATH |
c3edaffb |
1021 | |
1022 | If you run into dynamic loading problems, check your setting of |
aa689395 |
1023 | the LD_LIBRARY_PATH environment variable. If you're creating a static |
1024 | Perl library (libperl.a rather than libperl.so) it should build |
c3edaffb |
1025 | fine with LD_LIBRARY_PATH unset, though that may depend on details |
1026 | of your local set-up. |
1027 | |
1028 | =item dlopen: stub interception failed |
1029 | |
1030 | The primary cause of the 'dlopen: stub interception failed' message is |
1031 | that the LD_LIBRARY_PATH environment variable includes a directory |
1032 | which is a symlink to /usr/lib (such as /lib). |
1033 | |
aa689395 |
1034 | The reason this causes a problem is quite subtle. The file libdl.so.1.0 |
c3edaffb |
1035 | actually *only* contains functions which generate 'stub interception |
1036 | failed' errors! The runtime linker intercepts links to |
1037 | "/usr/lib/libdl.so.1.0" and links in internal implementation of those |
1038 | functions instead. [Thanks to Tim Bunce for this explanation.] |
1039 | |
aa689395 |
1040 | =item nm extraction |
c3edaffb |
1041 | |
1042 | If Configure seems to be having trouble finding library functions, |
1043 | try not using nm extraction. You can do this from the command line |
1044 | with |
1045 | |
1046 | sh Configure -Uusenm |
1047 | |
1048 | or by answering the nm extraction question interactively. |
1ec51d55 |
1049 | If you have previously run Configure, you should not reuse your old |
c3edaffb |
1050 | config.sh. |
1051 | |
7f678428 |
1052 | =item vsprintf |
c3edaffb |
1053 | |
1054 | If you run into problems with vsprintf in compiling util.c, the |
1055 | problem is probably that Configure failed to detect your system's |
1056 | version of vsprintf(). Check whether your system has vprintf(). |
1057 | (Virtually all modern Unix systems do.) Then, check the variable |
1058 | d_vprintf in config.sh. If your system has vprintf, it should be: |
1059 | |
1060 | d_vprintf='define' |
1061 | |
1062 | If Configure guessed wrong, it is likely that Configure guessed wrong |
1063 | on a number of other common functions too. You are probably better off |
1064 | re-running Configure without using nm extraction (see previous item). |
1065 | |
3fe9a6f1 |
1066 | =item do_aspawn |
1067 | |
1068 | If you run into problems relating to do_aspawn or do_spawn, the |
1069 | problem is probably that Configure failed to detect your system's |
1070 | fork() function. Follow the procedure in the previous items |
1071 | on L<"vsprintf"> and L<"nm extraction">. |
1072 | |
84902520 |
1073 | =item __inet_* errors |
1074 | |
1075 | If you receive unresolved symbol errors during Perl build and/or test |
1076 | referring to __inet_* symbols, check to see whether BIND 8.1 is |
1077 | installed. It installs a /usr/local/include/arpa/inet.h that refers to |
1078 | these symbols. Versions of BIND later than 8.1 do not install inet.h |
1079 | in that location and avoid the errors. You should probably update to a |
1080 | newer version of BIND. If you can't, you can either link with the |
1081 | updated resolver library provided with BIND 8.1 or rename |
1082 | /usr/local/bin/arpa/inet.h during the Perl build and test process to |
1083 | avoid the problem. |
1084 | |
aa689395 |
1085 | =item Optimizer |
c3edaffb |
1086 | |
9d67150a |
1087 | If you can't compile successfully, try turning off your compiler's |
aa689395 |
1088 | optimizer. Edit config.sh and change the line |
9d67150a |
1089 | |
1090 | optimize='-O' |
1091 | |
1092 | to something like |
1093 | |
1094 | optimize=' ' |
1095 | |
1096 | then propagate your changes with B<sh Configure -S> and rebuild |
1097 | with B<make depend; make>. |
1098 | |
1ec51d55 |
1099 | =item CRIPPLED_CC |
9d67150a |
1100 | |
1ec51d55 |
1101 | If you still can't compile successfully, try adding a -DCRIPPLED_CC |
56c6f531 |
1102 | flag. (Just because you get no errors doesn't mean it compiled right!) |
1103 | This simplifies some complicated expressions for compilers that get |
1104 | indigestion easily. |
9d67150a |
1105 | |
1106 | =item Missing functions |
1107 | |
1108 | If you have missing routines, you probably need to add some library or |
1109 | other, or you need to undefine some feature that Configure thought was |
1110 | there but is defective or incomplete. Look through config.h for |
1111 | likely suspects. |
8e07c86e |
1112 | |
1ec51d55 |
1113 | =item toke.c |
8e07c86e |
1114 | |
1ec51d55 |
1115 | Some compilers will not compile or optimize the larger files (such as |
1116 | toke.c) without some extra switches to use larger jump offsets or |
1117 | allocate larger internal tables. You can customize the switches for |
1118 | each file in cflags. It's okay to insert rules for specific files into |
1119 | makefile since a default rule only takes effect in the absence of a |
8e07c86e |
1120 | specific rule. |
1121 | |
7f678428 |
1122 | =item Missing dbmclose |
8e07c86e |
1123 | |
c3edaffb |
1124 | SCO prior to 3.2.4 may be missing dbmclose(). An upgrade to 3.2.4 |
1125 | that includes libdbm.nfs (which includes dbmclose()) may be available. |
8e07c86e |
1126 | |
f3d9a6ba |
1127 | =item Note (probably harmless): No library found for -lsomething |
7f678428 |
1128 | |
1129 | If you see such a message during the building of an extension, but |
1130 | the extension passes its tests anyway (see L<"make test"> below), |
1131 | then don't worry about the warning message. The extension |
1132 | Makefile.PL goes looking for various libraries needed on various |
aa689395 |
1133 | systems; few systems will need all the possible libraries listed. |
7f678428 |
1134 | For example, a system may have -lcposix or -lposix, but it's |
1135 | unlikely to have both, so most users will see warnings for the one |
f3d9a6ba |
1136 | they don't have. The phrase 'probably harmless' is intended to |
1137 | reassure you that nothing unusual is happening, and the build |
1138 | process is continuing. |
7f678428 |
1139 | |
1140 | On the other hand, if you are building GDBM_File and you get the |
1141 | message |
1142 | |
f3d9a6ba |
1143 | Note (probably harmless): No library found for -lgdbm |
7f678428 |
1144 | |
1145 | then it's likely you're going to run into trouble somewhere along |
1146 | the line, since it's hard to see how you can use the GDBM_File |
1147 | extension without the -lgdbm library. |
1148 | |
1149 | It is true that, in principle, Configure could have figured all of |
1150 | this out, but Configure and the extension building process are not |
1151 | quite that tightly coordinated. |
1152 | |
aa689395 |
1153 | =item sh: ar: not found |
1154 | |
1155 | This is a message from your shell telling you that the command 'ar' |
1156 | was not found. You need to check your PATH environment variable to |
1157 | make sure that it includes the directory with the 'ar' command. This |
1ec51d55 |
1158 | is a common problem on Solaris, where 'ar' is in the /usr/ccs/bin |
aa689395 |
1159 | directory. |
1160 | |
1161 | =item db-recno failure on tests 51, 53 and 55 |
1162 | |
1163 | Old versions of the DB library (including the DB library which comes |
1164 | with FreeBSD 2.1) had broken handling of recno databases with modified |
1165 | bval settings. Upgrade your DB library or OS. |
1166 | |
1ec51d55 |
1167 | =item Miscellaneous |
8e07c86e |
1168 | |
1169 | Some additional things that have been reported for either perl4 or perl5: |
1170 | |
1171 | Genix may need to use libc rather than libc_s, or #undef VARARGS. |
1172 | |
1173 | NCR Tower 32 (OS 2.01.01) may need -W2,-Sl,2000 and #undef MKDIR. |
1174 | |
1ec51d55 |
1175 | UTS may need one or more of -DCRIPPLED_CC, -K or -g, and undef LSTAT. |
8e07c86e |
1176 | |
1177 | If you get syntax errors on '(', try -DCRIPPLED_CC. |
1178 | |
1179 | Machines with half-implemented dbm routines will need to #undef I_ODBM |
1180 | |
8e07c86e |
1181 | =back |
1182 | |
1183 | =head1 make test |
1184 | |
84902520 |
1185 | This will run the regression tests on the perl you just made (you |
1186 | should run plain 'make' before 'make test' otherwise you won't have a |
1187 | complete build). If 'make test' doesn't say "All tests successful" |
1188 | then something went wrong. See the file t/README in the t subdirectory. |
1189 | |
84902520 |
1190 | Note that you can't run the tests in background if this disables |
fb73857a |
1191 | opening of /dev/tty. You can use 'make test-notty' in that case but |
1192 | a few tty tests will be skipped. |
c3edaffb |
1193 | |
1ec51d55 |
1194 | If make test bombs out, just cd to the t directory and run ./TEST |
1195 | by hand to see if it makes any difference. If individual tests |
c3edaffb |
1196 | bomb, you can run them by hand, e.g., |
8e07c86e |
1197 | |
1198 | ./perl op/groups.t |
1199 | |
aa689395 |
1200 | Another way to get more detailed information about failed tests and |
1ec51d55 |
1201 | individual subtests is to cd to the t directory and run |
aa689395 |
1202 | |
1203 | ./perl harness |
1204 | |
fb73857a |
1205 | (this assumes that most basic tests succeed, since harness uses |
aa689395 |
1206 | complicated constructs). |
1207 | |
fb73857a |
1208 | You should also read the individual tests to see if there are any helpful |
c3edaffb |
1209 | comments that apply to your system. |
1210 | |
1ec51d55 |
1211 | Note: One possible reason for errors is that some external programs |
c07a80fd |
1212 | may be broken due to the combination of your environment and the way |
3fe9a6f1 |
1213 | B<make test> exercises them. For example, this may happen if you have |
1ec51d55 |
1214 | one or more of these environment variables set: LC_ALL LC_CTYPE |
1215 | LC_COLLATE LANG. In some versions of UNIX, the non-English locales |
e57fd563 |
1216 | are known to cause programs to exhibit mysterious errors. |
1217 | |
1218 | If you have any of the above environment variables set, please try |
aa689395 |
1219 | |
1220 | setenv LC_ALL C |
1221 | |
1222 | (for C shell) or |
1223 | |
1224 | LC_ALL=C;export LC_ALL |
1225 | |
1ec51d55 |
1226 | for Bourne or Korn shell) from the command line and then retry |
1227 | make test. If the tests then succeed, you may have a broken program that |
aa689395 |
1228 | is confusing the testing. Please run the troublesome test by hand as |
e57fd563 |
1229 | shown above and see whether you can locate the program. Look for |
1ec51d55 |
1230 | things like: exec, `backquoted command`, system, open("|...") or |
1231 | open("...|"). All these mean that Perl is trying to run some |
e57fd563 |
1232 | external program. |
eed2e782 |
1233 | |
8e07c86e |
1234 | =head1 make install |
1235 | |
1236 | This will put perl into the public directory you specified to |
1ec51d55 |
1237 | Configure; by default this is /usr/local/bin. It will also try |
8e07c86e |
1238 | to put the man pages in a reasonable place. It will not nroff the man |
aa689395 |
1239 | pages, however. You may need to be root to run B<make install>. If you |
8e07c86e |
1240 | are not root, you must own the directories in question and you should |
1241 | ignore any messages about chown not working. |
1242 | |
1243 | If you want to see exactly what will happen without installing |
1244 | anything, you can run |
4633a7c4 |
1245 | |
8e07c86e |
1246 | ./perl installperl -n |
1247 | ./perl installman -n |
1248 | |
1ec51d55 |
1249 | make install will install the following: |
8e07c86e |
1250 | |
1251 | perl, |
1252 | perl5.nnn where nnn is the current release number. This |
1253 | will be a link to perl. |
1254 | suidperl, |
1255 | sperl5.nnn If you requested setuid emulation. |
1256 | a2p awk-to-perl translator |
1257 | cppstdin This is used by perl -P, if your cc -E can't |
1258 | read from stdin. |
1259 | c2ph, pstruct Scripts for handling C structures in header files. |
1260 | s2p sed-to-perl translator |
1261 | find2perl find-to-perl translator |
aa689395 |
1262 | h2ph Extract constants and simple macros from C headers |
8e07c86e |
1263 | h2xs Converts C .h header files to Perl extensions. |
24b3df7f |
1264 | perlbug Tool to report bugs in Perl. |
8e07c86e |
1265 | perldoc Tool to read perl's pod documentation. |
aa689395 |
1266 | pl2pm Convert Perl 4 .pl files to Perl 5 .pm modules |
8e07c86e |
1267 | pod2html, Converters from perl's pod documentation format |
aa689395 |
1268 | pod2latex, to other useful formats. |
1269 | pod2man, and |
1270 | pod2text |
1271 | splain Describe Perl warnings and errors |
8e07c86e |
1272 | |
1273 | library files in $privlib and $archlib specified to |
1274 | Configure, usually under /usr/local/lib/perl5/. |
1275 | man pages in the location specified to Configure, usually |
1276 | something like /usr/local/man/man1. |
1277 | module in the location specified to Configure, usually |
1278 | man pages under /usr/local/lib/perl5/man/man3. |
1279 | pod/*.pod in $privlib/pod/. |
1280 | |
4633a7c4 |
1281 | Installperl will also create the library directories $siteperl and |
1282 | $sitearch listed in config.sh. Usually, these are something like |
24b3df7f |
1283 | /usr/local/lib/perl5/site_perl/ |
1284 | /usr/local/lib/perl5/site_perl/$archname |
4633a7c4 |
1285 | where $archname is something like sun4-sunos. These directories |
1286 | will be used for installing extensions. |
1287 | |
56c6f531 |
1288 | Perl's *.h header files and the libperl.a library are also installed |
1289 | under $archlib so that any user may later build new extensions, run the |
1290 | optional Perl compiler, or embed the perl interpreter into another |
1291 | program even if the Perl source is no longer available. |
8e07c86e |
1292 | |
aa689395 |
1293 | =head1 Coexistence with earlier versions of perl5 |
4633a7c4 |
1294 | |
693762b4 |
1295 | WARNING: The upgrade from 5.004_0x to 5.005 is going to be a bit |
1296 | tricky. See L<"Upgrading from 5.004 to 5.005"> below. |
1297 | |
1298 | In general, you can usually safely upgrade from one version of Perl (e.g. |
1299 | 5.004_04) to another similar version (e.g. 5.004_05) without re-compiling |
1300 | all of your add-on extensions. You can also safely leave the old version |
1301 | around in case the new version causes you problems for some reason. |
1302 | For example, if you want to be sure that your script continues to run |
1303 | with 5.004_04, simplly replace the '#!/usr/local/bin/perl' line at the |
1304 | top of the script with the particular version you want to run, e.g. |
1305 | #!/usr/local/bin/perl5.00404. |
1306 | |
1307 | (If you are upgrading from 5.002 or earlier, beware that some of the |
1308 | standard library files have changed in incompatible ways, so you are |
1309 | probably better off starting with a fresh installation.) |
1310 | |
1311 | The standard library files in /usr/local/lib/perl5 should be usable by |
1312 | all versions of perl5 after 5.002. An exception is the diagnostics.pm |
1313 | module. Since that module uses the /usr/local/lib/perl5/pod/perldiag.pod |
1314 | documentation file, the C<use diagnostics;> pragma and the splain script |
1315 | will only identify and explain any warnings or errors that the most |
1316 | recently-installed version of perl can generate. Usually, this is not |
1317 | a problem. |
1318 | |
1319 | Most extensions will probably not need to be recompiled to use |
1320 | with a newer version of perl. Here is how it is supposed to work. |
1321 | (These examples assume you accept all the Configure defaults.) |
1322 | |
1323 | The directories searched by version 5.004_05 will be |
1324 | |
1325 | /usr/local/lib/perl5/archname/5.00405 |
1326 | /usr/local/lib/perl5/ |
1327 | /usr/local/lib/perl5/site_perl/archname |
1328 | /usr/local/lib/perl5/site_perl |
1329 | |
1330 | while the directories searched by version 5.004_04 are |
1331 | |
1332 | /usr/local/lib/perl5/archname/5.00404 |
1333 | /usr/local/lib/perl5/ |
1334 | /usr/local/lib/perl5/site_perl/archname |
1335 | /usr/local/lib/perl5/site_perl |
1336 | |
1337 | When you install an add-on extension, it gets installed into |
1338 | /usr/local/lib/perl5/site_perl/archname (if it is architecture-specific.) |
1339 | This directory is deliberately NOT version-specific so that both 5.004_04 |
1340 | and 5.004_05 can use the extension. |
1341 | |
1342 | However, if you do run into problems, and you want to continue to |
1343 | use the old version of perl along with your extension, simply move |
4633a7c4 |
1344 | those extension files to the appropriate version directory, such as |
693762b4 |
1345 | /usr/local/lib/perl5/archname/5.00404. Then use your newer version of |
1346 | perl to rebuild and re-install the extension into site_perl. This way, |
1347 | Perl 5.004_04 will find your files in the 5.00404 directory, and |
1348 | newer versions of perl will find your newer extension in the site_perl |
1349 | directory. |
1350 | |
1351 | =head2 Maintaining completely separate versions |
4633a7c4 |
1352 | |
1ec51d55 |
1353 | Many users prefer to keep all versions of perl in completely |
d52d4e46 |
1354 | separate directories. One convenient way to do this is by |
1355 | using a separate prefix for each version, such as |
1356 | |
46bb10fb |
1357 | sh Configure -Dprefix=/opt/perl5.004 |
d52d4e46 |
1358 | |
46bb10fb |
1359 | and adding /opt/perl5.004/bin to the shell PATH variable. Such users |
d52d4e46 |
1360 | may also wish to add a symbolic link /usr/local/bin/perl so that |
1361 | scripts can still start with #!/usr/local/bin/perl. |
1362 | |
693762b4 |
1363 | Others might share a common directory for maintenance sub-versions |
1364 | (e.g. 5.004 for all 5.004_0x versions), but change directory with |
1365 | each major version. |
1366 | |
6877a1cf |
1367 | If you are installing a development subversion, you probably ought to |
1368 | seriously consider using a separate directory, since development |
1369 | subversions may not have all the compatibility wrinkles ironed out |
1370 | yet. |
1371 | |
693762b4 |
1372 | =head2 Upgrading from 5.004 to 5.005 |
1373 | |
1374 | Extensions compiled with versions of perl prior to 5.004_50 will need |
1375 | to be recompiled to be used with 5.004_50 and later. |
1376 | |
1377 | If you wish to continue using those extensions under 5.004_04, for |
1378 | example, then you need to move those extensions from their current |
1379 | direcotries, which are something like |
1380 | |
1381 | /usr/local/lib/perl5/site_perl/ |
1382 | /usr/local/lib/perl5/site_perl/archname |
1383 | |
1384 | to the version-specific directory such as |
1385 | |
1386 | /usr/local/lib/perl5/archname/5.00404 |
1387 | |
1388 | as described above. |
1389 | |
1390 | Once you have moved the 5.00404 versions of the extensions out of the |
1391 | way, you may recompile and reinstall with 5.005. |
1392 | |
8e07c86e |
1393 | =head1 Coexistence with perl4 |
1394 | |
1395 | You can safely install perl5 even if you want to keep perl4 around. |
1396 | |
1ec51d55 |
1397 | By default, the perl5 libraries go into /usr/local/lib/perl5/, so |
1398 | they don't override the perl4 libraries in /usr/local/lib/perl/. |
8e07c86e |
1399 | |
1400 | In your /usr/local/bin directory, you should have a binary named |
1ec51d55 |
1401 | perl4.036. That will not be touched by the perl5 installation |
8e07c86e |
1402 | process. Most perl4 scripts should run just fine under perl5. |
1403 | However, if you have any scripts that require perl4, you can replace |
1ec51d55 |
1404 | the #! line at the top of them by #!/usr/local/bin/perl4.036 |
edb1cbcb |
1405 | (or whatever the appropriate pathname is). See pod/perltrap.pod |
1406 | for possible problems running perl4 scripts under perl5. |
8e07c86e |
1407 | |
aa689395 |
1408 | =head1 cd /usr/include; h2ph *.h sys/*.h |
1409 | |
1410 | Some perl scripts need to be able to obtain information from |
1411 | the system header files. This command will convert the most commonly used |
1ec51d55 |
1412 | header files in /usr/include into files that can be easily interpreted |
aa689395 |
1413 | by perl. These files will be placed in the architectural library directory |
1ec51d55 |
1414 | you specified to Configure; by default this is |
1415 | /usr/local/lib/perl5/ARCH/VERSION, where ARCH is your architecture |
1416 | (such as sun4-solaris) and VERSION is the version of perl you are |
1417 | building (for example, 5.004). |
aa689395 |
1418 | |
1ec51d55 |
1419 | Note: Due to differences in the C and perl languages, the |
aa689395 |
1420 | conversion of the header files is not perfect. You will probably have |
1421 | to hand-edit some of the converted files to get them to parse |
1422 | correctly. For example, h2ph breaks spectacularly on type casting and |
1423 | certain structures. |
1424 | |
fb73857a |
1425 | =head1 installhtml --help |
aa689395 |
1426 | |
3e3baf6d |
1427 | Some sites may wish to make perl documentation available in HTML |
1428 | format. The installhtml utility can be used to convert pod |
fb73857a |
1429 | documentation into linked HTML files and install them. |
aa689395 |
1430 | |
fb73857a |
1431 | The following command-line is an example of one used to convert |
3e3baf6d |
1432 | perl documentation: |
aa689395 |
1433 | |
3e3baf6d |
1434 | ./installhtml \ |
1435 | --podroot=. \ |
1436 | --podpath=lib:ext:pod:vms \ |
1437 | --recurse \ |
1438 | --htmldir=/perl/nmanual \ |
1439 | --htmlroot=/perl/nmanual \ |
1440 | --splithead=pod/perlipc \ |
1441 | --splititem=pod/perlfunc \ |
1442 | --libpods=perlfunc:perlguts:perlvar:perlrun:perlop \ |
1443 | --verbose |
1444 | |
1445 | See the documentation in installhtml for more details. It can take |
1446 | many minutes to execute a large installation and you should expect to |
1447 | see warnings like "no title", "unexpected directive" and "cannot |
1448 | resolve" as the files are processed. We are aware of these problems |
1449 | (and would welcome patches for them). |
aa689395 |
1450 | |
fb73857a |
1451 | You may find it helpful to run installhtml twice. That should reduce |
1452 | the number of "cannot resolve" warnings. |
1453 | |
aa689395 |
1454 | =head1 cd pod && make tex && (process the latex files) |
1455 | |
1456 | Some sites may also wish to make the documentation in the pod/ directory |
1457 | available in TeX format. Type |
1458 | |
1459 | (cd pod && make tex && <process the latex files>) |
1460 | |
1461 | =head1 Reporting Problems |
1462 | |
1463 | If you have difficulty building perl, and none of the advice in this |
1464 | file helps, and careful reading of the error message and the relevant |
1465 | manual pages on your system doesn't help either, then you should send a |
1466 | message to either the comp.lang.perl.misc newsgroup or to |
1467 | perlbug@perl.com with an accurate description of your problem. |
1468 | |
1ec51d55 |
1469 | Please include the output of the ./myconfig shell script |
aa689395 |
1470 | that comes with the distribution. Alternatively, you can use the |
1ec51d55 |
1471 | perlbug program that comes with the perl distribution, |
aa689395 |
1472 | but you need to have perl compiled and installed before you can use it. |
1473 | |
1ec51d55 |
1474 | You might also find helpful information in the Porting |
aa689395 |
1475 | directory of the perl distribution. |
1476 | |
8e07c86e |
1477 | =head1 DOCUMENTATION |
1478 | |
1479 | Read the manual entries before running perl. The main documentation is |
1480 | in the pod/ subdirectory and should have been installed during the |
1481 | build process. Type B<man perl> to get started. Alternatively, you |
1ec51d55 |
1482 | can type B<perldoc perl> to use the supplied perldoc script. This |
8e07c86e |
1483 | is sometimes useful for finding things in the library modules. |
1484 | |
1ec51d55 |
1485 | Under UNIX, you can produce a documentation book in postscript form, |
1486 | along with its table of contents, by going to the pod/ subdirectory |
34a2a22e |
1487 | and running (either): |
1488 | |
1489 | ./roffitall -groff # If you have GNU groff installed |
aa689395 |
1490 | ./roffitall -psroff # If you have psroff |
34a2a22e |
1491 | |
1492 | This will leave you with two postscript files ready to be printed. |
aa689395 |
1493 | (You may need to fix the roffitall command to use your local troff |
1494 | set-up.) |
34a2a22e |
1495 | |
1496 | Note that you must have performed the installation already before |
1497 | running the above, since the script collects the installed files to |
1498 | generate the documentation. |
1499 | |
8e07c86e |
1500 | =head1 AUTHOR |
1501 | |
fb73857a |
1502 | Original author: Andy Dougherty doughera@lafcol.lafayette.edu , |
1503 | borrowing very heavily from the original README by Larry Wall, |
1504 | with lots of helpful feedback and additions from the |
1505 | perl5-porters@perl.org folks. |
1506 | |
1507 | If you have problems or questions, please see L<"Reporting Problems"> |
1508 | above. |
8e07c86e |
1509 | |
a5f75d66 |
1510 | =head1 LAST MODIFIED |
24b3df7f |
1511 | |
693762b4 |
1512 | $Id: INSTALL,v 1.31 1998/03/03 18:08:52 doughera Released $ |