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