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