Commit | Line | Data |
---|---|---|
f1300be0 | 1 | If you read this file _as_is_, just ignore the funny characters you see. |
b0a63d58 | 2 | It is written in the POD format (see F<pod/perlpod.pod>) which is specially |
f1300be0 YST |
3 | designed to be readable as is. |
4 | ||
8e07c86e AD |
5 | =head1 NAME |
6 | ||
cb8c159f | 7 | INSTALL - Build and Installation guide for perl 5. |
8e07c86e AD |
8 | |
9 | =head1 SYNOPSIS | |
10 | ||
7df75831 | 11 | First, make sure you have an up-to-date version of Perl. If you |
ce80d64e | 12 | didn't get your Perl source from CPAN, check the latest version at |
f6521f7c | 13 | L<https://www.cpan.org/src/>. Perl uses a version scheme where even-numbered |
08854360 | 14 | subreleases (like 5.8.x and 5.10.x) are stable maintenance releases and |
ce80d64e AD |
15 | odd-numbered subreleases (like 5.7.x and 5.9.x) are unstable |
16 | development releases. Development releases should not be used in | |
17 | production environments. Fixes and new features are first carefully | |
18 | tested in development releases and only if they prove themselves to be | |
19 | worthy will they be migrated to the maintenance releases. | |
3ce0d271 | 20 | |
7df75831 | 21 | The basic steps to build and install perl 5 on a Unix system with all |
dd3196cd | 22 | the defaults are to run, from a freshly unpacked source tree: |
8e07c86e | 23 | |
491517e0 | 24 | sh Configure -de |
8e07c86e AD |
25 | make |
26 | make test | |
27 | make install | |
36477c24 | 28 | |
8e07c86e AD |
29 | Each of these is explained in further detail below. |
30 | ||
b0a63d58 KW |
31 | The above commands will install Perl to F</usr/local> (or some other |
32 | platform-specific directory -- see the appropriate file in F<hints/>.) | |
7df75831 | 33 | If that's not okay with you, you can run Configure interactively, by |
ff52061e | 34 | just typing "sh Configure" (without the -de args). You can also specify |
b0a63d58 | 35 | any prefix location by adding C<"-Dprefix='/some/dir'"> to Configure's args. |
ff52061e RGS |
36 | To explicitly name the perl binary, use the command |
37 | "make install PERLNAME=myperl". | |
491517e0 | 38 | |
668cbedd | 39 | Building perl from source requires an ANSI compliant C compiler. |
a66ca998 NC |
40 | C89 with a minimal subset of C99 features is required. Some other |
41 | features available in C99 will be probed for and used when found. | |
51eec7ec | 42 | |
ff52061e | 43 | These options, and many more, are explained in further detail below. |
7f678428 | 44 | |
e0ddbfb2 | 45 | If you're building perl from a git repository, you should also consult |
b0a63d58 | 46 | the documentation in F<pod/perlgit.pod> for information on that special |
e0ddbfb2 RS |
47 | circumstance. |
48 | ||
8d74ce1c | 49 | If you have problems, corrections, or questions, please see |
ff52061e | 50 | L<"Reporting Problems"> below. |
8d74ce1c | 51 | |
7beaa944 | 52 | For information on what's new in this release, see the |
b0a63d58 | 53 | F<pod/perldelta.pod> file. For more information about how to find more |
9519d2ec | 54 | specific detail about changes, see the Changes file. |
c3edaffb | 55 | |
1ec51d55 | 56 | =head1 DESCRIPTION |
edb1cbcb | 57 | |
c3edaffb | 58 | This document is written in pod format as an easy way to indicate its |
b0a63d58 | 59 | structure. The pod format is described in F<pod/perlpod.pod>, but you can |
1ec51d55 CS |
60 | read it as is with any pager or editor. Headings and items are marked |
61 | by lines beginning with '='. The other mark-up used is | |
62 | ||
63 | B<text> embolden text, used for switches, programs or commands | |
64 | C<code> literal code | |
65 | L<name> A link (cross reference) to name | |
ce80d64e | 66 | F<file> A filename |
1ec51d55 | 67 | |
c42e3e15 | 68 | Although most of the defaults are probably fine for most users, |
ce80d64e | 69 | you should probably at least skim through this document before |
1ec51d55 | 70 | proceeding. |
c3edaffb | 71 | |
ce80d64e AD |
72 | In addition to this file, check if there is a README file specific to |
73 | your operating system, since it may provide additional or different | |
74 | instructions for building Perl. If there is a hint file for your | |
b0a63d58 | 75 | system (in the F<hints/> directory) you might also want to read it |
dd3196cd | 76 | for even more information. |
c42e3e15 | 77 | |
ce80d64e | 78 | For additional information about porting Perl, see the section on |
b0a63d58 | 79 | L<"Porting information"> below, and look at the files in the F<Porting/> |
ce80d64e | 80 | directory. |
d56c5707 | 81 | |
ce80d64e | 82 | =head1 PRELIMINARIES |
c42e3e15 | 83 | |
ce80d64e | 84 | =head2 Changes and Incompatibilities |
c42e3e15 | 85 | |
b0a63d58 | 86 | Please see F<pod/perldelta.pod> for a description of the changes and |
ce80d64e AD |
87 | potential incompatibilities introduced with this release. A few of |
88 | the most important issues are listed below, but you should refer | |
b0a63d58 | 89 | to F<pod/perldelta.pod> for more detailed information. |
c42e3e15 | 90 | |
c44af6e3 NC |
91 | =head3 Compatibility with earlier versions |
92 | ||
ab97e755 MB |
93 | B<WARNING:> This version is not binary compatible with earlier versions |
94 | of Perl. If you have built extensions (i.e. modules that include C code) | |
64fa5b0b DM |
95 | using an earlier version of Perl, you will need to rebuild and reinstall |
96 | those extensions. | |
1b1c1ae2 GS |
97 | |
98 | Pure perl modules without XS or C code should continue to work fine | |
dd3196cd | 99 | without reinstallation. See the discussion below on |
7df75831 | 100 | L<"Coexistence with earlier versions of perl 5"> for more details. |
693762b4 AD |
101 | |
102 | The standard extensions supplied with Perl will be handled automatically. | |
103 | ||
ce80d64e AD |
104 | On a related issue, old modules may possibly be affected by the changes |
105 | in the Perl language in the current release. Please see | |
b0a63d58 | 106 | F<pod/perldelta.pod> for a description of what's changed. See your |
ce80d64e | 107 | installed copy of the perllocal.pod file for a (possibly incomplete) |
c75cfcf0 FC |
108 | list of locally installed modules. Also see the L<CPAN> module's |
109 | C<autobundle> function for one way to make a "bundle" of your currently | |
110 | installed modules. | |
16dc217a | 111 | |
c44af6e3 NC |
112 | =head3 C99 |
113 | ||
114 | With 5.36 we changed our C compiler baseline requirement from "ANSI C89" to | |
115 | "C89 plus some specific C99 features". We have been using C99 features | |
116 | optionally for some time - we now additionally B<rely> on a few in the core C | |
117 | code and installed headers, which we know work on all supported compilers on | |
118 | all platforms we target. Because earlier versions of Perl still compile with | |
119 | strictly ANSI C89 compilers and there are still a few installations in the | |
120 | wild which use these very old compilers, XS code that targets earlier versions | |
121 | of Perl must not B<rely> on C99 features - that includes XS code in this | |
122 | distribution that is dual life on CPAN. To test that XS code can build on | |
123 | such compilers, some authors configure their perl builds with compiler flags | |
124 | to warn or raise errors on C99 specific features, most often for mixed | |
125 | declarations and code. This obviously will not work if you attempt it for | |
126 | this release - it will not build. However, XS authors should be aware that | |
127 | this means | |
128 | ||
129 | =over 4 | |
130 | ||
131 | =item * | |
132 | ||
133 | If you change the C compiler flags in your F<Makefile.PL> or similar to add | |
134 | such warnings or errors, you must now only do it for 5.35.4 or earlier. | |
135 | ||
136 | =item * | |
137 | ||
138 | Do not rely on now being able to use C99 features in your XS code, even for | |
139 | platforms with C99 compilers - some installations of earlier versions of perl | |
140 | are deliberately configured to enforce C89 standards so that locally authored | |
141 | extension code conforms to them. If you choose to require C99 for your code, | |
142 | that's fine, but do so knowing that if you distribute it, some installations | |
143 | of perl are configured to fault C99. | |
144 | ||
145 | =back | |
146 | ||
aa689395 | 147 | =head1 Run Configure |
8e07c86e AD |
148 | |
149 | Configure will figure out various things about your system. Some | |
150 | things Configure will figure out for itself, other things it will ask | |
d6baa268 JH |
151 | you about. To accept the default, just press RETURN. The default is |
152 | almost always okay. It is normal for some things to be "NOT found", | |
153 | since Configure often searches for many different ways of performing | |
154 | the same function. | |
155 | ||
ce80d64e | 156 | At any Configure prompt, you can type &-d and Configure will use the |
d6baa268 | 157 | defaults from then on. |
8e07c86e AD |
158 | |
159 | After it runs, Configure will perform variable substitution on all the | |
1ec51d55 | 160 | *.SH files and offer to run make depend. |
8e07c86e | 161 | |
dd3196cd RGS |
162 | The results of a Configure run are stored in the config.sh and Policy.sh |
163 | files. | |
164 | ||
ce80d64e | 165 | =head2 Common Configure options |
844fc9f4 | 166 | |
ce80d64e | 167 | Configure supports a number of useful options. Run |
844fc9f4 | 168 | |
ce80d64e | 169 | Configure -h |
d6baa268 | 170 | |
b52f3fcb JK |
171 | to get a listing. |
172 | ||
173 | Many Configure switches are expressed as C<key=value> pairs, for example: | |
174 | ||
175 | -Dcc=clang | |
176 | ||
177 | Sometimes the value to be supplied for a switch is a string which contains | |
178 | spaces. In that case, the value needs to be quoted so as to delimit that | |
179 | "shell word" from any following switch. Example: | |
180 | ||
181 | sh ./Configure -des \ | |
182 | -Doptimize="-O2 -pipe -fstack-protector -fno-strict-aliasing" \ | |
183 | -Dusedevel | |
184 | ||
185 | Once Configure has run, you will be able to access configuration data via | |
186 | entries in the file F<config.sh>. | |
187 | ||
188 | config_arg0='./Configure' | |
189 | config_args='-des -Doptimize=-O2 -pipe -fstack-protector -fno-strict-aliasing -Dusedevel' | |
190 | config_argc=3 | |
191 | config_arg1='-des' | |
192 | config_arg2='-Doptimize=-O2 -pipe -fstack-protector -fno-strict-aliasing' | |
193 | config_arg3='-Dusedevel' | |
194 | ||
195 | See the F<Porting/Glossary> file for a complete list of | |
fb73857a | 196 | Configure variables you can set and their definitions. |
197 | ||
d6baa268 JH |
198 | =over 4 |
199 | ||
08854360 | 200 | =item C compiler |
d6baa268 | 201 | |
08854360 RGS |
202 | To compile with gcc, if it's not the default compiler on your |
203 | system, you should run | |
8e07c86e AD |
204 | |
205 | sh Configure -Dcc=gcc | |
206 | ||
08854360 | 207 | This is the preferred way to specify gcc (or any another alternative |
8e07c86e AD |
208 | compiler) so that the hints files can set appropriate defaults. |
209 | ||
d6baa268 | 210 | =item Installation prefix |
4633a7c4 | 211 | |
8e07c86e | 212 | By default, for most systems, perl will be installed in |
b0a63d58 | 213 | F</usr/local/>{F<bin>, F<lib>, F<man>}. (See L<"Installation Directories"> |
7df75831 | 214 | and L<"Coexistence with earlier versions of perl 5"> below for |
8d74ce1c AD |
215 | further details.) |
216 | ||
217 | You can specify a different 'prefix' for the default installation | |
ce80d64e | 218 | directory when Configure prompts you, or by using the Configure command |
b0a63d58 | 219 | line option C<-Dprefix='/some/directory'>, e.g. |
8e07c86e | 220 | |
25f94b33 | 221 | sh Configure -Dprefix=/opt/perl |
4633a7c4 | 222 | |
d6baa268 JH |
223 | If your prefix contains the string "perl", then the suggested |
224 | directory structure is simplified. For example, if you use | |
b0a63d58 KW |
225 | C<prefix=/opt/perl>, then Configure will suggest F</opt/perl/lib> instead of |
226 | F</opt/perl/lib/perl5/>. Again, see L<"Installation Directories"> below | |
227 | for more details. Do not include a trailing slash, (i.e. F</opt/perl/>) | |
bc70e9ec | 228 | or you may experience odd test failures. |
8e07c86e | 229 | |
8d74ce1c AD |
230 | NOTE: You must not specify an installation directory that is the same |
231 | as or below your perl source directory. If you do, installperl will | |
232 | attempt infinite recursion. | |
84902520 | 233 | |
b0a63d58 | 234 | =item F</usr/bin/perl> |
d6baa268 JH |
235 | |
236 | It may seem obvious, but Perl is useful only when users can easily | |
b0a63d58 KW |
237 | find it. It's often a good idea to have both F</usr/bin/perl> and |
238 | F</usr/local/bin/perl> be symlinks to the actual binary. Be especially | |
d6baa268 | 239 | careful, however, not to overwrite a version of perl supplied by your |
b66c6cec AD |
240 | vendor unless you are sure you know what you are doing. If you insist |
241 | on replacing your vendor's perl, useful information on how it was | |
242 | configured may be found with | |
243 | ||
244 | perl -V:config_args | |
245 | ||
246 | (Check the output carefully, however, since this doesn't preserve | |
ce80d64e AD |
247 | spaces in arguments to Configure. For that, you have to look carefully |
248 | at config_arg1, config_arg2, etc.) | |
d6baa268 | 249 | |
b0a63d58 | 250 | By default, Configure will not try to link F</usr/bin/perl> to the current |
ce80d64e | 251 | version of perl. You can turn on that behavior by running |
d6baa268 | 252 | |
7d56c962 | 253 | Configure -Dinstallusrbinperl |
d6baa268 | 254 | |
7d56c962 | 255 | or by answering 'yes' to the appropriate Configure prompt. |
d6baa268 | 256 | |
ce80d64e AD |
257 | In any case, system administrators are strongly encouraged to put |
258 | (symlinks to) perl and its accompanying utilities, such as perldoc, | |
4682965a MB |
259 | into a directory typically found along a user's PATH, or in another |
260 | obvious and convenient place. | |
261 | ||
71c4561b | 262 | =item Building a development release |
04d420f9 | 263 | |
ce80d64e AD |
264 | For development releases (odd subreleases, like 5.9.x) if you want to |
265 | use Configure -d, you will also need to supply -Dusedevel to Configure, | |
266 | because the default answer to the question "do you really want to | |
267 | Configure a development version?" is "no". The -Dusedevel skips that | |
268 | sanity check. | |
d6baa268 JH |
269 | |
270 | =back | |
8e07c86e | 271 | |
203c3eec AD |
272 | If you are willing to accept all the defaults, and you want terse |
273 | output, you can run | |
274 | ||
275 | sh Configure -des | |
276 | ||
dd3196cd | 277 | =head2 Altering Configure variables for C compiler switches etc. |
46bb10fb | 278 | |
ce80d64e AD |
279 | For most users, most of the Configure defaults are fine, or can easily |
280 | be set on the Configure command line. However, if Configure doesn't | |
281 | have an option to do what you want, you can change Configure variables | |
282 | after the platform hints have been run by using Configure's -A switch. | |
283 | For example, here's how to add a couple of extra flags to C compiler | |
284 | invocations: | |
46bb10fb | 285 | |
08854360 | 286 | sh Configure -Accflags="-DPERL_EXTERNAL_GLOB -DNO_HASH_SEED" |
46bb10fb | 287 | |
5247441a | 288 | To clarify, those ccflags values are not Configure options; if passed to |
dd3196cd RGS |
289 | Configure directly, they won't do anything useful (they will define a |
290 | variable in config.sh, but without taking any action based upon it). | |
291 | But when passed to the compiler, those flags will activate #ifdefd code. | |
5247441a | 292 | |
ce80d64e | 293 | For more help on Configure switches, run |
46bb10fb | 294 | |
ce80d64e | 295 | sh Configure -h |
46bb10fb | 296 | |
ce80d64e | 297 | =head2 Major Configure-time Build Options |
46bb10fb | 298 | |
ce80d64e AD |
299 | There are several different ways to Configure and build perl for your |
300 | system. For most users, the defaults are sensible and will work. | |
301 | Some users, however, may wish to further customize perl. Here are | |
302 | some of the main things you can change. | |
46bb10fb | 303 | |
ce80d64e | 304 | =head3 Threads |
cc65bb49 | 305 | |
ce80d64e AD |
306 | On some platforms, perl can be compiled with support for threads. To |
307 | enable this, run | |
4633a7c4 | 308 | |
ce80d64e | 309 | sh Configure -Dusethreads |
4633a7c4 | 310 | |
ce80d64e | 311 | The default is to compile without thread support. |
cc65bb49 | 312 | |
ab97e755 MB |
313 | Perl used to have two different internal threads implementations. The |
314 | current model (available internally since 5.6, and as a user-level module | |
315 | since 5.8) is called interpreter-based implementation (ithreads), with | |
316 | one interpreter per thread, and explicit sharing of data. The (deprecated) | |
317 | 5.005 version (5005threads) was removed for release 5.10. | |
d6baa268 | 318 | |
ce80d64e | 319 | The 'threads' module is for use with the ithreads implementation. The |
ab97e755 MB |
320 | 'Thread' module emulates the old 5005threads interface on top of the |
321 | current ithreads model. | |
d6baa268 | 322 | |
ce80d64e AD |
323 | When using threads, perl uses a dynamically-sized buffer for some of |
324 | the thread-safe library calls, such as those in the getpw*() family. | |
325 | This buffer starts small, but it will keep growing until the result | |
326 | fits. To get a fixed upper limit, you should compile Perl with | |
327 | PERL_REENTRANT_MAXSIZE defined to be the number of bytes you want. One | |
328 | way to do this is to run Configure with | |
08854360 | 329 | C<-Accflags=-DPERL_REENTRANT_MAXSIZE=65536>. |
d6baa268 | 330 | |
08854360 | 331 | =head3 Large file support |
b367e8b0 | 332 | |
ce80d64e AD |
333 | Since Perl 5.6.0, Perl has supported large files (files larger than |
334 | 2 gigabytes), and in many common platforms like Linux or Solaris this | |
335 | support is on by default. | |
d6baa268 | 336 | |
ce80d64e | 337 | This is both good and bad. It is good in that you can use large files, |
ab97e755 MB |
338 | seek(), stat(), and -s them. It is bad in that if you are interfacing |
339 | Perl using some extension, the components you are connecting to must also | |
ce80d64e AD |
340 | be large file aware: if Perl thinks files can be large but the other |
341 | parts of the software puzzle do not understand the concept, bad things | |
08854360 | 342 | will happen. |
d6baa268 | 343 | |
ce80d64e AD |
344 | There's also one known limitation with the current large files |
345 | implementation: unless you also have 64-bit integers (see the next | |
346 | section), you cannot use the printf/sprintf non-decimal integer formats | |
347 | like C<%x> to print filesizes. You can use C<%d>, though. | |
d6baa268 | 348 | |
71c4561b RGS |
349 | If you want to compile perl without large file support, use |
350 | ||
351 | sh Configure -Uuselargefiles | |
352 | ||
08854360 | 353 | =head3 64 bit support |
d6baa268 | 354 | |
08854360 RGS |
355 | If your platform does not run natively at 64 bits, but can simulate |
356 | them with compiler flags and/or C<long long> or C<int64_t>, | |
ce80d64e | 357 | you can build a perl that uses 64 bits. |
d6baa268 | 358 | |
ce80d64e AD |
359 | There are actually two modes of 64-bitness: the first one is achieved |
360 | using Configure -Duse64bitint and the second one using Configure | |
361 | -Duse64bitall. The difference is that the first one is minimal and | |
362 | the second one maximal. The first works in more places than the second. | |
d6baa268 | 363 | |
ce80d64e AD |
364 | The C<use64bitint> option does only as much as is required to get |
365 | 64-bit integers into Perl (this may mean, for example, using "long | |
366 | longs") while your memory may still be limited to 2 gigabytes (because | |
367 | your pointers could still be 32-bit). Note that the name C<64bitint> | |
368 | does not imply that your C compiler will be using 64-bit C<int>s (it | |
369 | might, but it doesn't have to). The C<use64bitint> simply means that | |
370 | you will be able to have 64 bit-wide scalar values. | |
d6baa268 | 371 | |
ce80d64e AD |
372 | The C<use64bitall> option goes all the way by attempting to switch |
373 | integers (if it can), longs (and pointers) to being 64-bit. This may | |
374 | create an even more binary incompatible Perl than -Duse64bitint: the | |
375 | resulting executable may not run at all in a 32-bit box, or you may | |
376 | have to reboot/reconfigure/rebuild your operating system to be 64-bit | |
377 | aware. | |
d6baa268 | 378 | |
08854360 | 379 | Natively 64-bit systems need neither -Duse64bitint nor -Duse64bitall. |
0e78eb44 MB |
380 | On these systems, it might be the default compilation mode, and there |
381 | is currently no guarantee that passing no use64bitall option to the | |
382 | Configure process will build a 32bit perl. Implementing -Duse32bit* | |
1ed7425e | 383 | options is planned for a future release of perl. |
d6baa268 | 384 | |
ce80d64e | 385 | =head3 Long doubles |
d6baa268 | 386 | |
ce80d64e AD |
387 | In some systems you may be able to use long doubles to enhance the |
388 | range and precision of your double precision floating point numbers | |
389 | (that is, Perl's numbers). Use Configure -Duselongdouble to enable | |
390 | this support (if it is available). | |
d6baa268 | 391 | |
aacf4ea2 JH |
392 | Note that the exact format and range of long doubles varies: |
393 | the most common is the x86 80-bit (64 bits of mantissa) format, | |
394 | but there are others, with different mantissa and exponent ranges. | |
395 | ||
ce80d64e | 396 | =head3 "more bits" |
b367e8b0 | 397 | |
ce80d64e AD |
398 | You can "Configure -Dusemorebits" to turn on both the 64-bit support |
399 | and the long double support. | |
b367e8b0 | 400 | |
257c99f5 JH |
401 | =head3 quadmath |
402 | ||
b7ce25dd | 403 | One option for more precision is that gcc 4.6 and later have a library |
257c99f5 JH |
404 | called quadmath, which implements the IEEE 754 quadruple precision |
405 | (128-bit, 113 bits of mantissa) floating point numbers. The library | |
406 | works at least on x86 and ia64 platforms. It may be part of your gcc | |
407 | installation, or you may need to install it separately. | |
408 | ||
79f6e7a5 JH |
409 | With "Configure -Dusequadmath" you can try enabling its use, but note |
410 | the compiler dependency, you may need to also add "-Dcc=...". | |
84e6cb05 | 411 | At C level the type is called C<__float128> (note, not "long double"), |
b7ce25dd | 412 | but Perl source knows it as NV. (This is not "long doubles".) |
257c99f5 | 413 | |
ce80d64e | 414 | =head3 Algorithmic Complexity Attacks on Hashes |
504f80c1 | 415 | |
e6b54db6 YO |
416 | Perl 5.18 reworked the measures used to secure its hash function |
417 | from algorithmic complexity attacks. By default it will build with | |
418 | all of these measures enabled along with support for controlling and | |
419 | disabling them via environment variables. | |
420 | ||
421 | You can override various aspects of this feature by defining various | |
422 | symbols during configure. An example might be: | |
423 | ||
f0c21bde | 424 | sh Configure -Accflags=-DPERL_HASH_FUNC_SIPHASH |
e6b54db6 YO |
425 | |
426 | B<Unless stated otherwise these options are considered experimental or | |
427 | insecure and are not recommended for production use.> | |
428 | ||
99111b89 YO |
429 | Since Perl 5.18 we have included support for multiple hash functions, |
430 | although from time to time we change which functions we support, | |
8bc8b6db | 431 | and which function is default (currently SBOX+SIPHASH13 on 64 bit builds |
99111b89 YO |
432 | and SBOX+ZAPHOD32 for 32 bit builds). You can choose a different |
433 | algorithm by defining one of the following symbols during configure. | |
055663bc | 434 | Note that there are security implications regarding which hash function you choose |
99111b89 YO |
435 | to use. The functions are listed roughly by how secure they are believed |
436 | to be, with the one believed to be most secure at release time being PERL_HASH_FUNC_SIPHASH. | |
e6b54db6 YO |
437 | |
438 | PERL_HASH_FUNC_SIPHASH | |
99111b89 YO |
439 | PERL_HASH_FUNC_SIPHASH13 |
440 | PERL_HASH_FUNC_ZAPHOD32 | |
8bc8b6db | 441 | |
99111b89 YO |
442 | In addition, these, (or custom hash functions), may be "fronted" by the |
443 | SBOX32 hash function for keys under a chosen size. This hash function is | |
444 | special in that it has proven theoretical security properties, and is very | |
445 | fast to hash, but which by nature is restricted to a maximum key length, | |
446 | and which has rather expensive setup costs (relatively speaking), both in | |
447 | terms of performance and more importantly in terms of memory. SBOX32 | |
448 | requires 1k of storage per character it can hash, and it must populate that | |
449 | storage with 256 32-bit random values as well. In practice the RNG we use | |
055663bc | 450 | for seeding the SBOX32 storage is very efficient, and populating the table |
ab473f03 | 451 | required for hashing even fairly long keys is negligible as we only do it |
055663bc KW |
452 | during startup. By default we build with SBOX32 enabled, but you can change |
453 | that by setting | |
99111b89 YO |
454 | |
455 | PERL_HASH_USE_SBOX32_ALSO | |
456 | ||
457 | to zero in configure. By default Perl will use SBOX32 to hash strings 24 bytes | |
458 | or shorter, you can change this length by setting | |
459 | ||
460 | SBOX32_MAX_LEN | |
461 | ||
462 | to the desired length, with the maximum length being 256. | |
463 | ||
464 | As of Perl 5.18 the order returned by keys(), values(), and each() is | |
465 | non-deterministic and distinct per hash, and the insert order for | |
466 | colliding keys is randomized as well, and perl allows for controlling this | |
467 | by the PERL_PERTURB_KEYS environment setting. You can disable this behavior | |
468 | entirely with the define | |
e6b54db6 YO |
469 | |
470 | PERL_PERTURB_KEYS_DISABLED | |
471 | ||
99111b89 YO |
472 | You can disable the environment variable checks and compile time specify |
473 | the type of key traversal randomization to be used by defining one of these: | |
e6b54db6 YO |
474 | |
475 | PERL_PERTURB_KEYS_RANDOM | |
476 | PERL_PERTURB_KEYS_DETERMINISTIC | |
477 | ||
99111b89 YO |
478 | Since Perl 5.18 the seed used for the hash function is randomly selected |
479 | at process start, which can be overridden by specifying a seed by setting | |
25722165 YO |
480 | the PERL_HASH_SEED environment variable. Be aware that |
481 | PERL_PERTURB_KEYS_DETERMINISTIC and the equivalent environment variable | |
482 | setting will produce the same results if and only if the code does not | |
483 | put non-deterministic data into a hash, and the code is executed in exactly | |
484 | the same context in terms of the environment. If the code populates a hash | |
485 | with random data, or builds a hash using the address of its items, or | |
486 | if the code is run in a different environment context with a different | |
487 | number or selection of environment variables then the result may differ. | |
488 | DETERMINISTIC in this context means "if everything else is kept the same | |
489 | the same results should be observed". | |
e6b54db6 | 490 | |
99111b89 YO |
491 | You can change this behavior so that your perl is built with a hard coded |
492 | seed with the define | |
e6b54db6 YO |
493 | |
494 | NO_HASH_SEED | |
495 | ||
99111b89 YO |
496 | Note that if you do this you should modify the code in hv_func.h to specify |
497 | your own key. In the future this define may be renamed and replaced with one | |
498 | that requires you to specify the key to use. | |
504f80c1 | 499 | |
99111b89 | 500 | B<NOTE WELL: Perl has never guaranteed any ordering of the hash keys>, and the |
86358043 NC |
501 | ordering has already changed several times during the lifetime of Perl |
502 | 5. Also, the ordering of hash keys has always been, and continues to | |
99111b89 YO |
503 | be, affected by the insertion order regardless of whether you build with |
504 | or without the randomization features. Note that because of this | |
505 | and especially with randomization that the key order of a hash is *undefined* | |
506 | and that things like Data::Dumper, for example, may produce different output | |
507 | between different runs of Perl, since Data::Dumper serializes the key in the | |
508 | native order for the hash. The use of the Data::Dumper C<Sortkeys> option is | |
509 | recommended if you are comparing dumps between different invocations of perl. | |
504f80c1 | 510 | |
ab97e755 MB |
511 | See L<perlrun/PERL_HASH_SEED> and L<perlrun/PERL_PERTURB_KEYS> for |
512 | details on the environment variables, and L<perlsec/Algorithmic | |
513 | Complexity Attacks> for further security details. | |
e6b54db6 | 514 | |
95309d6b TC |
515 | The C<PERL_HASH_SEED> and PERL_PERTURB_KEYS> environment variables can |
516 | be disabled by building configuring perl with | |
517 | C<-Accflags=-DNO_PERL_HASH_ENV>. | |
518 | ||
519 | The C<PERL_HASH_SEED_DEBUG> environment variable can be disabled by | |
520 | configuring perl with C<-Accflags=-DNO_PERL_HASH_SEED_DEBUG>. | |
521 | ||
ce80d64e | 522 | =head3 SOCKS |
1b9c9cf5 DH |
523 | |
524 | Perl can be configured to be 'socksified', that is, to use the SOCKS | |
525 | TCP/IP proxy protocol library. SOCKS is used to give applications | |
526 | access to transport layer network proxies. Perl supports only SOCKS | |
71c4561b RGS |
527 | Version 5. The corresponding Configure option is -Dusesocks. |
528 | You can find more about SOCKS from wikipedia at | |
f6521f7c | 529 | L<https://en.wikipedia.org/wiki/SOCKS>. |
1b9c9cf5 | 530 | |
ce80d64e | 531 | =head3 Dynamic Loading |
d6baa268 | 532 | |
71c4561b RGS |
533 | By default, Configure will compile perl to use dynamic loading. |
534 | If you want to force perl to be compiled completely | |
d6baa268 JH |
535 | statically, you can either choose this when Configure prompts you or |
536 | you can use the Configure command line option -Uusedl. | |
7df75831 RGS |
537 | With this option, you won't be able to use any new extension |
538 | (XS) module without recompiling perl itself. | |
d6baa268 | 539 | |
ce80d64e | 540 | =head3 Building a shared Perl library |
c3edaffb | 541 | |
542 | Currently, for most systems, the main perl executable is built by | |
543 | linking the "perl library" libperl.a with perlmain.o, your static | |
8ba4bff0 | 544 | extensions, and various extra libraries, such as -lm. |
c3edaffb | 545 | |
08854360 | 546 | On systems that support dynamic loading, it may be possible to |
9d67150a | 547 | replace libperl.a with a shared libperl.so. If you anticipate building |
c3edaffb | 548 | several different perl binaries (e.g. by embedding libperl into |
549 | different programs, or by using the optional compiler extension), then | |
9d67150a | 550 | you might wish to build a shared libperl.so so that all your binaries |
c3edaffb | 551 | can share the same library. |
552 | ||
553 | The disadvantages are that there may be a significant performance | |
9d67150a | 554 | penalty associated with the shared libperl.so, and that the overall |
aa689395 | 555 | mechanism is still rather fragile with respect to different versions |
c3edaffb | 556 | and upgrades. |
557 | ||
558 | In terms of performance, on my test system (Solaris 2.5_x86) the perl | |
9d67150a | 559 | test suite took roughly 15% longer to run with the shared libperl.so. |
c3edaffb | 560 | Your system and typical applications may well give quite different |
561 | results. | |
562 | ||
563 | The default name for the shared library is typically something like | |
08854360 | 564 | libperl.so.5.8.8 (for Perl 5.8.8), or libperl.so.588, or simply |
9d67150a | 565 | libperl.so. Configure tries to guess a sensible naming convention |
c3edaffb | 566 | based on your C library name. Since the library gets installed in a |
567 | version-specific architecture-dependent directory, the exact name | |
568 | isn't very important anyway, as long as your linker is happy. | |
569 | ||
c3edaffb | 570 | You can elect to build a shared libperl by |
571 | ||
ce80d64e AD |
572 | sh Configure -Duseshrplib |
573 | ||
574 | To build a shared libperl, the environment variable controlling shared | |
575 | library search (LD_LIBRARY_PATH in most systems, DYLD_LIBRARY_PATH for | |
f05550c0 | 576 | Darwin, LD_LIBRARY_PATH/SHLIB_PATH |
0fd807f7 | 577 | for HP-UX, LIBPATH for AIX and z/OS, PATH for Cygwin) must be set up to include |
ce80d64e AD |
578 | the Perl build directory because that's where the shared libperl will |
579 | be created. Configure arranges makefile to have the correct shared | |
580 | library search settings. You can find the name of the environment | |
581 | variable Perl thinks works in your your system by | |
582 | ||
583 | grep ldlibpthname config.sh | |
584 | ||
585 | However, there are some special cases where manually setting the | |
586 | shared library path might be required. For example, if you want to run | |
587 | something like the following with the newly-built but not-yet-installed | |
588 | ./perl: | |
589 | ||
a070ca95 | 590 | ./perl -I. -MTestInit t/misc/failing_test.t |
08854360 | 591 | |
ce80d64e | 592 | or |
08854360 | 593 | |
ce80d64e AD |
594 | ./perl -Ilib ~/my_mission_critical_test |
595 | ||
596 | then you need to set up the shared library path explicitly. | |
597 | You can do this with | |
598 | ||
599 | LD_LIBRARY_PATH=`pwd`:$LD_LIBRARY_PATH; export LD_LIBRARY_PATH | |
600 | ||
601 | for Bourne-style shells, or | |
602 | ||
603 | setenv LD_LIBRARY_PATH `pwd` | |
604 | ||
605 | for Csh-style shells. (This procedure may also be needed if for some | |
606 | unexpected reason Configure fails to set up makefile correctly.) (And | |
607 | again, it may be something other than LD_LIBRARY_PATH for you, see above.) | |
608 | ||
609 | You can often recognize failures to build/use a shared libperl from error | |
610 | messages complaining about a missing libperl.so (or libperl.sl in HP-UX), | |
611 | for example: | |
08854360 RGS |
612 | |
613 | 18126:./miniperl: /sbin/loader: Fatal Error: cannot map libperl.so | |
ce80d64e AD |
614 | |
615 | There is also an potential problem with the shared perl library if you | |
616 | want to have more than one "flavor" of the same version of perl (e.g. | |
617 | with and without -DDEBUGGING). For example, suppose you build and | |
08854360 RGS |
618 | install a standard Perl 5.10.0 with a shared library. Then, suppose you |
619 | try to build Perl 5.10.0 with -DDEBUGGING enabled, but everything else | |
ce80d64e AD |
620 | the same, including all the installation directories. How can you |
621 | ensure that your newly built perl will link with your newly built | |
622 | libperl.so.8 rather with the installed libperl.so.8? The answer is | |
623 | that you might not be able to. The installation directory is encoded | |
624 | in the perl binary with the LD_RUN_PATH environment variable (or | |
625 | equivalent ld command-line option). On Solaris, you can override that | |
626 | with LD_LIBRARY_PATH; on Linux, you can only override at runtime via | |
627 | LD_PRELOAD, specifying the exact filename you wish to be used; and on | |
628 | Digital Unix, you can override LD_LIBRARY_PATH by setting the | |
629 | _RLD_ROOT environment variable to point to the perl build directory. | |
630 | ||
631 | In other words, it is generally not a good idea to try to build a perl | |
632 | with a shared library if $archlib/CORE/$libperl already exists from a | |
633 | previous build. | |
634 | ||
635 | A good workaround is to specify a different directory for the | |
636 | architecture-dependent library for your -DDEBUGGING version of perl. | |
637 | You can do this by changing all the *archlib* variables in config.sh to | |
638 | point to your new architecture-dependent library. | |
639 | ||
575e1338 NC |
640 | =head3 Environment access |
641 | ||
ab97e755 MB |
642 | Perl often needs to write to the program's environment, such as when |
643 | C<%ENV> is assigned to. Many implementations of the C library function | |
644 | C<putenv()> leak memory, so where possible perl will manipulate the | |
645 | environment directly to avoid these leaks. The default is now to perform | |
646 | direct manipulation whenever perl is running as a stand alone interpreter, | |
647 | and to call the safe but potentially leaky C<putenv()> function when the | |
648 | perl interpreter is embedded in another application. You can force perl | |
649 | to always use C<putenv()> by compiling with | |
650 | C<-Accflags="-DPERL_USE_SAFE_PUTENV">, see section L</"Altering Configure | |
651 | variables for C compiler switches etc.">. You can force an embedded perl | |
652 | to use direct manipulation by setting C<PL_use_safe_putenv = 0;> after | |
653 | the C<perl_construct()> call. | |
575e1338 | 654 | |
0a790ceb JK |
655 | =head3 External glob |
656 | ||
657 | Before File::Glob entered core in 5.6.0 globbing was implemented by shelling | |
658 | out. If the environmental variable PERL_EXTERNAL_GLOB is defined and if the | |
659 | F<csh> shell is available, perl will still do this the old way. | |
660 | ||
ce80d64e AD |
661 | =head2 Installation Directories |
662 | ||
663 | The installation directories can all be changed by answering the | |
be8498a1 RGS |
664 | appropriate questions in Configure. For convenience, all the installation |
665 | questions are near the beginning of Configure. Do not include trailing | |
666 | slashes on directory names. At any point during the Configure process, | |
667 | you can answer a question with &-d and Configure will use the defaults | |
668 | from then on. Alternatively, you can | |
ce80d64e AD |
669 | |
670 | grep '^install' config.sh | |
671 | ||
672 | after Configure has run to verify the installation paths. | |
673 | ||
674 | The defaults are intended to be reasonable and sensible for most | |
675 | people building from sources. Those who build and distribute binary | |
676 | distributions or who export perl to a range of systems will probably | |
677 | need to alter them. If you are content to just accept the defaults, | |
678 | you can safely skip the next section. | |
679 | ||
680 | The directories set up by Configure fall into three broad categories. | |
681 | ||
682 | =over 4 | |
683 | ||
684 | =item Directories for the perl distribution | |
685 | ||
5585d096 | 686 | By default, Configure will use the following directories for 5.35.10. |
ce80d64e | 687 | $version is the full perl version number, including subversion, e.g. |
8891dd8d | 688 | 5.12.3, and $archname is a string like sun4-sunos, |
ce80d64e AD |
689 | determined by Configure. The full definitions of all Configure |
690 | variables are in the file Porting/Glossary. | |
691 | ||
692 | Configure variable Default value | |
693 | $prefixexp /usr/local | |
694 | $binexp $prefixexp/bin | |
695 | $scriptdirexp $prefixexp/bin | |
696 | $privlibexp $prefixexp/lib/perl5/$version | |
697 | $archlibexp $prefixexp/lib/perl5/$version/$archname | |
698 | $man1direxp $prefixexp/man/man1 | |
699 | $man3direxp $prefixexp/man/man3 | |
700 | $html1direxp (none) | |
701 | $html3direxp (none) | |
702 | ||
ab97e755 MB |
703 | $prefixexp is generated from $prefix, with ~ expansion done to convert |
704 | home directories into absolute paths. Similarly for the other variables | |
705 | listed. As file system calls do not do this, you should always reference | |
706 | the ...exp variables, to support users who build perl in their home | |
707 | directory. | |
ce80d64e AD |
708 | |
709 | Actually, Configure recognizes the SVR3-style | |
710 | /usr/local/man/l_man/man1 directories, if present, and uses those | |
711 | instead. Also, if $prefix contains the string "perl", the library | |
712 | directories are simplified as described below. For simplicity, only | |
713 | the common style is shown here. | |
714 | ||
715 | =item Directories for site-specific add-on files | |
716 | ||
717 | After perl is installed, you may later wish to add modules (e.g. from | |
718 | CPAN) or scripts. Configure will set up the following directories to | |
719 | be used for installing those add-on modules and scripts. | |
720 | ||
979b4168 KW |
721 | Configure Default |
722 | variable value | |
723 | $siteprefixexp $prefixexp | |
724 | $sitebinexp $siteprefixexp/bin | |
725 | $sitescriptexp $siteprefixexp/bin | |
726 | $sitelibexp $siteprefixexp/lib/perl5/site_perl/$version | |
727 | $sitearchexp | |
728 | $siteprefixexp/lib/perl5/site_perl/$version/$archname | |
729 | $siteman1direxp $siteprefixexp/man/man1 | |
730 | $siteman3direxp $siteprefixexp/man/man3 | |
731 | $sitehtml1direxp (none) | |
732 | $sitehtml3direxp (none) | |
ce80d64e AD |
733 | |
734 | By default, ExtUtils::MakeMaker will install architecture-independent | |
735 | modules into $sitelib and architecture-dependent modules into $sitearch. | |
736 | ||
737 | =item Directories for vendor-supplied add-on files | |
738 | ||
739 | Lastly, if you are building a binary distribution of perl for | |
740 | distribution, Configure can optionally set up the following directories | |
741 | for you to use to distribute add-on modules. | |
742 | ||
979b4168 KW |
743 | Configure Default |
744 | variable value | |
745 | $vendorprefixexp (none) | |
746 | ||
747 | (The next ones are set only if vendorprefix is set.) | |
748 | ||
749 | $vendorbinexp $vendorprefixexp/bin | |
750 | $vendorscriptexp $vendorprefixexp/bin | |
751 | $vendorlibexp $vendorprefixexp/lib/perl5/vendor_perl/$version | |
752 | $vendorarchexp | |
753 | $vendorprefixexp/lib/perl5/vendor_perl/$version/$archname | |
754 | $vendorman1direxp $vendorprefixexp/man/man1 | |
755 | $vendorman3direxp $vendorprefixexp/man/man3 | |
756 | $vendorhtml1direxp (none) | |
757 | $vendorhtml3direxp (none) | |
ce80d64e AD |
758 | |
759 | These are normally empty, but may be set as needed. For example, | |
760 | a vendor might choose the following settings: | |
761 | ||
979b4168 KW |
762 | $prefix /usr |
763 | $siteprefix /usr/local | |
764 | $vendorprefix /usr | |
ce80d64e AD |
765 | |
766 | This would have the effect of setting the following: | |
767 | ||
979b4168 KW |
768 | $binexp /usr/bin |
769 | $scriptdirexp /usr/bin | |
770 | $privlibexp /usr/lib/perl5/$version | |
771 | $archlibexp /usr/lib/perl5/$version/$archname | |
772 | $man1direxp /usr/man/man1 | |
773 | $man3direxp /usr/man/man3 | |
774 | ||
775 | $sitebinexp /usr/local/bin | |
776 | $sitescriptexp /usr/local/bin | |
777 | $sitelibexp /usr/local/lib/perl5/site_perl/$version | |
778 | $sitearchexp /usr/local/lib/perl5/site_perl/$version/$archname | |
779 | $siteman1direxp /usr/local/man/man1 | |
780 | $siteman3direxp /usr/local/man/man3 | |
781 | ||
782 | $vendorbinexp /usr/bin | |
783 | $vendorscriptexp /usr/bin | |
784 | $vendorlibexp /usr/lib/perl5/vendor_perl/$version | |
785 | $vendorarchexp /usr/lib/perl5/vendor_perl/$version/$archname | |
786 | $vendorman1direxp /usr/man/man1 | |
787 | $vendorman3direxp /usr/man/man3 | |
ce80d64e AD |
788 | |
789 | Note how in this example, the vendor-supplied directories are in the | |
668cbedd | 790 | /usr hierarchy, while the directories reserved for the end user are in |
ce80d64e AD |
791 | the /usr/local hierarchy. |
792 | ||
793 | The entire installed library hierarchy is installed in locations with | |
794 | version numbers, keeping the installations of different versions distinct. | |
ab97e755 MB |
795 | However, later installations of Perl can still be configured to search |
796 | the installed libraries corresponding to compatible earlier versions. | |
797 | See L<"Coexistence with earlier versions of perl 5"> below for more | |
798 | details on how Perl can be made to search older version directories. | |
ce80d64e AD |
799 | |
800 | Of course you may use these directories however you see fit. For | |
801 | example, you may wish to use $siteprefix for site-specific files that | |
802 | are stored locally on your own disk and use $vendorprefix for | |
803 | site-specific files that are stored elsewhere on your organization's | |
804 | network. One way to do that would be something like | |
805 | ||
979b4168 | 806 | sh Configure -Dsiteprefix=/usr/local -Dvendorprefix=/usr/share/perl |
ce80d64e AD |
807 | |
808 | =item otherlibdirs | |
809 | ||
810 | As a final catch-all, Configure also offers an $otherlibdirs | |
811 | variable. This variable contains a colon-separated list of additional | |
812 | directories to add to @INC. By default, it will be empty. | |
813 | Perl will search these directories (including architecture and | |
814 | version-specific subdirectories) for add-on modules and extensions. | |
815 | ||
816 | For example, if you have a bundle of perl libraries from a previous | |
817 | installation, perhaps in a strange place: | |
818 | ||
f0c21bde | 819 | sh Configure -Dotherlibdirs=/usr/lib/perl5/site_perl/5.8.1 |
ce80d64e AD |
820 | |
821 | =item APPLLIB_EXP | |
822 | ||
823 | There is one other way of adding paths to @INC at perl build time, and | |
824 | that is by setting the APPLLIB_EXP C pre-processor token to a colon- | |
825 | separated list of directories, like this | |
826 | ||
827 | sh Configure -Accflags='-DAPPLLIB_EXP=\"/usr/libperl\"' | |
828 | ||
829 | The directories defined by APPLLIB_EXP get added to @INC I<first>, | |
830 | ahead of any others, and so provide a way to override the standard perl | |
831 | modules should you, for example, want to distribute fixes without | |
832 | touching the perl distribution proper. And, like otherlib dirs, | |
833 | version and architecture specific subdirectories are also searched, if | |
834 | present, at run time. Of course, you can still search other @INC | |
835 | directories ahead of those in APPLLIB_EXP by using any of the standard | |
836 | run-time methods: $PERLLIB, $PERL5LIB, -I, use lib, etc. | |
837 | ||
939e7f26 DM |
838 | =item default_inc_excludes_dot |
839 | ||
988217a0 | 840 | Since version 5.26.0, default perl builds no longer includes C<'.'> as the |
218f5fa9 | 841 | last element of @INC. The old behaviour can restored using |
939e7f26 | 842 | |
f0c21bde | 843 | sh Configure -Udefault_inc_excludes_dot |
939e7f26 DM |
844 | |
845 | Note that this is likely to make programs run under such a perl | |
846 | interpreter less secure. | |
847 | ||
785aa5e3 | 848 | =item usesitecustomize |
20ef40cf GA |
849 | |
850 | Run-time customization of @INC can be enabled with: | |
851 | ||
36de116d | 852 | sh Configure -Dusesitecustomize |
20ef40cf | 853 | |
785aa5e3 RGS |
854 | which will define USE_SITECUSTOMIZE and $Config{usesitecustomize}. |
855 | When enabled, this makes perl run F<$sitelibexp/sitecustomize.pl> before | |
20ef40cf GA |
856 | anything else. This script can then be set up to add additional |
857 | entries to @INC. | |
858 | ||
ce80d64e AD |
859 | =item Man Pages |
860 | ||
be8498a1 RGS |
861 | By default, man pages will be installed in $man1dir and $man3dir, which |
862 | are normally /usr/local/man/man1 and /usr/local/man/man3. If you | |
863 | want to use a .3pm suffix for perl man pages, you can do that with | |
ce80d64e AD |
864 | |
865 | sh Configure -Dman3ext=3pm | |
866 | ||
a36b9036 MB |
867 | You can disable installation of man pages completely using |
868 | ||
869 | sh Configure -Dman1dir=none -Dman3dir=none | |
870 | ||
ce80d64e AD |
871 | =item HTML pages |
872 | ||
873 | Currently, the standard perl installation does not do anything with | |
874 | HTML documentation, but that may change in the future. Further, some | |
875 | add-on modules may wish to install HTML documents. The html Configure | |
876 | variables listed above are provided if you wish to specify where such | |
877 | documents should be placed. The default is "none", but will likely | |
878 | eventually change to something useful based on user feedback. | |
879 | ||
880 | =back | |
881 | ||
882 | Some users prefer to append a "/share" to $privlib and $sitelib | |
883 | to emphasize that those directories can be shared among different | |
884 | architectures. | |
885 | ||
886 | Note that these are just the defaults. You can actually structure the | |
887 | directories any way you like. They don't even have to be on the same | |
888 | filesystem. | |
c3edaffb | 889 | |
ce80d64e AD |
890 | Further details about the installation directories, maintenance and |
891 | development subversions, and about supporting multiple versions are | |
7df75831 | 892 | discussed in L<"Coexistence with earlier versions of perl 5"> below. |
10c7e831 | 893 | |
ce80d64e AD |
894 | If you specify a prefix that contains the string "perl", then the |
895 | library directory structure is slightly simplified. Instead of | |
896 | suggesting $prefix/lib/perl5/, Configure will suggest $prefix/lib. | |
2bf2710f | 897 | |
ce80d64e AD |
898 | Thus, for example, if you Configure with |
899 | -Dprefix=/opt/perl, then the default library directories for 5.9.0 are | |
2bf2710f | 900 | |
ce80d64e AD |
901 | Configure variable Default value |
902 | $privlib /opt/perl/lib/5.9.0 | |
903 | $archlib /opt/perl/lib/5.9.0/$archname | |
904 | $sitelib /opt/perl/lib/site_perl/5.9.0 | |
905 | $sitearch /opt/perl/lib/site_perl/5.9.0/$archname | |
2bf2710f | 906 | |
ce80d64e | 907 | =head2 Changing the installation directory |
c3edaffb | 908 | |
ce80d64e | 909 | Configure distinguishes between the directory in which perl (and its |
7df75831 | 910 | associated files) should be installed, and the directory in which it |
ce80d64e AD |
911 | will eventually reside. For most sites, these two are the same; for |
912 | sites that use AFS, this distinction is handled automatically. | |
7df75831 RGS |
913 | However, sites that use package management software such as rpm or |
914 | dpkg, or users building binary packages for distribution may also | |
915 | wish to install perl into a different directory before moving perl | |
916 | to its final destination. There are two ways to do that: | |
917 | ||
918 | =over 4 | |
919 | ||
920 | =item installprefix | |
c3edaffb | 921 | |
be8498a1 RGS |
922 | To install perl under the /tmp/perl5 directory, use the following |
923 | command line: | |
c3edaffb | 924 | |
7df75831 | 925 | sh Configure -Dinstallprefix=/tmp/perl5 |
c3edaffb | 926 | |
ce80d64e | 927 | (replace /tmp/perl5 by a directory of your choice). |
2bf2710f | 928 | |
ce80d64e AD |
929 | Beware, though, that if you go to try to install new add-on |
930 | modules, they too will get installed in under '/tmp/perl5' if you | |
7df75831 RGS |
931 | follow this example. That's why it's usually better to use DESTDIR, |
932 | as shown in the next section. | |
c3edaffb | 933 | |
7df75831 | 934 | =item DESTDIR |
9d67150a | 935 | |
ce80d64e AD |
936 | If you need to install perl on many identical systems, it is convenient |
937 | to compile it once and create an archive that can be installed on | |
938 | multiple systems. Suppose, for example, that you want to create an | |
939 | archive that can be installed in /opt/perl. One way to do that is by | |
940 | using the DESTDIR variable during C<make install>. The DESTDIR is | |
941 | automatically prepended to all the installation paths. Thus you | |
942 | simply do: | |
830717a7 | 943 | |
ce80d64e AD |
944 | sh Configure -Dprefix=/opt/perl -des |
945 | make | |
946 | make test | |
947 | make install DESTDIR=/tmp/perl5 | |
948 | cd /tmp/perl5/opt/perl | |
949 | tar cvf /tmp/perl5-archive.tar . | |
9d67150a | 950 | |
7df75831 RGS |
951 | =back |
952 | ||
32878f30 NP |
953 | =head2 Relocatable @INC |
954 | ||
955 | To create a relocatable perl tree, use the following command line: | |
956 | ||
957 | sh Configure -Duserelocatableinc | |
958 | ||
959 | Then the paths in @INC (and everything else in %Config) can be | |
960 | optionally located via the path of the perl executable. | |
961 | ||
962 | That means that, if the string ".../" is found at the start of any | |
963 | path, it's substituted with the directory of $^X. So, the relocation | |
964 | can be configured on a per-directory basis, although the default with | |
965 | "-Duserelocatableinc" is that everything is relocated. The initial | |
966 | install is done to the original configured prefix. | |
967 | ||
79f7885c RGS |
968 | This option is not compatible with the building of a shared libperl |
969 | ("-Duseshrplib"), because in that case perl is linked with an hard-coded | |
970 | rpath that points at the libperl.so, that cannot be relocated. | |
971 | ||
ce80d64e | 972 | =head2 Site-wide Policy settings |
55479bb6 | 973 | |
ce80d64e | 974 | After Configure runs, it stores a number of common site-wide "policy" |
7df75831 RGS |
975 | answers (such as installation directories) in the Policy.sh file. |
976 | If you want to build perl on another system using the same policy | |
977 | defaults, simply copy the Policy.sh file to the new system's perl build | |
978 | directory, and Configure will use it. This will work even if Policy.sh was | |
a0a8d9d3 | 979 | generated for another version of Perl, or on a system with a |
da1b4322 | 980 | different architecture and/or operating system. However, in such cases, |
a0a8d9d3 DD |
981 | you should review the contents of the file before using it: for |
982 | example, your new target may not keep its man pages in the same place | |
983 | as the system on which the file was generated. | |
55479bb6 | 984 | |
ce80d64e AD |
985 | Alternatively, if you wish to change some or all of those policy |
986 | answers, you should | |
c3edaffb | 987 | |
ce80d64e | 988 | rm -f Policy.sh |
aa689395 | 989 | |
ce80d64e | 990 | to ensure that Configure doesn't re-use them. |
2ae324a7 | 991 | |
ce80d64e | 992 | Further information is in the Policy_sh.SH file itself. |
aa689395 | 993 | |
ce80d64e AD |
994 | If the generated Policy.sh file is unsuitable, you may freely edit it |
995 | to contain any valid shell commands. It will be run just after the | |
996 | platform-specific hints files. | |
aa689395 | 997 | |
ce80d64e | 998 | =head2 Disabling older versions of Perl |
aa689395 | 999 | |
ce80d64e | 1000 | Configure will search for binary compatible versions of previously |
7df75831 RGS |
1001 | installed perl binaries in the tree that is specified as target tree, |
1002 | and these will be used as locations to search for modules by the perl | |
1003 | being built. The list of perl versions found will be put in the Configure | |
1004 | variable inc_version_list. | |
86058a2d | 1005 | |
ab97e755 MB |
1006 | To disable this use of older perl modules, even completely valid pure |
1007 | perl modules, you can specify to not include the paths found: | |
b2a6d19e | 1008 | |
ce80d64e | 1009 | sh Configure -Dinc_version_list=none ... |
d6baa268 | 1010 | |
ab97e755 MB |
1011 | If you do want to use modules from some previous perl versions, the |
1012 | variable must contain a space separated list of directories under the | |
1013 | site_perl directory, and has to include architecture-dependent | |
1014 | directories separately, eg. | |
274ca399 | 1015 | |
4683a5d7 | 1016 | sh Configure -Dinc_version_list="5.16.0/x86_64-linux 5.16.0" ... |
274ca399 | 1017 | |
ce80d64e | 1018 | When using the newer perl, you can add these paths again in the |
668cbedd | 1019 | PERL5LIB environment variable or with perl's -I runtime option. |
86058a2d | 1020 | |
ce80d64e | 1021 | =head2 Building Perl outside of the source directory |
86058a2d | 1022 | |
ce80d64e AD |
1023 | Sometimes it is desirable to build Perl in a directory different from |
1024 | where the sources are, for example if you want to keep your sources | |
1025 | read-only, or if you want to share the sources between different binary | |
1026 | architectures. You can do this (if your file system supports symbolic | |
1027 | links) by | |
06c896bb | 1028 | |
ce80d64e AD |
1029 | mkdir /tmp/perl/build/directory |
1030 | cd /tmp/perl/build/directory | |
1031 | sh /path/to/perl/source/Configure -Dmksymlinks ... | |
06c896bb | 1032 | |
ce80d64e AD |
1033 | This will create in /tmp/perl/build/directory a tree of symbolic links |
1034 | pointing to files in /path/to/perl/source. The original files are left | |
1035 | unaffected. After Configure has finished you can just say | |
06c896bb | 1036 | |
ce80d64e | 1037 | make |
7df75831 RGS |
1038 | make test |
1039 | make install | |
06c896bb | 1040 | |
ce80d64e | 1041 | as usual, and Perl will be built in /tmp/perl/build/directory. |
aa689395 | 1042 | |
3bf462b8 CS |
1043 | =head2 Building a debugging perl |
1044 | ||
1045 | You can run perl scripts under the perl debugger at any time with | |
3fe9a6f1 | 1046 | B<perl -d your_script>. If, however, you want to debug perl itself, |
eaf812ae MB |
1047 | you probably want to have support for perl internal debugging code |
1048 | (activated by adding -DDEBUGGING to ccflags), and/or support for the | |
f075db89 | 1049 | system debugger by adding -g to the optimisation flags. |
eaf812ae | 1050 | |
f075db89 DM |
1051 | A perl compiled with the DEBUGGING C preprocessor macro will support the |
1052 | C<-D> perl command-line switch, have assertions enabled, and have many | |
1053 | extra checks compiled into the code; but will execute much more slowly | |
1054 | (typically 2-3x) and the binary will be much larger (typically 2-3x). | |
08854360 | 1055 | |
f075db89 DM |
1056 | As a convenience, debugging code (-DDEBUGGING) and debugging symbols (-g) |
1057 | can be enabled jointly or separately using a Configure switch, also | |
1058 | (somewhat confusingly) named -DDEBUGGING. For a more eye appealing call, | |
1059 | -DEBUGGING is defined to be an alias for -DDEBUGGING. For both, the -U | |
1060 | calls are also supported, in order to be able to overrule the hints or | |
1061 | Policy.sh settings. | |
eaf812ae | 1062 | |
7df75831 | 1063 | Here are the DEBUGGING modes: |
3bf462b8 | 1064 | |
7df75831 | 1065 | =over 4 |
3bf462b8 | 1066 | |
f075db89 | 1067 | =item Configure -DDEBUGGING |
eaf812ae | 1068 | |
f075db89 | 1069 | =item Configure -DEBUGGING |
eaf812ae | 1070 | |
f075db89 | 1071 | =item Configure -DEBUGGING=both |
eaf812ae | 1072 | |
7df75831 RGS |
1073 | Sets both -DDEBUGGING in the ccflags, and adds -g to optimize. |
1074 | ||
1075 | You can actually specify -g and -DDEBUGGING independently (see below), | |
1076 | but usually it's convenient to have both. | |
eaf812ae | 1077 | |
f075db89 | 1078 | =item Configure -DEBUGGING=-g |
eaf812ae | 1079 | |
f075db89 | 1080 | =item Configure -Doptimize=-g |
7df75831 | 1081 | |
eaf812ae MB |
1082 | Adds -g to optimize, but does not set -DDEBUGGING. |
1083 | ||
7df75831 RGS |
1084 | (Note: Your system may actually require something like cc -g2. |
1085 | Check your man pages for cc(1) and also any hint file for your system.) | |
1086 | ||
f075db89 | 1087 | =item Configure -DEBUGGING=none |
eaf812ae | 1088 | |
f075db89 | 1089 | =item Configure -UDEBUGGING |
7df75831 | 1090 | |
eaf812ae MB |
1091 | Removes -g from optimize, and -DDEBUGGING from ccflags. |
1092 | ||
1093 | =back | |
1094 | ||
3bf462b8 | 1095 | If you are using a shared libperl, see the warnings about multiple |
ef460fb9 | 1096 | versions of perl under L</Building a shared Perl library>. |
3bf462b8 | 1097 | |
def5f8a5 DM |
1098 | Note that a perl built with -DDEBUGGING will be much bigger and will run |
1099 | much, much more slowly than a standard perl. | |
1db12997 DM |
1100 | |
1101 | =head2 DTrace support | |
1102 | ||
979b4168 | 1103 | On platforms where DTrace is available, it may be enabled by |
ab97e755 MB |
1104 | using the -Dusedtrace option to Configure. DTrace probes are available |
1105 | for subroutine entry (sub-entry) and subroutine exit (sub-exit). Here's a | |
1db12997 DM |
1106 | simple D script that uses them: |
1107 | ||
1108 | perl$target:::sub-entry, perl$target:::sub-return { | |
1109 | printf("%s %s (%s:%d)\n", probename == "sub-entry" ? "->" : "<-", | |
1110 | copyinstr(arg0), copyinstr(arg1), arg2); | |
1111 | } | |
1112 | ||
1113 | ||
8d74ce1c AD |
1114 | =head2 Extensions |
1115 | ||
80c1f5de | 1116 | Perl ships with a number of standard extensions. These are contained |
b0a63d58 | 1117 | in the F<ext/> subdirectory. |
80c1f5de | 1118 | |
8d74ce1c AD |
1119 | By default, Configure will offer to build every extension which appears |
1120 | to be supported. For example, Configure will offer to build GDBM_File | |
7df75831 | 1121 | only if it is able to find the gdbm library. |
ce80d64e AD |
1122 | |
1123 | To disable certain extensions so that they are not built, use the | |
1124 | -Dnoextensions=... and -Donlyextensions=... options. They both accept | |
47bd56ab DM |
1125 | a space-separated list of extensions, such as C<IPC/SysV>. The extensions |
1126 | listed in | |
ce80d64e AD |
1127 | C<noextensions> are removed from the list of extensions to build, while |
1128 | the C<onlyextensions> is rather more severe and builds only the listed | |
1129 | extensions. The latter should be used with extreme caution since | |
1130 | certain extensions are used by many other extensions and modules: | |
1131 | examples of such modules include Fcntl and IO. The order of processing | |
1132 | these options is first C<only> (if present), then C<no> (if present). | |
8d74ce1c AD |
1133 | |
1134 | Of course, you may always run Configure interactively and select only | |
1135 | the extensions you want. | |
1136 | ||
7df75831 RGS |
1137 | If you unpack any additional extensions in the ext/ directory before |
1138 | running Configure, then Configure will offer to build those additional | |
1139 | extensions as well. Most users probably shouldn't have to do this -- | |
1140 | it is usually easier to build additional extensions later after perl | |
1141 | has been installed. However, if you wish to have those additional | |
1142 | extensions statically linked into the perl binary, then this offers a | |
1143 | convenient way to do that in one step. (It is not necessary, however; | |
1144 | you can build and install extensions just fine even if you don't have | |
1145 | dynamic loading. See lib/ExtUtils/MakeMaker.pm for more details.) | |
1146 | Another way of specifying extra modules is described in | |
1147 | L<"Adding extra modules to the build"> below. | |
8d74ce1c | 1148 | |
dd3196cd | 1149 | If you re-use an old config.sh but change your system (e.g. by |
8d74ce1c AD |
1150 | adding libgdbm) Configure will still offer your old choices of extensions |
1151 | for the default answer, but it will also point out the discrepancy to | |
1152 | you. | |
1153 | ||
8d74ce1c AD |
1154 | =head2 Including locally-installed libraries |
1155 | ||
7df75831 RGS |
1156 | Perl comes with interfaces to number of libraries, including threads, |
1157 | dbm, ndbm, gdbm, and Berkeley db. For the *db* extension, if | |
8d74ce1c | 1158 | Configure can find the appropriate header files and libraries, it will |
7df75831 | 1159 | automatically include that extension. The threading extension needs |
27021420 | 1160 | to be specified explicitly (see L</Threads>). |
7df75831 RGS |
1161 | |
1162 | Those libraries are not distributed with perl. If your header (.h) files | |
1163 | for those libraries are not in a directory normally searched by your C | |
1164 | compiler, then you will need to include the appropriate -I/your/directory | |
1165 | option when prompted by Configure. If your libraries are not in a | |
1166 | directory normally searched by your C compiler and linker, then you will | |
1167 | need to include the appropriate -L/your/directory option when prompted | |
1168 | by Configure. See the examples below. | |
8d74ce1c | 1169 | |
ce80d64e | 1170 | =head3 Examples |
8d74ce1c AD |
1171 | |
1172 | =over 4 | |
1173 | ||
1174 | =item gdbm in /usr/local | |
1175 | ||
1176 | Suppose you have gdbm and want Configure to find it and build the | |
d6baa268 | 1177 | GDBM_File extension. This example assumes you have gdbm.h |
8d74ce1c AD |
1178 | installed in /usr/local/include/gdbm.h and libgdbm.a installed in |
1179 | /usr/local/lib/libgdbm.a. Configure should figure all the | |
1180 | necessary steps out automatically. | |
1181 | ||
1182 | Specifically, when Configure prompts you for flags for | |
7df75831 RGS |
1183 | your C compiler, you should include -I/usr/local/include, if it's |
1184 | not here yet. Similarly, when Configure prompts you for linker flags, | |
1185 | you should include -L/usr/local/lib. | |
8d74ce1c AD |
1186 | |
1187 | If you are using dynamic loading, then when Configure prompts you for | |
1188 | linker flags for dynamic loading, you should again include | |
1189 | -L/usr/local/lib. | |
1190 | ||
d6baa268 JH |
1191 | Again, this should all happen automatically. This should also work if |
1192 | you have gdbm installed in any of (/usr/local, /opt/local, /usr/gnu, | |
1193 | /opt/gnu, /usr/GNU, or /opt/GNU). | |
8d74ce1c | 1194 | |
e8b9ce60 AD |
1195 | =item BerkeleyDB in /usr/local/BerkeleyDB |
1196 | ||
668cbedd | 1197 | The version of BerkeleyDB distributed by Oracle installs in a |
e8b9ce60 AD |
1198 | version-specific directory by default, typically something like |
1199 | /usr/local/BerkeleyDB.4.7. To have Configure find that, you need to add | |
ab97e755 MB |
1200 | -I/usr/local/BerkeleyDB.4.7/include to cc flags, as in the previous |
1201 | example, and you will also have to take extra steps to help Configure | |
1202 | find -ldb. Specifically, when Configure prompts you for library | |
1203 | directories, add /usr/local/BerkeleyDB.4.7/lib to the list. Also, you | |
1204 | will need to add appropriate linker flags to tell the runtime linker | |
1205 | where to find the BerkeleyDB shared libraries. | |
e8b9ce60 AD |
1206 | |
1207 | It is possible to specify this from the command line (all on one | |
8d74ce1c AD |
1208 | line): |
1209 | ||
979b4168 KW |
1210 | sh Configure -de \ |
1211 | -Dlocincpth='/usr/local/BerkeleyDB.4.7/include \ | |
1212 | /usr/local/include' \ | |
1213 | -Dloclibpth='/usr/local/BerkeleyDB.4.7/lib /usr/local/lib' \ | |
1214 | -Aldflags='-R/usr/local/BerkeleyDB.4.7/lib' | |
8d74ce1c AD |
1215 | |
1216 | locincpth is a space-separated list of include directories to search. | |
1217 | Configure will automatically add the appropriate -I directives. | |
1218 | ||
1219 | loclibpth is a space-separated list of library directories to search. | |
e8b9ce60 | 1220 | Configure will automatically add the appropriate -L directives. |
8d74ce1c | 1221 | |
e8b9ce60 AD |
1222 | The addition to ldflags is so that the dynamic linker knows where to find |
1223 | the BerkeleyDB libraries. For Linux and Solaris, the -R option does that. | |
1224 | Other systems may use different flags. Use the appropriate flag for your | |
1225 | system. | |
8d74ce1c AD |
1226 | |
1227 | =back | |
1228 | ||
b76ca5cc BF |
1229 | =head2 Specifying a logical root directory |
1230 | ||
1231 | If you are cross-compiling, or are using a compiler which has it's own | |
1232 | headers and libraries in a nonstandard location, and your compiler | |
ab97e755 MB |
1233 | understands the C<--sysroot> option, you can use the C<-Dsysroot> option |
1234 | to specify the logical root directory under which all libraries and | |
1235 | headers are searched for. This patch adjusts Configure to search under | |
1236 | $sysroot, instead of /. | |
1237 | ||
b76ca5cc BF |
1238 | --sysroot is added to ccflags and friends so that make in |
1239 | ExtUtils::MakeMaker, and other extensions, will use it. | |
1240 | ||
ce80d64e AD |
1241 | =head2 Overriding an old config.sh |
1242 | ||
dd3196cd RGS |
1243 | If you want to use an old config.sh produced by a previous run of |
1244 | Configure, but override some of the items with command line options, you | |
1245 | need to use B<Configure -O>. | |
ce80d64e AD |
1246 | |
1247 | =head2 GNU-style configure | |
1248 | ||
1249 | If you prefer the GNU-style configure command line interface, you can | |
1250 | use the supplied configure.gnu command, e.g. | |
1251 | ||
1252 | CC=gcc ./configure.gnu | |
1253 | ||
1254 | The configure.gnu script emulates a few of the more common configure | |
1255 | options. Try | |
1256 | ||
1257 | ./configure.gnu --help | |
1258 | ||
1259 | for a listing. | |
1260 | ||
1261 | (The file is called configure.gnu to avoid problems on systems | |
1262 | that would not distinguish the files "Configure" and "configure".) | |
1263 | ||
ce80d64e AD |
1264 | =head2 Malloc Issues |
1265 | ||
1266 | Perl relies heavily on malloc(3) to grow data structures as needed, | |
1267 | so perl's performance can be noticeably affected by the performance of | |
1268 | the malloc function on your system. The perl source is shipped with a | |
1269 | version of malloc that has been optimized for the typical requests from | |
1270 | perl, so there's a chance that it may be both faster and use less memory | |
1271 | than your system malloc. | |
1272 | ||
1273 | However, if your system already has an excellent malloc, or if you are | |
1274 | experiencing difficulties with extensions that use third-party libraries | |
1275 | that call malloc, then you should probably use your system's malloc. | |
1276 | (Or, you might wish to explore the malloc flags discussed below.) | |
1277 | ||
1278 | =over 4 | |
1279 | ||
1280 | =item Using the system malloc | |
1281 | ||
1282 | To build without perl's malloc, you can use the Configure command | |
1283 | ||
1284 | sh Configure -Uusemymalloc | |
1285 | ||
1286 | or you can answer 'n' at the appropriate interactive Configure prompt. | |
1287 | ||
73d6d1b0 RGS |
1288 | Note that Perl's malloc isn't always used by default; that actually |
1289 | depends on your system. For example, on Linux and FreeBSD (and many more | |
1290 | systems), Configure chooses to use the system's malloc by default. | |
1291 | See the appropriate file in the F<hints/> directory to see how the | |
1292 | default is set. | |
1293 | ||
ce80d64e AD |
1294 | =item -DPERL_POLLUTE_MALLOC |
1295 | ||
1296 | NOTE: This flag is enabled automatically on some platforms if you just | |
7df75831 | 1297 | run Configure to accept all the defaults. |
ce80d64e AD |
1298 | |
1299 | Perl's malloc family of functions are normally called Perl_malloc(), | |
1300 | Perl_realloc(), Perl_calloc() and Perl_mfree(). | |
1301 | These names do not clash with the system versions of these functions. | |
1302 | ||
1303 | If this flag is enabled, however, Perl's malloc family of functions | |
1304 | will have the same names as the system versions. This may be required | |
1305 | sometimes if you have libraries that like to free() data that may have | |
1306 | been allocated by Perl_malloc() and vice versa. | |
1307 | ||
1308 | Note that enabling this option may sometimes lead to duplicate symbols | |
1309 | from the linker for malloc et al. In such cases, the system probably | |
1310 | does not allow its malloc functions to be fully replaced with custom | |
1311 | versions. | |
1312 | ||
1313 | =item -DPERL_DEBUGGING_MSTATS | |
1314 | ||
1315 | This flag enables debugging mstats, which is required to use the | |
1316 | Devel::Peek::mstat() function. You cannot enable this unless you are | |
1317 | using Perl's malloc, so a typical Configure command would be | |
1318 | ||
7df75831 | 1319 | sh Configure -Accflags=-DPERL_DEBUGGING_MSTATS -Dusemymalloc |
ce80d64e AD |
1320 | |
1321 | to enable this option. | |
1322 | ||
1323 | =back | |
1324 | ||
8e07c86e AD |
1325 | =head2 What if it doesn't work? |
1326 | ||
8d74ce1c | 1327 | If you run into problems, try some of the following ideas. |
ff52061e | 1328 | If none of them help, then see L<"Reporting Problems"> below. |
8d74ce1c | 1329 | |
8e07c86e AD |
1330 | =over 4 |
1331 | ||
25f94b33 AD |
1332 | =item Running Configure Interactively |
1333 | ||
1334 | If Configure runs into trouble, remember that you can always run | |
1335 | Configure interactively so that you can check (and correct) its | |
1336 | guesses. | |
1337 | ||
1338 | All the installation questions have been moved to the top, so you don't | |
aa689395 | 1339 | have to wait for them. Once you've handled them (and your C compiler and |
1ec51d55 | 1340 | flags) you can type &-d at the next Configure prompt and Configure |
25f94b33 AD |
1341 | will use the defaults from then on. |
1342 | ||
1343 | If you find yourself trying obscure command line incantations and | |
1344 | config.over tricks, I recommend you run Configure interactively | |
1345 | instead. You'll probably save yourself time in the long run. | |
1346 | ||
aa689395 | 1347 | =item Hint files |
8e07c86e | 1348 | |
a0a8d9d3 DD |
1349 | Hint files tell Configure about a number of things: |
1350 | ||
1351 | =over 4 | |
1352 | ||
1353 | =item o | |
1354 | ||
1355 | The peculiarities or conventions of particular platforms -- non-standard | |
1356 | library locations and names, default installation locations for binaries, | |
1357 | and so on. | |
1358 | ||
1359 | =item o | |
1360 | ||
1361 | The deficiencies of the platform -- for example, library functions that, | |
1362 | although present, are too badly broken to be usable; or limits on | |
1363 | resources that are generously available on most platforms. | |
1364 | ||
1365 | =item o | |
1366 | ||
ab97e755 MB |
1367 | How best to optimize for the platform, both in terms of binary size |
1368 | and/or speed, and for Perl feature support. Because of wide variations in | |
1369 | the implementation of shared libraries and of threading, for example, | |
1370 | Configure often needs hints in order to be able to use these features. | |
a0a8d9d3 DD |
1371 | |
1372 | =back | |
1373 | ||
1374 | The perl distribution includes many system-specific hints files | |
1375 | in the hints/ directory. If one of them matches your system, Configure | |
1376 | will offer to use that hint file. Unless you have a very good reason | |
1377 | not to, you should accept its offer. | |
8e07c86e AD |
1378 | |
1379 | Several of the hint files contain additional important information. | |
ab97e755 MB |
1380 | If you have any problems, it is a good idea to read the relevant hint |
1381 | file for further information. See hints/solaris_2.sh for an extensive | |
1382 | example. More information about writing good hints is in the | |
1383 | hints/README.hints file, which also explains hint files known as | |
1384 | callback-units. | |
a0a8d9d3 DD |
1385 | |
1386 | Note that any hint file is read before any Policy file, meaning that | |
1387 | Policy overrides hints -- see L</Site-wide Policy settings>. | |
8e07c86e | 1388 | |
73d6d1b0 | 1389 | =item WHOA THERE!!! |
edb1cbcb | 1390 | |
ab97e755 MB |
1391 | If you are re-using an old config.sh, it's possible that Configure |
1392 | detects different values from the ones specified in this file. You will | |
1393 | almost always want to keep the previous value, unless you have changed | |
1394 | something on your system. | |
edb1cbcb | 1395 | |
1396 | For example, suppose you have added libgdbm.a to your system | |
1397 | and you decide to reconfigure perl to use GDBM_File. When you run | |
1398 | Configure again, you will need to add -lgdbm to the list of libraries. | |
bfb7748a AD |
1399 | Now, Configure will find your gdbm include file and library and will |
1400 | issue a message: | |
edb1cbcb | 1401 | |
1402 | *** WHOA THERE!!! *** | |
1403 | The previous value for $i_gdbm on this machine was "undef"! | |
1404 | Keep the previous value? [y] | |
1405 | ||
1ec51d55 | 1406 | In this case, you do not want to keep the previous value, so you |
c3edaffb | 1407 | should answer 'n'. (You'll also have to manually add GDBM_File to |
edb1cbcb | 1408 | the list of dynamic extensions to build.) |
1409 | ||
8e07c86e AD |
1410 | =item Changing Compilers |
1411 | ||
1412 | If you change compilers or make other significant changes, you should | |
1ec51d55 | 1413 | probably not re-use your old config.sh. Simply remove it or |
dd3196cd | 1414 | rename it, then rerun Configure with the options you want to use. |
8e07c86e | 1415 | |
c3edaffb | 1416 | =item Propagating your changes to config.sh |
8e07c86e | 1417 | |
1ec51d55 CS |
1418 | If you make any changes to config.sh, you should propagate |
1419 | them to all the .SH files by running | |
1420 | ||
1421 | sh Configure -S | |
1422 | ||
1423 | You will then have to rebuild by running | |
9d67150a | 1424 | |
1425 | make depend | |
1426 | make | |
8e07c86e | 1427 | |
48370efc JH |
1428 | =item config.over and config.arch |
1429 | ||
668cbedd | 1430 | You can also supply a shell script config.over to override |
48370efc JH |
1431 | Configure's guesses. It will get loaded up at the very end, just |
1432 | before config.sh is created. You have to be careful with this, | |
1433 | however, as Configure does no checking that your changes make sense. | |
1434 | This file is usually good for site-specific customizations. | |
1435 | ||
1436 | There is also another file that, if it exists, is loaded before the | |
1437 | config.over, called config.arch. This file is intended to be per | |
1438 | architecture, not per site, and usually it's the architecture-specific | |
1439 | hints file that creates the config.arch. | |
8e07c86e AD |
1440 | |
1441 | =item config.h | |
1442 | ||
1ec51d55 CS |
1443 | Many of the system dependencies are contained in config.h. |
1444 | Configure builds config.h by running the config_h.SH script. | |
1445 | The values for the variables are taken from config.sh. | |
8e07c86e | 1446 | |
1ec51d55 CS |
1447 | If there are any problems, you can edit config.h directly. Beware, |
1448 | though, that the next time you run Configure, your changes will be | |
8e07c86e AD |
1449 | lost. |
1450 | ||
1451 | =item cflags | |
1452 | ||
1453 | If you have any additional changes to make to the C compiler command | |
1ec51d55 | 1454 | line, they can be made in cflags.SH. For instance, to turn off the |
5729ffdd NC |
1455 | optimizer on toke.c, find the switch structure marked 'or customize here', |
1456 | and add a line for toke.c ahead of the catch-all *) so that it now reads: | |
1457 | ||
1458 | : or customize here | |
1459 | ||
1460 | case "$file" in | |
1461 | toke) optimize='-g' ;; | |
1462 | *) ;; | |
1463 | ||
ab97e755 MB |
1464 | You should not edit the generated file cflags directly, as your changes |
1465 | will be lost the next time you run Configure, or if you edit config.sh. | |
8e07c86e | 1466 | |
f5b3b617 AD |
1467 | To explore various ways of changing ccflags from within a hint file, |
1468 | see the file hints/README.hints. | |
1469 | ||
1470 | To change the C flags for all the files, edit config.sh and change either | |
1471 | $ccflags or $optimize, and then re-run | |
1ec51d55 CS |
1472 | |
1473 | sh Configure -S | |
1474 | make depend | |
8e07c86e | 1475 | |
aa689395 | 1476 | =item No sh |
8e07c86e | 1477 | |
c42e3e15 GS |
1478 | If you don't have sh, you'll have to copy the sample file |
1479 | Porting/config.sh to config.sh and edit your config.sh to reflect your | |
1480 | system's peculiarities. See Porting/pumpkin.pod for more information. | |
8e07c86e AD |
1481 | You'll probably also have to extensively modify the extension building |
1482 | mechanism. | |
1483 | ||
c3edaffb | 1484 | =item Porting information |
1485 | ||
e6f03d26 | 1486 | Specific information for the OS/2, Plan 9, VMS and Win32 ports is in the |
1ec51d55 CS |
1487 | corresponding README files and subdirectories. Additional information, |
1488 | including a glossary of all those config.sh variables, is in the Porting | |
ce80d64e | 1489 | subdirectory. Porting/Glossary should especially come in handy. |
c3edaffb | 1490 | |
7f678428 | 1491 | Ports for other systems may also be available. You should check out |
f6521f7c | 1492 | L<https://www.cpan.org/ports> for current information on ports to |
7f678428 | 1493 | various other operating systems. |
1494 | ||
ce80d64e | 1495 | If you plan to port Perl to a new architecture, study carefully the |
491517e0 | 1496 | section titled "Philosophical Issues in Patching and Porting Perl" |
c222ef46 | 1497 | in the file Porting/pumpkin.pod and the file pod/perlgit.pod. |
491517e0 JA |
1498 | Study also how other non-UNIX ports have solved problems. |
1499 | ||
8e07c86e AD |
1500 | =back |
1501 | ||
ce80d64e | 1502 | =head2 Adding extra modules to the build |
fadf0ef5 JH |
1503 | |
1504 | You can specify extra modules or module bundles to be fetched from the | |
1505 | CPAN and installed as part of the Perl build. Either use the -Dextras=... | |
1506 | command line parameter to Configure, for example like this: | |
1507 | ||
d3df0cfd | 1508 | Configure -Dextras="Bundle::LWP DBI" |
fadf0ef5 JH |
1509 | |
1510 | or answer first 'y' to the question 'Install any extra modules?' and | |
d3df0cfd | 1511 | then answer "Bundle::LWP DBI" to the 'Extras?' question. |
ab97e755 MB |
1512 | The module or the bundle names are as for the CPAN module 'install' |
1513 | command. This will only work if those modules are to be built as dynamic | |
a522f097 AD |
1514 | extensions. If you wish to include those extra modules as static |
1515 | extensions, see L<"Extensions"> above. | |
fadf0ef5 JH |
1516 | |
1517 | Notice that because the CPAN module will be used to fetch the extra | |
1518 | modules, you will need access to the CPAN, either via the Internet, | |
1519 | or via a local copy such as a CD-ROM or a local CPAN mirror. If you | |
1520 | do not, using the extra modules option will die horribly. | |
1521 | ||
1522 | Also notice that you yourself are responsible for satisfying any extra | |
ab97e755 MB |
1523 | dependencies such as external headers or libraries BEFORE trying the |
1524 | build. For example: you will need to have the Foo database specific | |
fadf0ef5 JH |
1525 | headers and libraries installed for the DBD::Foo module. The Configure |
1526 | process or the Perl build process will not help you with these. | |
1527 | ||
ce80d64e | 1528 | =head2 suidperl |
03739d21 | 1529 | |
172dd959 JV |
1530 | suidperl was an optional component of earlier releases of perl. It is no |
1531 | longer available. Instead, use a tool specifically designed to handle | |
1532 | changes in privileges, such as B<sudo>. | |
03739d21 | 1533 | |
8e07c86e AD |
1534 | =head1 make depend |
1535 | ||
bfb7748a AD |
1536 | This will look for all the includes. The output is stored in makefile. |
1537 | The only difference between Makefile and makefile is the dependencies at | |
1538 | the bottom of makefile. If you have to make any changes, you should edit | |
ce80d64e | 1539 | makefile, not Makefile, since the Unix make command reads makefile first. |
bfb7748a AD |
1540 | (On non-Unix systems, the output may be stored in a different file. |
1541 | Check the value of $firstmakefile in your config.sh if in doubt.) | |
8e07c86e AD |
1542 | |
1543 | Configure will offer to do this step for you, so it isn't listed | |
1544 | explicitly above. | |
1545 | ||
1546 | =head1 make | |
1547 | ||
1548 | This will attempt to make perl in the current directory. | |
1549 | ||
8d410bc4 YST |
1550 | =head2 Expected errors |
1551 | ||
f5b5f377 | 1552 | These error reports are normal, and can be ignored: |
8d410bc4 YST |
1553 | |
1554 | ... | |
1555 | make: [extra.pods] Error 1 (ignored) | |
1556 | ... | |
1557 | make: [extras.make] Error 1 (ignored) | |
1558 | ||
8d74ce1c AD |
1559 | =head2 What if it doesn't work? |
1560 | ||
8e07c86e | 1561 | If you can't compile successfully, try some of the following ideas. |
7f678428 | 1562 | If none of them help, and careful reading of the error message and |
8d74ce1c | 1563 | the relevant manual pages on your system doesn't help, |
ff52061e | 1564 | then see L<"Reporting Problems"> below. |
8e07c86e AD |
1565 | |
1566 | =over 4 | |
1567 | ||
1ec51d55 | 1568 | =item hints |
8e07c86e AD |
1569 | |
1570 | If you used a hint file, try reading the comments in the hint file | |
1571 | for further tips and information. | |
1572 | ||
1ec51d55 | 1573 | =item extensions |
8e07c86e | 1574 | |
1ec51d55 | 1575 | If you can successfully build miniperl, but the process crashes |
ce80d64e | 1576 | during the building of extensions, run |
c3edaffb | 1577 | |
3a6175e1 | 1578 | make minitest |
c3edaffb | 1579 | |
1580 | to test your version of miniperl. | |
1581 | ||
e57fd563 | 1582 | =item locale |
1583 | ||
bfb7748a AD |
1584 | If you have any locale-related environment variables set, try unsetting |
1585 | them. I have some reports that some versions of IRIX hang while | |
1586 | running B<./miniperl configpm> with locales other than the C locale. | |
1587 | See the discussion under L<"make test"> below about locales and the | |
ab97e755 MB |
1588 | whole L<perllocale/"LOCALE PROBLEMS"> section in the file |
1589 | pod/perllocale.pod. The latter is especially useful if you see something | |
1590 | like this | |
3e6e419a JH |
1591 | |
1592 | perl: warning: Setting locale failed. | |
1593 | perl: warning: Please check that your locale settings: | |
1594 | LC_ALL = "En_US", | |
1595 | LANG = (unset) | |
1596 | are supported and installed on your system. | |
1597 | perl: warning: Falling back to the standard locale ("C"). | |
1598 | ||
1599 | at Perl startup. | |
e57fd563 | 1600 | |
06aa495b DM |
1601 | =item other environment variables |
1602 | ||
1603 | Configure does not check for environment variables that can sometimes | |
1604 | have a major influence on how perl is built or tested. For example, | |
1605 | OBJECT_MODE on AIX determines the way the compiler and linker deal with | |
1606 | their objects, but this is a variable that only influences build-time | |
1607 | behaviour, and should not affect the perl scripts that are eventually | |
1608 | executed by the perl binary. Other variables, like PERL_UNICODE, | |
adbb55c0 | 1609 | PERL5LIB, and PERL5OPT will influence the behaviour of the test suite. |
06aa495b DM |
1610 | So if you are getting strange test failures, you may want to try |
1611 | retesting with the various PERL variables unset. | |
1612 | ||
1ec51d55 | 1613 | =item LD_LIBRARY_PATH |
c3edaffb | 1614 | |
1615 | If you run into dynamic loading problems, check your setting of | |
0fd807f7 KW |
1616 | the LD_LIBRARY_PATH environment variable (or on some systems the equivalent |
1617 | with a different name, see L</Building a shared Perl library>). If you're | |
1618 | creating a static Perl library (libperl.a rather than libperl.so) it should | |
1619 | build fine with LD_LIBRARY_PATH unset, though that may depend on details of | |
1620 | your local setup. | |
c3edaffb | 1621 | |
aa689395 | 1622 | =item nm extraction |
c3edaffb | 1623 | |
1624 | If Configure seems to be having trouble finding library functions, | |
1625 | try not using nm extraction. You can do this from the command line | |
1626 | with | |
1627 | ||
1628 | sh Configure -Uusenm | |
1629 | ||
1630 | or by answering the nm extraction question interactively. | |
1ec51d55 | 1631 | If you have previously run Configure, you should not reuse your old |
c3edaffb | 1632 | config.sh. |
1633 | ||
bfb7748a AD |
1634 | =item umask not found |
1635 | ||
1636 | If the build processes encounters errors relating to umask(), the problem | |
1637 | is probably that Configure couldn't find your umask() system call. | |
1638 | Check your config.sh. You should have d_umask='define'. If you don't, | |
1639 | this is probably the L<"nm extraction"> problem discussed above. Also, | |
1640 | try reading the hints file for your system for further information. | |
1641 | ||
3fe9a6f1 | 1642 | =item do_aspawn |
1643 | ||
1644 | If you run into problems relating to do_aspawn or do_spawn, the | |
1645 | problem is probably that Configure failed to detect your system's | |
bfb7748a AD |
1646 | fork() function. Follow the procedure in the previous item |
1647 | on L<"nm extraction">. | |
3fe9a6f1 | 1648 | |
84902520 TB |
1649 | =item __inet_* errors |
1650 | ||
1651 | If you receive unresolved symbol errors during Perl build and/or test | |
1652 | referring to __inet_* symbols, check to see whether BIND 8.1 is | |
1653 | installed. It installs a /usr/local/include/arpa/inet.h that refers to | |
1654 | these symbols. Versions of BIND later than 8.1 do not install inet.h | |
1655 | in that location and avoid the errors. You should probably update to a | |
6d240721 | 1656 | newer version of BIND (and remove the files the old one left behind). |
ab97e755 MB |
1657 | If you can't, you can either link with the updated resolver library |
1658 | provided with BIND 8.1 or rename /usr/local/bin/arpa/inet.h during the | |
1659 | Perl build and test process to avoid the problem. | |
6d240721 | 1660 | |
73d6d1b0 | 1661 | =item .*_r() prototype NOT found |
6d240721 JH |
1662 | |
1663 | On a related note, if you see a bunch of complaints like the above about | |
ab97e755 MB |
1664 | reentrant functions -- specifically networking-related ones -- being |
1665 | present but without prototypes available, check to see if BIND 8.1 (or | |
1666 | possibly other BIND 8 versions) is (or has been) installed. They install | |
1667 | header files such as netdb.h into places such as /usr/local/include (or | |
1668 | into another directory as specified at build/install time), at least | |
1669 | optionally. Remove them or put them in someplace that isn't in the C | |
1670 | preprocessor's header file include search path (determined by -I options | |
1671 | plus defaults, normally /usr/include). | |
84902520 | 1672 | |
d6baa268 JH |
1673 | =item #error "No DATAMODEL_NATIVE specified" |
1674 | ||
1675 | This is a common error when trying to build perl on Solaris 2.6 with a | |
1676 | gcc installation from Solaris 2.5 or 2.5.1. The Solaris header files | |
1677 | changed, so you need to update your gcc installation. You can either | |
1678 | rerun the fixincludes script from gcc or take the opportunity to | |
1679 | update your gcc installation. | |
1680 | ||
aa689395 | 1681 | =item Optimizer |
c3edaffb | 1682 | |
9d67150a | 1683 | If you can't compile successfully, try turning off your compiler's |
aa689395 | 1684 | optimizer. Edit config.sh and change the line |
9d67150a | 1685 | |
1686 | optimize='-O' | |
1687 | ||
bfb7748a | 1688 | to |
9d67150a | 1689 | |
1690 | optimize=' ' | |
1691 | ||
1692 | then propagate your changes with B<sh Configure -S> and rebuild | |
1693 | with B<make depend; make>. | |
1694 | ||
4bbc1586 | 1695 | =item Missing functions and Undefined symbols |
9d67150a | 1696 | |
4bbc1586 AD |
1697 | If the build of miniperl fails with a long list of missing functions or |
1698 | undefined symbols, check the libs variable in the config.sh file. It | |
1699 | should look something like | |
1700 | ||
1701 | libs='-lsocket -lnsl -ldl -lm -lc' | |
1702 | ||
1703 | The exact libraries will vary from system to system, but you typically | |
1704 | need to include at least the math library -lm. Normally, Configure | |
1705 | will suggest the correct defaults. If the libs variable is empty, you | |
1706 | need to start all over again. Run | |
1707 | ||
1708 | make distclean | |
1709 | ||
1710 | and start from the very beginning. This time, unless you are sure of | |
1711 | what you are doing, accept the default list of libraries suggested by | |
1712 | Configure. | |
1713 | ||
0ff780f4 MB |
1714 | If the libs variable is missing -lm, there is a chance that libm.so.1 |
1715 | is available, but the required (symbolic) link to libm.so is missing. | |
1716 | (same could be the case for other libraries like libcrypt.so). You | |
1717 | should check your installation for packages that create that link, and | |
1718 | if no package is installed that supplies that link or you cannot install | |
1719 | them, make the symbolic link yourself e.g.: | |
1720 | ||
c7121961 FC |
1721 | $ rpm -qf /usr/lib64/libm.so |
1722 | glibc-devel-2.15-22.17.1.x86_64 | |
1723 | $ ls -lgo /usr/lib64/libm.so | |
1724 | lrwxrwxrwx 1 16 Jan 7 2013 /usr/lib64/libm.so -> /lib64/libm.so.6 | |
0ff780f4 | 1725 | |
c7121961 | 1726 | or |
0ff780f4 | 1727 | |
c7121961 | 1728 | $ sudo ln -s /lib64/libm.so.6 /lib64/libm.so |
0ff780f4 | 1729 | |
4bbc1586 AD |
1730 | If the libs variable looks correct, you might have the |
1731 | L<"nm extraction"> problem discussed above. | |
1732 | ||
668cbedd | 1733 | If you still have missing routines or undefined symbols, you probably |
0ff780f4 MB |
1734 | need to add some library or other, make a symbolic link like described |
1735 | above, or you need to undefine some feature that Configure thought was | |
1736 | there but is defective or incomplete. If you used a hint file, see if | |
a3815e44 | 1737 | it has any relevant advice. You can also look through config.h |
0ff780f4 | 1738 | for likely suspects. |
8e07c86e | 1739 | |
1ec51d55 | 1740 | =item toke.c |
8e07c86e | 1741 | |
1ec51d55 CS |
1742 | Some compilers will not compile or optimize the larger files (such as |
1743 | toke.c) without some extra switches to use larger jump offsets or | |
1744 | allocate larger internal tables. You can customize the switches for | |
ab97e755 MB |
1745 | each file in cflags.SH. It's okay to insert rules for specific files |
1746 | into makefile since a default rule only takes effect in the absence of a | |
8e07c86e AD |
1747 | specific rule. |
1748 | ||
7f678428 | 1749 | =item Missing dbmclose |
8e07c86e | 1750 | |
c3edaffb | 1751 | SCO prior to 3.2.4 may be missing dbmclose(). An upgrade to 3.2.4 |
1752 | that includes libdbm.nfs (which includes dbmclose()) may be available. | |
8e07c86e | 1753 | |
1bb125e2 MB |
1754 | =item error: too few arguments to function 'dbmclose' |
1755 | ||
1756 | Building ODBM_File on some (Open)SUSE distributions might run into this | |
1757 | error, as the header file is broken. There are two ways to deal with this | |
1758 | ||
1759 | 1. Disable the use of ODBM_FILE | |
1760 | ||
f0c21bde | 1761 | sh Configure ... -Dnoextensions=ODBM_File |
1bb125e2 MB |
1762 | |
1763 | 2. Fix the header file, somewhat like this: | |
1764 | ||
1765 | --- a/usr/include/dbm.h 2010-03-24 08:54:59.000000000 +0100 | |
1766 | +++ b/usr/include/dbm.h 2010-03-24 08:55:15.000000000 +0100 | |
1767 | @@ -59,4 +59,4 @@ extern datum firstkey __P((void)); | |
1768 | ||
1769 | extern datum nextkey __P((datum key)); | |
1770 | ||
1771 | -extern int dbmclose __P((DBM *)); | |
1772 | +extern int dbmclose __P((void)); | |
1773 | ||
44666fef | 1774 | =item Warning (mostly harmless): No library found for -lsomething |
7f678428 | 1775 | |
1776 | If you see such a message during the building of an extension, but | |
1777 | the extension passes its tests anyway (see L<"make test"> below), | |
1778 | then don't worry about the warning message. The extension | |
1779 | Makefile.PL goes looking for various libraries needed on various | |
aa689395 | 1780 | systems; few systems will need all the possible libraries listed. |
74b7c41f | 1781 | Most users will see warnings for the ones they don't have. The |
44666fef | 1782 | phrase 'mostly harmless' is intended to reassure you that nothing |
74b7c41f | 1783 | unusual is happening, and the build process is continuing. |
7f678428 | 1784 | |
1785 | On the other hand, if you are building GDBM_File and you get the | |
1786 | message | |
1787 | ||
44666fef | 1788 | Warning (mostly harmless): No library found for -lgdbm |
7f678428 | 1789 | |
1790 | then it's likely you're going to run into trouble somewhere along | |
1791 | the line, since it's hard to see how you can use the GDBM_File | |
1792 | extension without the -lgdbm library. | |
1793 | ||
1794 | It is true that, in principle, Configure could have figured all of | |
1795 | this out, but Configure and the extension building process are not | |
1796 | quite that tightly coordinated. | |
1797 | ||
aa689395 | 1798 | =item sh: ar: not found |
1799 | ||
1800 | This is a message from your shell telling you that the command 'ar' | |
1801 | was not found. You need to check your PATH environment variable to | |
1802 | make sure that it includes the directory with the 'ar' command. This | |
1ec51d55 | 1803 | is a common problem on Solaris, where 'ar' is in the /usr/ccs/bin |
aa689395 | 1804 | directory. |
1805 | ||
1806 | =item db-recno failure on tests 51, 53 and 55 | |
1807 | ||
1808 | Old versions of the DB library (including the DB library which comes | |
1809 | with FreeBSD 2.1) had broken handling of recno databases with modified | |
1810 | bval settings. Upgrade your DB library or OS. | |
1811 | ||
6087ac44 JH |
1812 | =item Bad arg length for semctl, is XX, should be ZZZ |
1813 | ||
c935ba53 | 1814 | If you get this error message from the F<cpan/IPC-SysV/t/sem.t> test, your |
ab97e755 | 1815 | System V IPC may be broken. The XX typically is 20, and that is what ZZZ |
6087ac44 JH |
1816 | also should be. Consider upgrading your OS, or reconfiguring your OS |
1817 | to include the System V semaphores. | |
1818 | ||
c935ba53 | 1819 | =item cpan/IPC-SysV/t/sem........semget: No space left on device |
220f3621 GS |
1820 | |
1821 | Either your account or the whole system has run out of semaphores. Or | |
1822 | both. Either list the semaphores with "ipcs" and remove the unneeded | |
1823 | ones (which ones these are depends on your system and applications) | |
1824 | with "ipcrm -s SEMAPHORE_ID_HERE" or configure more semaphores to your | |
1825 | system. | |
1826 | ||
d6baa268 JH |
1827 | =item GNU binutils |
1828 | ||
1829 | If you mix GNU binutils (nm, ld, ar) with equivalent vendor-supplied | |
1830 | tools you may be in for some trouble. For example creating archives | |
1831 | with an old GNU 'ar' and then using a new current vendor-supplied 'ld' | |
1832 | may lead into linking problems. Either recompile your GNU binutils | |
1833 | under your current operating system release, or modify your PATH not | |
1834 | to include the GNU utils before running Configure, or specify the | |
1835 | vendor-supplied utilities explicitly to Configure, for example by | |
1836 | Configure -Dar=/bin/ar. | |
1837 | ||
16dc217a GS |
1838 | =item THIS PACKAGE SEEMS TO BE INCOMPLETE |
1839 | ||
1840 | The F<Configure> program has not been able to find all the files which | |
1841 | make up the complete Perl distribution. You may have a damaged source | |
1842 | archive file (in which case you may also have seen messages such as | |
1843 | C<gzip: stdin: unexpected end of file> and C<tar: Unexpected EOF on | |
1844 | archive file>), or you may have obtained a structurally-sound but | |
1845 | incomplete archive. In either case, try downloading again from the | |
1846 | official site named at the start of this document. If you do find | |
1847 | that any site is carrying a corrupted or incomplete source code | |
1848 | archive, please report it to the site's maintainer. | |
1849 | ||
16dc217a GS |
1850 | =item invalid token: ## |
1851 | ||
ce80d64e AD |
1852 | You are using a non-ANSI-compliant C compiler. To compile Perl, you |
1853 | need to use a compiler that supports ANSI C. If there is a README | |
1854 | file for your system, it may have further details on your compiler | |
1855 | options. | |
16dc217a | 1856 | |
1ec51d55 | 1857 | =item Miscellaneous |
8e07c86e | 1858 | |
7df75831 | 1859 | Some additional things that have been reported: |
8e07c86e AD |
1860 | |
1861 | Genix may need to use libc rather than libc_s, or #undef VARARGS. | |
1862 | ||
1863 | NCR Tower 32 (OS 2.01.01) may need -W2,-Sl,2000 and #undef MKDIR. | |
1864 | ||
668cbedd | 1865 | UTS may need one or more of -K or -g, and #undef LSTAT. |
8e07c86e | 1866 | |
c935ba53 | 1867 | FreeBSD can fail the F<cpan/IPC-SysV/t/sem.t> test if SysV IPC has not been |
5cda700b | 1868 | configured in the kernel. Perl tries to detect this, though, and |
ce80d64e | 1869 | you will get a message telling you what to do. |
6087ac44 | 1870 | |
6c8d78fb HS |
1871 | Building Perl on a system that has also BIND (headers and libraries) |
1872 | installed may run into troubles because BIND installs its own netdb.h | |
1873 | and socket.h, which may not agree with the operating system's ideas of | |
1874 | the same files. Similarly, including -lbind may conflict with libc's | |
1875 | view of the world. You may have to tweak -Dlocincpth and -Dloclibpth | |
1876 | to avoid the BIND. | |
1877 | ||
8e07c86e AD |
1878 | =back |
1879 | ||
58a21a9b JH |
1880 | =head2 Cross-compilation |
1881 | ||
e7a3c61b | 1882 | Perl can be cross-compiled. It is just not trivial, cross-compilation |
30bba555 | 1883 | rarely is. Perl is routinely cross-compiled for several platforms: as of |
ae2a00c5 | 1884 | June 2019, these include Android, Blackberry 10, |
79c32fc2 | 1885 | ARM Linux, and Solaris. Previous versions of |
30bba555 BF |
1886 | Perl also provided support for Open Zaurus, Symbian, and |
1887 | the IBM OS/400, but it's unknown if those ports are still functional. | |
ab97e755 MB |
1888 | These platforms are known as the B<target> platforms, while the systems |
1889 | where the compilation takes place are the B<host> platforms. | |
e7a3c61b JH |
1890 | |
1891 | What makes the situation difficult is that first of all, | |
1892 | cross-compilation environments vary significantly in how they are set | |
1893 | up and used, and secondly because the primary way of configuring Perl | |
1894 | (using the rather large Unix-tool-dependent Configure script) is not | |
1895 | awfully well suited for cross-compilation. However, starting from | |
30bba555 BF |
1896 | version 5.18.0, the Configure script also knows two ways of supporting |
1897 | cross-compilation, so please keep reading. | |
e7a3c61b JH |
1898 | |
1899 | See the following files for more information about compiling Perl for | |
1900 | the particular platforms: | |
1901 | ||
1902 | =over 4 | |
1903 | ||
30bba555 | 1904 | =item Android |
e7a3c61b | 1905 | |
ab97e755 MB |
1906 | L<"Cross-compilation" in README.android or |
1907 | perlandroid|perlandroid/Cross-compilation> | |
e7a3c61b | 1908 | |
30bba555 | 1909 | =item Blackberry |
e7a3c61b | 1910 | |
30bba555 | 1911 | L<"Cross-compilation" in README.qnx or perlqnx|perlqnx/Cross-compilation> |
e7a3c61b | 1912 | |
30bba555 | 1913 | =item Solaris |
e7a3c61b | 1914 | |
ab97e755 MB |
1915 | L<"CROSS-COMPILATION" in README.solaris or |
1916 | perlsolaris|perlsolaris/CROSS-COMPILATION> | |
30bba555 BF |
1917 | |
1918 | =item Linux | |
1919 | ||
1920 | This document; See below. | |
e7a3c61b JH |
1921 | |
1922 | =back | |
1923 | ||
1924 | Packaging and transferring either the core Perl modules or CPAN | |
1925 | modules to the target platform is also left up to the each | |
1926 | cross-compilation environment. Often the cross-compilation target | |
1927 | platforms are somewhat limited in diskspace: see the section | |
ef460fb9 | 1928 | L</Minimizing the Perl installation> to learn more of the minimal set |
e7a3c61b JH |
1929 | of files required for a functional Perl installation. |
1930 | ||
1931 | For some cross-compilation environments the Configure option | |
ef460fb9 | 1932 | C<-Dinstallprefix=...> might be handy, see L</Changing the installation |
e7a3c61b JH |
1933 | directory>. |
1934 | ||
30bba555 | 1935 | About the cross-compilation support of Configure: There's two forms. |
ab97e755 MB |
1936 | The more common one requires some way of transferring and running |
1937 | executables in the target system, such as an ssh connection; this is the | |
1938 | C<./Configure -Dusecrosscompile -Dtargethost=...> route. The second | |
1939 | method doesn't need access to the target system, but requires you to | |
a3815e44 | 1940 | provide a config.sh, and a canned Makefile; the rest of this section |
ab97e755 | 1941 | describes the former. |
e7a3c61b | 1942 | |
30bba555 | 1943 | This cross-compilation setup of Configure has successfully been used in |
ab97e755 MB |
1944 | a wide variety of setups, such as a 64-bit OS X host for an Android ARM |
1945 | target, or an amd64 Linux host targeting x86 Solaris, or even Windows. | |
e7a3c61b JH |
1946 | |
1947 | To run Configure in cross-compilation mode the basic switch that | |
30bba555 | 1948 | has to be used is C<-Dusecrosscompile>: |
58a21a9b JH |
1949 | |
1950 | sh ./Configure -des -Dusecrosscompile -D... | |
1951 | ||
1952 | This will make the cpp symbol USE_CROSS_COMPILE and the %Config | |
30bba555 | 1953 | symbol C<usecrosscompile> available. |
58a21a9b JH |
1954 | |
1955 | During the Configure and build, certain helper scripts will be created | |
1956 | into the Cross/ subdirectory. The scripts are used to execute a | |
1957 | cross-compiled executable, and to transfer files to and from the | |
1958 | target host. The execution scripts are named F<run-*> and the | |
1959 | transfer scripts F<to-*> and F<from-*>. The part after the dash is | |
1960 | the method to use for remote execution and transfer: by default the | |
1961 | methods are B<ssh> and B<scp>, thus making the scripts F<run-ssh>, | |
1962 | F<to-scp>, and F<from-scp>. | |
1963 | ||
1964 | To configure the scripts for a target host and a directory (in which | |
1965 | the execution will happen and which is to and from where the transfer | |
1966 | happens), supply Configure with | |
1967 | ||
1968 | -Dtargethost=so.me.ho.st -Dtargetdir=/tar/get/dir | |
1969 | ||
1970 | The targethost is what e.g. ssh will use as the hostname, the targetdir | |
93bc48fa JH |
1971 | must exist (the scripts won't create it), the targetdir defaults to /tmp. |
1972 | You can also specify a username to use for ssh/rsh logins | |
58a21a9b JH |
1973 | |
1974 | -Dtargetuser=luser | |
1975 | ||
30bba555 | 1976 | but in case you don't, "root" will be used. Similarly, you can specify |
ab97e755 MB |
1977 | a non-standard (i.e. not 22) port for the connection, if applicable, |
1978 | through | |
30bba555 BF |
1979 | |
1980 | -Dtargetport=2222 | |
58a21a9b | 1981 | |
30bba555 BF |
1982 | If the name of C<cc> has the usual GNU C semantics for cross |
1983 | compilers, that is, CPU-OS-gcc, the target architecture (C<targetarch>), | |
1984 | plus names of the C<ar>, C<nm>, and C<ranlib> will also be automatically | |
1985 | chosen to be CPU-OS-ar and so on. | |
1986 | (The C<ld> requires more thought and will be chosen later by Configure | |
1987 | as appropriate). This will also aid in guessing the proper | |
1988 | operating system name for the target, which has other repercussions, like | |
ab97e755 MB |
1989 | better defaults and possibly critical fixes for the platform. If |
1990 | Configure isn't guessing the OS name properly, you may need to either add | |
1991 | a hint file redirecting Configure's guess, or modify Configure to make | |
1992 | the correct choice. | |
30bba555 BF |
1993 | |
1994 | If your compiler doesn't follow that convention, you will also need to | |
1995 | specify which target environment to use, as well as C<ar> and friends: | |
58a21a9b JH |
1996 | |
1997 | -Dtargetarch=arm-linux | |
30bba555 BF |
1998 | -Dcc=mycrossgcc |
1999 | -Dar=... | |
2000 | ||
2001 | Additionally, a cross-compilation toolchain will usually install it's own | |
ab97e755 | 2002 | logical system root somewhere -- that is, it'll create a directory |
a95b3d6a KW |
2003 | somewhere which includes subdirectories like C<'include'> or C<'lib'>. For |
2004 | example, you may end up with F</skiff/local/arm-linux>, where | |
2005 | F</skiff/local/arm-linux/bin> holds the binaries for cross-compilation, | |
2006 | F</skiff/local/arm-linux/include> has the headers, and | |
2007 | F</skiff/local/arm-linux/lib> has the library files. | |
30bba555 BF |
2008 | If this is the case, and you are using a compiler that understands |
2009 | C<--sysroot>, like gcc or clang, you'll want to specify the | |
2010 | C<-Dsysroot> option for Configure: | |
2011 | ||
2012 | -Dsysroot=/skiff/local/arm-linux | |
2013 | ||
2014 | However, if your don't have a suitable directory to pass to C<-Dsysroot>, | |
2015 | you will also need to specify which target environment to use: | |
2016 | ||
58a21a9b JH |
2017 | -Dusrinc=/skiff/local/arm-linux/include |
2018 | -Dincpth=/skiff/local/arm-linux/include | |
2019 | -Dlibpth=/skiff/local/arm-linux/lib | |
2020 | ||
58a21a9b JH |
2021 | In addition to the default execution/transfer methods you can also |
2022 | choose B<rsh> for execution, and B<rcp> or B<cp> for transfer, | |
2023 | for example: | |
2024 | ||
2025 | -Dtargetrun=rsh -Dtargetto=rcp -Dtargetfrom=cp | |
2026 | ||
2027 | Putting it all together: | |
2028 | ||
2029 | sh ./Configure -des -Dusecrosscompile \ | |
93bc48fa | 2030 | -Dtargethost=so.me.ho.st \ |
30bba555 | 2031 | -Dtargetdir=/tar/get/dir \ |
58a21a9b JH |
2032 | -Dtargetuser=root \ |
2033 | -Dtargetarch=arm-linux \ | |
2034 | -Dcc=arm-linux-gcc \ | |
30bba555 | 2035 | -Dsysroot=/skiff/local/arm-linux \ |
58a21a9b JH |
2036 | -D... |
2037 | ||
e7a3c61b | 2038 | or if you are happy with the defaults: |
93bc48fa JH |
2039 | |
2040 | sh ./Configure -des -Dusecrosscompile \ | |
2041 | -Dtargethost=so.me.ho.st \ | |
2042 | -Dcc=arm-linux-gcc \ | |
2043 | -D... | |
2044 | ||
e7a3c61b JH |
2045 | Another example where the cross-compiler has been installed under |
2046 | F</usr/local/arm/2.95.5>: | |
2047 | ||
2048 | sh ./Configure -des -Dusecrosscompile \ | |
2049 | -Dtargethost=so.me.ho.st \ | |
2050 | -Dcc=/usr/local/arm/2.95.5/bin/arm-linux-gcc \ | |
30bba555 BF |
2051 | -Dsysroot=/usr/local/arm/2.95.5 |
2052 | ||
2053 | There is also a C<targetenv> option for Configure which can be used | |
2054 | to modify the environment of the target just before testing begins | |
2055 | during 'make test'. For example, if the target system has a nonstandard | |
2056 | /tmp location, you could do this: | |
2057 | ||
2058 | -Dtargetenv="export TMPDIR=/other/tmp;" | |
2059 | ||
ab97e755 MB |
2060 | If you are planning on cross-compiling to several platforms, or some |
2061 | other thing that would involve running Configure several times, there are | |
2062 | two options that can be used to speed things up considerably. | |
30bba555 BF |
2063 | As a bit of background, when you |
2064 | call Configure with C<-Dusecrosscompile>, it begins by actually partially | |
2065 | building a miniperl on the host machine, as well as the generate_uudmap | |
2066 | binary, and we end up using that during the build. | |
ab97e755 MB |
2067 | So instead of building that new perl every single time, you can build it |
2068 | just once in a separate directory, and then pass the resulting binaries | |
2069 | to Configure like this: | |
30bba555 BF |
2070 | |
2071 | -Dhostperl=/path/to/second/build/dir/miniperl | |
2072 | -Dhostgenerate=/path/to/second/build/dir/generate_uudmap | |
2073 | ||
2074 | Much less commonly, if you are cross-compiling from an ASCII host to an | |
2075 | EBCDIC target, or vise versa, you'll have to pass C<-Uhostgenerate> to | |
2076 | Configure, to signify that you want to build a generate_uudmap binary | |
2077 | that, during make, will be run on the target system. | |
e7a3c61b | 2078 | |
8e07c86e AD |
2079 | =head1 make test |
2080 | ||
d6baa268 JH |
2081 | This will run the regression tests on the perl you just made. If |
2082 | 'make test' doesn't say "All tests successful" then something went | |
36bded94 | 2083 | wrong. |
84902520 | 2084 | |
84902520 | 2085 | Note that you can't run the tests in background if this disables |
fb73857a | 2086 | opening of /dev/tty. You can use 'make test-notty' in that case but |
2087 | a few tty tests will be skipped. | |
c3edaffb | 2088 | |
c4f23d77 AD |
2089 | =head2 What if make test doesn't work? |
2090 | ||
1ec51d55 | 2091 | If make test bombs out, just cd to the t directory and run ./TEST |
36bded94 | 2092 | by hand to see if it makes any difference. |
8e07c86e | 2093 | |
36bded94 AD |
2094 | One way to get more detailed information about failed tests and |
2095 | individual subtests is to run the harness from the t directory: | |
aa689395 | 2096 | |
785aa5e3 | 2097 | cd t ; ./perl harness <list of tests> |
aa689395 | 2098 | |
fb73857a | 2099 | (this assumes that most basic tests succeed, since harness uses |
785aa5e3 RGS |
2100 | complicated constructs). If no list of tests is provided, harness |
2101 | will run all tests. | |
10c7e831 | 2102 | |
36bded94 AD |
2103 | If individual tests fail, you can often run them by hand (from the main |
2104 | perl directory), e.g., | |
2105 | ||
524a2f33 | 2106 | ./perl -I. -MTestInit t/op/groups.t |
36bded94 | 2107 | |
fb73857a | 2108 | You should also read the individual tests to see if there are any helpful |
10c7e831 JH |
2109 | comments that apply to your system. You may also need to setup your |
2110 | shared library path if you get errors like: | |
2111 | ||
2112 | /sbin/loader: Fatal Error: cannot map libperl.so | |
2113 | ||
36bded94 AD |
2114 | The file t/README in the t subdirectory contains more information about |
2115 | running and modifying tests. | |
2116 | ||
10c7e831 | 2117 | See L</"Building a shared Perl library"> earlier in this document. |
c3edaffb | 2118 | |
c4f23d77 AD |
2119 | =over 4 |
2120 | ||
2121 | =item locale | |
2122 | ||
1ec51d55 | 2123 | Note: One possible reason for errors is that some external programs |
c07a80fd | 2124 | may be broken due to the combination of your environment and the way |
785aa5e3 | 2125 | 'make test' exercises them. For example, this may happen if you have |
1ec51d55 CS |
2126 | one or more of these environment variables set: LC_ALL LC_CTYPE |
2127 | LC_COLLATE LANG. In some versions of UNIX, the non-English locales | |
e57fd563 | 2128 | are known to cause programs to exhibit mysterious errors. |
2129 | ||
2130 | If you have any of the above environment variables set, please try | |
aa689395 | 2131 | |
2132 | setenv LC_ALL C | |
2133 | ||
2134 | (for C shell) or | |
2135 | ||
2136 | LC_ALL=C;export LC_ALL | |
2137 | ||
1ec51d55 CS |
2138 | for Bourne or Korn shell) from the command line and then retry |
2139 | make test. If the tests then succeed, you may have a broken program that | |
aa689395 | 2140 | is confusing the testing. Please run the troublesome test by hand as |
e57fd563 | 2141 | shown above and see whether you can locate the program. Look for |
1ec51d55 CS |
2142 | things like: exec, `backquoted command`, system, open("|...") or |
2143 | open("...|"). All these mean that Perl is trying to run some | |
e57fd563 | 2144 | external program. |
eed2e782 | 2145 | |
0740bb5b AD |
2146 | =item Timing problems |
2147 | ||
c29923ff JH |
2148 | Several tests in the test suite check timing functions, such as |
2149 | sleep(), and see if they return in a reasonable amount of time. | |
9341413f JH |
2150 | If your system is quite busy and doesn't respond quickly enough, |
2151 | these tests might fail. If possible, try running the tests again | |
2152 | with the system under a lighter load. These timing-sensitive | |
2153 | and load-sensitive tests include F<t/op/alarm.t>, | |
d0b0e707 TH |
2154 | F<dist/Time-HiRes/t/alarm.t>, F<dist/Time-HiRes/t/clock.t>, |
2155 | F<dist/Time-HiRes/t/itimer.t>, F<dist/Time-HiRes/t/usleep.t>, | |
1543af16 | 2156 | F<dist/threads-shared/t/waithires.t>, |
c935ba53 | 2157 | F<dist/threads-shared/t/stress.t>, F<lib/Benchmark.t>, |
9341413f | 2158 | F<lib/Memoize/t/expmod_t.t>, and F<lib/Memoize/t/speed.t>. |
0740bb5b | 2159 | |
f89caa8d RGS |
2160 | You might also experience some failures in F<t/op/stat.t> if you build |
2161 | perl on an NFS filesystem, if the remote clock and the system clock are | |
2162 | different. | |
2163 | ||
c4f23d77 AD |
2164 | =item Out of memory |
2165 | ||
2166 | On some systems, particularly those with smaller amounts of RAM, some | |
2167 | of the tests in t/op/pat.t may fail with an "Out of memory" message. | |
7970f296 GS |
2168 | For example, on my SparcStation IPC with 12 MB of RAM, in perl5.5.670, |
2169 | test 85 will fail if run under either t/TEST or t/harness. | |
c4f23d77 AD |
2170 | |
2171 | Try stopping other jobs on the system and then running the test by itself: | |
2172 | ||
524a2f33 | 2173 | ./perl -I. -MTestInit t/op/pat.t |
c4f23d77 AD |
2174 | |
2175 | to see if you have any better luck. If your perl still fails this | |
2176 | test, it does not necessarily mean you have a broken perl. This test | |
2177 | tries to exercise the regular expression subsystem quite thoroughly, | |
2178 | and may well be far more demanding than your normal usage. | |
2179 | ||
a55bb48b AD |
2180 | =item libgcc_s.so.1: cannot open shared object file |
2181 | ||
2182 | This message has been reported on gcc-3.2.3 and earlier installed with | |
2183 | a non-standard prefix. Setting the LD_LIBRARY_PATH environment variable | |
2184 | (or equivalent) to include gcc's lib/ directory with the libgcc_s.so.1 | |
2185 | shared library should fix the problem. | |
2186 | ||
4f76e5ba AD |
2187 | =item Failures from lib/File/Temp/t/security saying "system possibly insecure" |
2188 | ||
2189 | First, such warnings are not necessarily serious or indicative of a | |
2190 | real security threat. That being said, they bear investigating. | |
2191 | ||
2192 | Note that each of the tests is run twice. The first time is in the | |
2193 | directory returned by File::Spec->tmpdir() (often /tmp on Unix | |
2194 | systems), and the second time in the directory from which the test was | |
2195 | run (usually the 't' directory, if the test was run as part of 'make | |
2196 | test'). | |
2197 | ||
2198 | The tests may fail for the following reasons: | |
2199 | ||
2200 | (1) If the directory the tests are being run in is owned by somebody | |
2201 | other than the user running the tests, or by root (uid 0). | |
2202 | ||
2203 | This failure can happen if the Perl source code distribution is | |
668cbedd | 2204 | unpacked in such a way that the user IDs in the distribution package |
4f76e5ba AD |
2205 | are used as-is. Some tar programs do this. |
2206 | ||
2207 | (2) If the directory the tests are being run in is writable by group or | |
2208 | by others, and there is no sticky bit set for the directory. (With | |
2209 | UNIX/POSIX semantics, write access to a directory means the right to | |
2210 | add or remove files in that directory. The 'sticky bit' is a feature | |
2211 | used in some UNIXes to give extra protection to files: if the bit is | |
2212 | set for a directory, no one but the owner (or root) can remove that | |
2213 | file even if the permissions would otherwise allow file removal by | |
2214 | others.) | |
2215 | ||
2216 | This failure may or may not be a real problem: it depends on the | |
2217 | permissions policy used on this particular system. This failure can | |
2218 | also happen if the system either doesn't support the sticky bit (this | |
2219 | is the case with many non-UNIX platforms: in principle File::Temp | |
2220 | should know about these platforms and skip the tests), or if the system | |
2221 | supports the sticky bit but for some reason or reasons it is not being | |
2222 | used. This is, for example, the case with HP-UX: as of HP-UX release | |
2223 | 11.00, the sticky bit is very much supported, but HP-UX doesn't use it | |
2224 | on its /tmp directory as shipped. Also, as with the permissions, some | |
2225 | local policy might dictate that the stickiness is not used. | |
781948c1 | 2226 | |
b2b23189 JH |
2227 | (3) If the system supports the POSIX 'chown giveaway' feature and if |
2228 | any of the parent directories of the temporary file back to the root | |
2229 | directory are 'unsafe', using the definitions given above in (1) and | |
4f76e5ba AD |
2230 | (2). For Unix systems, this is usually not an issue if you are |
2231 | building on a local disk. See the documentation for the File::Temp | |
2232 | module for more information about 'chown giveaway'. | |
781948c1 JH |
2233 | |
2234 | See the documentation for the File::Temp module for more information | |
4f76e5ba | 2235 | about the various security aspects of temporary files. |
781948c1 | 2236 | |
c4f23d77 AD |
2237 | =back |
2238 | ||
5ee651a9 | 2239 | The core distribution can now run its regression tests in parallel on |
ab97e755 MB |
2240 | Unix-like platforms. Instead of running C<make test>, set C<TEST_JOBS> |
2241 | in your environment to the number of tests to run in parallel, and run | |
5ee651a9 NC |
2242 | C<make test_harness>. On a Bourne-like shell, this can be done as |
2243 | ||
2244 | TEST_JOBS=3 make test_harness # Run 3 tests in parallel | |
2245 | ||
ab97e755 MB |
2246 | An environment variable is used, rather than parallel make itself, |
2247 | because L<TAP::Harness> needs to be able to schedule individual | |
2248 | non-conflicting test scripts itself, and there is no standard interface | |
2249 | to C<make> utilities to interact with their job schedulers. | |
5ee651a9 | 2250 | |
8e07c86e AD |
2251 | =head1 make install |
2252 | ||
2253 | This will put perl into the public directory you specified to | |
ab97e755 MB |
2254 | Configure; by default this is /usr/local/bin. It will also try to put |
2255 | the man pages in a reasonable place. It will not nroff the man pages, | |
2256 | however. You may need to be root to run B<make install>. If you are not | |
2257 | root, you must still have permission to install into the directories | |
ce80d64e AD |
2258 | in question and you should ignore any messages about chown not working. |
2259 | ||
19f4563d | 2260 | If "make install" just says "'install' is up to date" or something |
ce80d64e AD |
2261 | similar, you may be on a case-insensitive filesystems such as Mac's HFS+, |
2262 | and you should say "make install-all". (This confusion is brought to you | |
2263 | by the Perl distribution having a file called INSTALL.) | |
8e07c86e | 2264 | |
dd64f1c3 AD |
2265 | =head2 Installing perl under different names |
2266 | ||
2267 | If you want to install perl under a name other than "perl" (for example, | |
2268 | when installing perl with special features enabled, such as debugging), | |
2269 | indicate the alternate name on the "make install" line, such as: | |
2270 | ||
2271 | make install PERLNAME=myperl | |
2272 | ||
beb13193 | 2273 | You can separately change the base used for versioned names (like |
be8498a1 | 2274 | "perl5.8.9") by setting PERLNAME_VERBASE, like |
beb13193 RS |
2275 | |
2276 | make install PERLNAME=perl5 PERLNAME_VERBASE=perl | |
2277 | ||
ab97e755 MB |
2278 | This can be useful if you have to install perl as "perl5" (e.g. to avoid |
2279 | conflicts with an ancient version in /usr/bin supplied by your vendor). | |
be8498a1 | 2280 | Without this the versioned binary would be called "perl55.8.8". |
beb13193 | 2281 | |
ce80d64e AD |
2282 | =head2 Installing perl under a different directory |
2283 | ||
2284 | You can install perl under a different destination directory by using | |
2285 | the DESTDIR variable during C<make install>, with a command like | |
2286 | ||
2287 | make install DESTDIR=/tmp/perl5 | |
2288 | ||
2289 | DESTDIR is automatically prepended to all the installation paths. See | |
7df75831 | 2290 | the example in L<"DESTDIR"> above. |
ce80d64e | 2291 | |
dd64f1c3 AD |
2292 | =head2 Installed files |
2293 | ||
8e07c86e AD |
2294 | If you want to see exactly what will happen without installing |
2295 | anything, you can run | |
4633a7c4 | 2296 | |
8e07c86e AD |
2297 | ./perl installperl -n |
2298 | ./perl installman -n | |
2299 | ||
1ec51d55 | 2300 | make install will install the following: |
8e07c86e | 2301 | |
d56c5707 JH |
2302 | binaries |
2303 | ||
8e07c86e | 2304 | perl, |
be8498a1 | 2305 | perl5.n.n where 5.n.n is the current release number. This |
8e07c86e | 2306 | will be a link to perl. |
d56c5707 JH |
2307 | |
2308 | scripts | |
2309 | ||
979b4168 KW |
2310 | cppstdin This is used by the deprecated switch perl -P, |
2311 | if your cc -E can't read from stdin. | |
979b4168 KW |
2312 | corelist Shows versions of modules that come with |
2313 | different | |
668cbedd KW |
2314 | versions of perl. |
2315 | cpan The CPAN shell. | |
668cbedd | 2316 | enc2xs Encoding module generator. |
979b4168 KW |
2317 | h2ph Extract constants and simple macros from C |
2318 | headers. | |
8e07c86e | 2319 | h2xs Converts C .h header files to Perl extensions. |
73d6d1b0 RGS |
2320 | instmodsh A shell to examine installed modules. |
2321 | libnetcfg Configure libnet. | |
24b3df7f | 2322 | perlbug Tool to report bugs in Perl. |
8e07c86e | 2323 | perldoc Tool to read perl's pod documentation. |
668cbedd | 2324 | perlivp Perl Installation Verification Procedure. |
73d6d1b0 | 2325 | piconv A Perl implementation of the encoding conversion |
668cbedd KW |
2326 | utility iconv. |
2327 | pl2pm Convert Perl 4 .pl files to Perl 5 .pm modules. | |
8e07c86e | 2328 | pod2html, Converters from perl's pod documentation format |
d56c5707 JH |
2329 | pod2man, |
2330 | pod2text, | |
d56c5707 | 2331 | pod2usage |
668cbedd KW |
2332 | podchecker POD syntax checker. |
2333 | podselect Prints sections of POD documentation. | |
2334 | prove A command-line tool for running tests. | |
2335 | psed A Perl implementation of sed. | |
2336 | ptar A Perl implementation of tar. | |
2337 | ptardiff A diff for tar archives. | |
2338 | ptargrep A grep for tar archives. | |
668cbedd KW |
2339 | shasum A tool to print or check SHA checksums. |
2340 | splain Describe Perl warnings and errors. | |
2341 | xsubpp Compiler to convert Perl XS code into C code. | |
979b4168 | 2342 | zipdetails display the internal structure of zip files |
8e07c86e | 2343 | |
d56c5707 JH |
2344 | library files |
2345 | ||
2346 | in $privlib and $archlib specified to | |
8e07c86e | 2347 | Configure, usually under /usr/local/lib/perl5/. |
d56c5707 JH |
2348 | |
2349 | documentation | |
2350 | ||
d6baa268 JH |
2351 | man pages in $man1dir, usually /usr/local/man/man1. |
2352 | module man | |
2353 | pages in $man3dir, usually /usr/local/man/man3. | |
8e07c86e AD |
2354 | pod/*.pod in $privlib/pod/. |
2355 | ||
33cceb07 | 2356 | installperl will also create the directories listed above |
d6baa268 | 2357 | in L<"Installation Directories">. |
4633a7c4 | 2358 | |
d56c5707 | 2359 | Perl's *.h header files and the libperl library are also installed |
d6baa268 | 2360 | under $archlib so that any user may later build new modules, run the |
56c6f531 JH |
2361 | optional Perl compiler, or embed the perl interpreter into another |
2362 | program even if the Perl source is no longer available. | |
8e07c86e | 2363 | |
6baaafe3 | 2364 | =head2 Installing with a version-specific suffix |
33cceb07 | 2365 | |
6baaafe3 DC |
2366 | Sometimes you only want to install the perl distribution with a |
2367 | version-specific suffix. For example, you may wish to install a newer | |
2368 | version of perl alongside an already installed production version. | |
d56c5707 JH |
2369 | To only install the version-specific parts of the perl installation, run |
2370 | ||
2371 | Configure -Dversiononly | |
2372 | ||
2373 | or answer 'y' to the appropriate Configure prompt. Alternatively, | |
2374 | you can just manually run | |
2375 | ||
2376 | ./perl installperl -v | |
2377 | ||
2378 | and skip installman altogether. | |
33cceb07 | 2379 | |
d56c5707 JH |
2380 | See also L<"Maintaining completely separate versions"> for another |
2381 | approach. | |
2382 | ||
f4ce0e6d RGS |
2383 | =head1 cd /usr/include; h2ph *.h sys/*.h |
2384 | ||
2385 | Some perl scripts need to be able to obtain information from the | |
2386 | system header files. This command will convert the most commonly used | |
2387 | header files in /usr/include into files that can be easily interpreted | |
2388 | by perl. These files will be placed in the architecture-dependent | |
2389 | library ($archlib) directory you specified to Configure. | |
2390 | ||
668cbedd | 2391 | Note: Due to differences in the C and perl languages, the conversion |
f4ce0e6d RGS |
2392 | of the header files is not perfect. You will probably have to |
2393 | hand-edit some of the converted files to get them to parse correctly. | |
2394 | For example, h2ph breaks spectacularly on type casting and certain | |
2395 | structures. | |
2396 | ||
2397 | =head1 installhtml --help | |
2398 | ||
2399 | Some sites may wish to make perl documentation available in HTML | |
2400 | format. The installhtml utility can be used to convert pod | |
2401 | documentation into linked HTML files and install them. | |
2402 | ||
2403 | Currently, the supplied ./installhtml script does not make use of the | |
2404 | html Configure variables. This should be fixed in a future release. | |
2405 | ||
2406 | The following command-line is an example of one used to convert | |
2407 | perl documentation: | |
2408 | ||
2409 | ./installhtml \ | |
2410 | --podroot=. \ | |
2411 | --podpath=lib:ext:pod:vms \ | |
2412 | --recurse \ | |
2413 | --htmldir=/perl/nmanual \ | |
2414 | --htmlroot=/perl/nmanual \ | |
2415 | --splithead=pod/perlipc \ | |
2416 | --splititem=pod/perlfunc \ | |
f4ce0e6d RGS |
2417 | --verbose |
2418 | ||
2419 | See the documentation in installhtml for more details. It can take | |
2420 | many minutes to execute a large installation and you should expect to | |
2421 | see warnings like "no title", "unexpected directive" and "cannot | |
2422 | resolve" as the files are processed. We are aware of these problems | |
2423 | (and would welcome patches for them). | |
2424 | ||
2425 | You may find it helpful to run installhtml twice. That should reduce | |
2426 | the number of "cannot resolve" warnings. | |
2427 | ||
2428 | =head1 cd pod && make tex && (process the latex files) | |
2429 | ||
2430 | Some sites may also wish to make the documentation in the pod/ directory | |
2431 | available in TeX format. Type | |
2432 | ||
2433 | (cd pod && make tex && <process the latex files>) | |
2434 | ||
2435 | =head1 Starting all over again | |
2436 | ||
668cbedd | 2437 | If you wish to rebuild perl from the same build directory, you should |
f4ce0e6d RGS |
2438 | clean it out with the command |
2439 | ||
2440 | make distclean | |
2441 | ||
2442 | or | |
2443 | ||
2444 | make realclean | |
2445 | ||
2446 | The only difference between the two is that make distclean also removes | |
dd8235d9 | 2447 | your old config.sh and Policy.sh files. (A plain 'make clean' is now |
54f6f377 | 2448 | equivalent to 'make realclean'.) |
f4ce0e6d RGS |
2449 | |
2450 | If you are upgrading from a previous version of perl, or if you | |
2451 | change systems or compilers or make other significant changes, or if | |
668cbedd | 2452 | you are experiencing difficulties building perl, you should not reuse |
f4ce0e6d RGS |
2453 | your old config.sh. |
2454 | ||
2455 | If your reason to reuse your old config.sh is to save your particular | |
2456 | installation choices, then you can probably achieve the same effect by | |
2457 | using the Policy.sh file. See the section on L<"Site-wide Policy | |
2458 | settings"> above. | |
2459 | ||
ff52061e RGS |
2460 | =head1 Reporting Problems |
2461 | ||
8166b4e0 DB |
2462 | Please report problems to the GitHub issue tracker at |
2463 | https://github.com/Perl/perl5/issues, which will ask for the | |
2464 | appropriate summary configuration information about your perl, which | |
2465 | may help us track down problems far more quickly. But first you should | |
2466 | read the advice in this file, carefully re-read the error message and | |
2467 | check the relevant manual pages on your system, as these may help you | |
2468 | find an immediate solution. Once you've exhausted the documentation, | |
2469 | please report bugs to us using the GitHub tracker. | |
2470 | ||
2471 | The summary configuration information can be printed with C<perl -V>. | |
2472 | If the install fails, or you want to report problems with C<make test> | |
2473 | without installing perl, then you can run it by hand from this source | |
2474 | directory with C<./perl -V>. | |
2475 | ||
2476 | If the build fails too early to run perl, then please | |
2477 | B<run> the C<./myconfig> shell script, and include its output along | |
2478 | with an accurate description of your problem. | |
ff52061e RGS |
2479 | |
2480 | If Configure itself fails, and does not generate a config.sh file | |
8166b4e0 | 2481 | (needed to run C<./myconfig>), then please open an issue with the |
ff52061e | 2482 | description of how Configure fails along with details of your system |
8166b4e0 | 2483 | -- for example the output from running C<uname -a>. |
ff52061e RGS |
2484 | |
2485 | Please try to make your message brief but clear. Brief, clear bug | |
2486 | reports tend to get answered more quickly. Please don't worry if your | |
668cbedd | 2487 | written English is not great -- what matters is how well you describe |
ff52061e RGS |
2488 | the important technical details of the problem you have encountered, |
2489 | not whether your grammar and spelling is flawless. | |
2490 | ||
2491 | Trim out unnecessary information. Do not include large files (such as | |
2492 | config.sh or a complete Configure or make log) unless absolutely | |
2493 | necessary. Do not include a complete transcript of your build | |
2494 | session. Just include the failing commands, the relevant error | |
2495 | messages, and whatever preceding commands are necessary to give the | |
8166b4e0 | 2496 | appropriate context. |
ff52061e | 2497 | |
87c118b9 | 2498 | If the bug you are reporting has security implications which make it |
8166b4e0 | 2499 | inappropriate to send to a public issue tracker, then see |
87c118b9 DM |
2500 | L<perlsec/SECURITY VULNERABILITY CONTACT INFORMATION> |
2501 | for details of how to report the issue. | |
5acb7768 | 2502 | |
ff52061e RGS |
2503 | If you are unsure what makes a good bug report please read "How to |
2504 | report Bugs Effectively" by Simon Tatham: | |
f6521f7c | 2505 | L<https://www.chiark.greenend.org.uk/~sgtatham/bugs.html> |
ff52061e | 2506 | |
7df75831 | 2507 | =head1 Coexistence with earlier versions of perl 5 |
4633a7c4 | 2508 | |
5585d096 | 2509 | Perl 5.35.10 is not binary compatible with earlier versions of Perl. |
cc65bb49 | 2510 | In other words, you will have to recompile your XS modules. |
14eee2f1 | 2511 | |
725c980e SH |
2512 | In general, you can usually safely upgrade from one stable version of Perl |
2513 | (e.g. 5.30.0) to another similar minor version (e.g. 5.30.1) without | |
33cceb07 | 2514 | re-compiling all of your extensions. You can also safely leave the old |
ab97e755 MB |
2515 | version around in case the new version causes you problems for some |
2516 | reason. | |
693762b4 | 2517 | |
be8498a1 RGS |
2518 | Usually, most extensions will probably not need to be recompiled to be |
2519 | used with a newer version of Perl. Here is how it is supposed to work. | |
ce80d64e | 2520 | (These examples assume you accept all the Configure defaults.) |
693762b4 | 2521 | |
33cceb07 RGS |
2522 | Suppose you already have version 5.8.7 installed. The directories |
2523 | searched by 5.8.7 are typically like: | |
d6baa268 | 2524 | |
33cceb07 RGS |
2525 | /usr/local/lib/perl5/5.8.7/$archname |
2526 | /usr/local/lib/perl5/5.8.7 | |
2527 | /usr/local/lib/perl5/site_perl/5.8.7/$archname | |
2528 | /usr/local/lib/perl5/site_perl/5.8.7 | |
d6baa268 | 2529 | |
33cceb07 RGS |
2530 | Now, suppose you install version 5.8.8. The directories |
2531 | searched by version 5.8.8 will be: | |
d6baa268 | 2532 | |
33cceb07 RGS |
2533 | /usr/local/lib/perl5/5.8.8/$archname |
2534 | /usr/local/lib/perl5/5.8.8 | |
2535 | /usr/local/lib/perl5/site_perl/5.8.8/$archname | |
2536 | /usr/local/lib/perl5/site_perl/5.8.8 | |
d6baa268 | 2537 | |
33cceb07 RGS |
2538 | /usr/local/lib/perl5/site_perl/5.8.7/$archname |
2539 | /usr/local/lib/perl5/site_perl/5.8.7 | |
c42e3e15 | 2540 | /usr/local/lib/perl5/site_perl/ |
bfb7748a | 2541 | |
c42e3e15 | 2542 | Notice the last three entries -- Perl understands the default structure |
d6baa268 | 2543 | of the $sitelib directories and will look back in older, compatible |
33cceb07 RGS |
2544 | directories. This way, modules installed under 5.8.7 will continue |
2545 | to be usable by 5.8.7 but will also accessible to 5.8.8. Further, | |
d6baa268 | 2546 | suppose that you upgrade a module to one which requires features |
33cceb07 RGS |
2547 | present only in 5.8.8. That new module will get installed into |
2548 | /usr/local/lib/perl5/site_perl/5.8.8 and will be available to 5.8.8, | |
2549 | but will not interfere with the 5.8.7 version. | |
bfb7748a | 2550 | |
c42e3e15 | 2551 | The last entry, /usr/local/lib/perl5/site_perl/, is there so that |
fe23a901 | 2552 | 5.6.0 and above will look for 5.004-era pure perl modules. |
d6baa268 | 2553 | |
33cceb07 RGS |
2554 | Lastly, suppose you now install 5.10.0, which is not binary compatible |
2555 | with 5.8.x. The directories searched by 5.10.0 (if you don't change the | |
fe23a901 RF |
2556 | Configure defaults) will be: |
2557 | ||
33cceb07 RGS |
2558 | /usr/local/lib/perl5/5.10.0/$archname |
2559 | /usr/local/lib/perl5/5.10.0 | |
2560 | /usr/local/lib/perl5/site_perl/5.10.0/$archname | |
2561 | /usr/local/lib/perl5/site_perl/5.10.0 | |
d6baa268 | 2562 | |
33cceb07 | 2563 | /usr/local/lib/perl5/site_perl/5.8.8 |
d6baa268 | 2564 | |
33cceb07 | 2565 | /usr/local/lib/perl5/site_perl/5.8.7 |
fe23a901 | 2566 | |
d6baa268 | 2567 | /usr/local/lib/perl5/site_perl/ |
bfb7748a | 2568 | |
cc65bb49 AD |
2569 | Note that the earlier $archname entries are now gone, but pure perl |
2570 | modules from earlier versions will still be found. | |
2571 | ||
0a08c020 GS |
2572 | This way, you can choose to share compatible extensions, but also upgrade |
2573 | to a newer version of an extension that may be incompatible with earlier | |
2574 | versions, without breaking the earlier versions' installations. | |
693762b4 AD |
2575 | |
2576 | =head2 Maintaining completely separate versions | |
4633a7c4 | 2577 | |
1ec51d55 | 2578 | Many users prefer to keep all versions of perl in completely |
d6baa268 | 2579 | separate directories. This guarantees that an update to one version |
0a08c020 GS |
2580 | won't interfere with another version. (The defaults guarantee this for |
2581 | libraries after 5.6.0, but not for executables. TODO?) One convenient | |
2582 | way to do this is by using a separate prefix for each version, such as | |
d52d4e46 | 2583 | |
5585d096 | 2584 | sh Configure -Dprefix=/opt/perl5.35.10 |
d52d4e46 | 2585 | |
5585d096 | 2586 | and adding /opt/perl5.35.10/bin to the shell PATH variable. Such users |
d52d4e46 | 2587 | may also wish to add a symbolic link /usr/local/bin/perl so that |
2588 | scripts can still start with #!/usr/local/bin/perl. | |
2589 | ||
693762b4 | 2590 | Others might share a common directory for maintenance sub-versions |
33cceb07 | 2591 | (e.g. 5.10 for all 5.10.x versions), but change directory with |
693762b4 AD |
2592 | each major version. |
2593 | ||
6877a1cf AD |
2594 | If you are installing a development subversion, you probably ought to |
2595 | seriously consider using a separate directory, since development | |
2596 | subversions may not have all the compatibility wrinkles ironed out | |
2597 | yet. | |
2598 | ||
5585d096 | 2599 | =head2 Upgrading from 5.35.9 or earlier |
693762b4 | 2600 | |
5585d096 | 2601 | B<Perl 5.35.10 may not be binary compatible with Perl 5.35.9 or |
4683a5d7 | 2602 | earlier Perl releases.> Perl modules having binary parts |
e655887d | 2603 | (meaning that a C compiler is used) will have to be recompiled to be |
5585d096 RB |
2604 | used with 5.35.10. If you find you do need to rebuild an extension with |
2605 | 5.35.10, you may safely do so without disturbing the older | |
7df75831 | 2606 | installations. (See L<"Coexistence with earlier versions of perl 5"> |
e655887d | 2607 | above.) |
c42e3e15 GS |
2608 | |
2609 | See your installed copy of the perllocal.pod file for a (possibly | |
2610 | incomplete) list of locally installed modules. Note that you want | |
cc65bb49 | 2611 | perllocal.pod, not perllocale.pod, for installed module information. |
693762b4 | 2612 | |
8ebf57cf JH |
2613 | =head1 Minimizing the Perl installation |
2614 | ||
2615 | The following section is meant for people worrying about squeezing the | |
2616 | Perl installation into minimal systems (for example when installing | |
2617 | operating systems, or in really small filesystems). | |
2618 | ||
c8214fdf | 2619 | Leaving out as many extensions as possible is an obvious way: |
5cda700b AD |
2620 | Encode, with its big conversion tables, consumes a lot of |
2621 | space. On the other hand, you cannot throw away everything. The | |
2622 | Fcntl module is pretty essential. If you need to do network | |
c8214fdf JH |
2623 | programming, you'll appreciate the Socket module, and so forth: it all |
2624 | depends on what do you need to do. | |
2625 | ||
8ebf57cf JH |
2626 | In the following we offer two different slimmed down installation |
2627 | recipes. They are informative, not normative: the choice of files | |
2628 | depends on what you need. | |
2629 | ||
2630 | Firstly, the bare minimum to run this script | |
2631 | ||
2632 | use strict; | |
2633 | use warnings; | |
2634 | foreach my $f (</*>) { | |
2635 | print("$f\n"); | |
2636 | } | |
2637 | ||
5585d096 | 2638 | in Linux with perl-5.35.10 is as follows (under $Config{prefix}): |
8ebf57cf JH |
2639 | |
2640 | ./bin/perl | |
5585d096 RB |
2641 | ./lib/perl5/5.35.10/strict.pm |
2642 | ./lib/perl5/5.35.10/warnings.pm | |
2643 | ./lib/perl5/5.35.10/i686-linux/File/Glob.pm | |
2644 | ./lib/perl5/5.35.10/feature.pm | |
2645 | ./lib/perl5/5.35.10/XSLoader.pm | |
2646 | ./lib/perl5/5.35.10/i686-linux/auto/File/Glob/Glob.so | |
8ebf57cf | 2647 | |
ab97e755 MB |
2648 | Secondly, for perl-5.10.1, the Debian perl-base package contains 591 |
2649 | files, (of which 510 are for lib/unicore) totaling about 3.5MB in its | |
2650 | i386 version. Omitting the lib/unicore/* files for brevity, the | |
2651 | remaining files are: | |
8ebf57cf | 2652 | |
bfe08c74 | 2653 | /usr/bin/perl |
00930d57 AD |
2654 | /usr/bin/perl5.10.1 |
2655 | /usr/lib/perl/5.10.1/Config.pm | |
2656 | /usr/lib/perl/5.10.1/Config_git.pl | |
2657 | /usr/lib/perl/5.10.1/Config_heavy.pl | |
2658 | /usr/lib/perl/5.10.1/Cwd.pm | |
2659 | /usr/lib/perl/5.10.1/DynaLoader.pm | |
2660 | /usr/lib/perl/5.10.1/Errno.pm | |
2661 | /usr/lib/perl/5.10.1/Fcntl.pm | |
2662 | /usr/lib/perl/5.10.1/File/Glob.pm | |
2663 | /usr/lib/perl/5.10.1/Hash/Util.pm | |
2664 | /usr/lib/perl/5.10.1/IO.pm | |
2665 | /usr/lib/perl/5.10.1/IO/File.pm | |
2666 | /usr/lib/perl/5.10.1/IO/Handle.pm | |
2667 | /usr/lib/perl/5.10.1/IO/Pipe.pm | |
2668 | /usr/lib/perl/5.10.1/IO/Seekable.pm | |
2669 | /usr/lib/perl/5.10.1/IO/Select.pm | |
2670 | /usr/lib/perl/5.10.1/IO/Socket.pm | |
2671 | /usr/lib/perl/5.10.1/IO/Socket/INET.pm | |
2672 | /usr/lib/perl/5.10.1/IO/Socket/UNIX.pm | |
2673 | /usr/lib/perl/5.10.1/List/Util.pm | |
2674 | /usr/lib/perl/5.10.1/POSIX.pm | |
2675 | /usr/lib/perl/5.10.1/Scalar/Util.pm | |
2676 | /usr/lib/perl/5.10.1/Socket.pm | |
2677 | /usr/lib/perl/5.10.1/XSLoader.pm | |
2678 | /usr/lib/perl/5.10.1/auto/Cwd/Cwd.so | |
2679 | /usr/lib/perl/5.10.1/auto/DynaLoader/autosplit.ix | |
2680 | /usr/lib/perl/5.10.1/auto/DynaLoader/dl_expandspec.al | |
2681 | /usr/lib/perl/5.10.1/auto/DynaLoader/dl_find_symbol_anywhere.al | |
2682 | /usr/lib/perl/5.10.1/auto/DynaLoader/dl_findfile.al | |
2683 | /usr/lib/perl/5.10.1/auto/Fcntl/Fcntl.so | |
2684 | /usr/lib/perl/5.10.1/auto/File/Glob/Glob.so | |
2685 | /usr/lib/perl/5.10.1/auto/Hash/Util/Util.so | |
2686 | /usr/lib/perl/5.10.1/auto/IO/IO.so | |
2687 | /usr/lib/perl/5.10.1/auto/List/Util/Util.so | |
2688 | /usr/lib/perl/5.10.1/auto/POSIX/POSIX.so | |
2689 | /usr/lib/perl/5.10.1/auto/POSIX/autosplit.ix | |
2690 | /usr/lib/perl/5.10.1/auto/POSIX/load_imports.al | |
2691 | /usr/lib/perl/5.10.1/auto/Socket/Socket.so | |
2692 | /usr/lib/perl/5.10.1/lib.pm | |
2693 | /usr/lib/perl/5.10.1/re.pm | |
8ebf57cf | 2694 | /usr/share/doc/perl/AUTHORS.gz |
bfe08c74 | 2695 | /usr/share/doc/perl/Documentation |
00930d57 | 2696 | /usr/share/doc/perl/README.Debian |
8ebf57cf | 2697 | /usr/share/doc/perl/changelog.Debian.gz |
bfe08c74 | 2698 | /usr/share/doc/perl/copyright |
00930d57 | 2699 | /usr/share/lintian/overrides/perl-base |
8ebf57cf | 2700 | /usr/share/man/man1/perl.1.gz |
00930d57 AD |
2701 | /usr/share/man/man1/perl5.10.1.1.gz |
2702 | /usr/share/perl/5.10.1/AutoLoader.pm | |
2703 | /usr/share/perl/5.10.1/Carp.pm | |
2704 | /usr/share/perl/5.10.1/Carp/Heavy.pm | |
2705 | /usr/share/perl/5.10.1/Exporter.pm | |
2706 | /usr/share/perl/5.10.1/Exporter/Heavy.pm | |
2707 | /usr/share/perl/5.10.1/File/Spec.pm | |
2708 | /usr/share/perl/5.10.1/File/Spec/Unix.pm | |
2709 | /usr/share/perl/5.10.1/FileHandle.pm | |
2710 | /usr/share/perl/5.10.1/Getopt/Long.pm | |
2711 | /usr/share/perl/5.10.1/IPC/Open2.pm | |
2712 | /usr/share/perl/5.10.1/IPC/Open3.pm | |
2713 | /usr/share/perl/5.10.1/SelectSaver.pm | |
2714 | /usr/share/perl/5.10.1/Symbol.pm | |
2715 | /usr/share/perl/5.10.1/Text/ParseWords.pm | |
2716 | /usr/share/perl/5.10.1/Text/Tabs.pm | |
2717 | /usr/share/perl/5.10.1/Text/Wrap.pm | |
2718 | /usr/share/perl/5.10.1/Tie/Hash.pm | |
2719 | /usr/share/perl/5.10.1/attributes.pm | |
2720 | /usr/share/perl/5.10.1/base.pm | |
2721 | /usr/share/perl/5.10.1/bytes.pm | |
2722 | /usr/share/perl/5.10.1/bytes_heavy.pl | |
2723 | /usr/share/perl/5.10.1/constant.pm | |
2724 | /usr/share/perl/5.10.1/fields.pm | |
2725 | /usr/share/perl/5.10.1/integer.pm | |
2726 | /usr/share/perl/5.10.1/locale.pm | |
2727 | /usr/share/perl/5.10.1/overload.pm | |
2728 | /usr/share/perl/5.10.1/strict.pm | |
2729 | /usr/share/perl/5.10.1/unicore/* | |
2730 | /usr/share/perl/5.10.1/utf8.pm | |
2731 | /usr/share/perl/5.10.1/utf8_heavy.pl | |
2732 | /usr/share/perl/5.10.1/vars.pm | |
2733 | /usr/share/perl/5.10.1/warnings.pm | |
2734 | /usr/share/perl/5.10.1/warnings/register.pm | |
8ebf57cf | 2735 | |
e7a3c61b JH |
2736 | A nice trick to find out the minimal set of Perl library files you will |
2737 | need to run a Perl program is | |
2738 | ||
a0a8d9d3 | 2739 | perl -e 'do "prog.pl"; END { print "$_\n" for sort keys %INC }' |
e7a3c61b JH |
2740 | |
2741 | (this will not find libraries required in runtime, unfortunately, but | |
2742 | it's a minimal set) and if you want to find out all the files you can | |
2743 | use something like the below | |
2744 | ||
979b4168 KW |
2745 | strace perl -le 'do "x.pl"' 2>&1 \ |
2746 | | perl -nle '/^open\(\"(.+?)"/ && print $1' | |
e7a3c61b JH |
2747 | |
2748 | (The 'strace' is Linux-specific, other similar utilities include 'truss' | |
2749 | and 'ktrace'.) | |
2750 | ||
c19ccd8c RGS |
2751 | =head2 C<-DNO_MATHOMS> |
2752 | ||
2753 | If you configure perl with C<-Accflags=-DNO_MATHOMS>, the functions from | |
2754 | F<mathoms.c> will not be compiled in. Those functions are no longer used | |
2755 | by perl itself; for source compatibility reasons, though, they weren't | |
2756 | completely removed. | |
2757 | ||
d6295071 TC |
2758 | =head2 C<-DNO_PERL_INTERNAL_RAND_SEED> |
2759 | X<PERL_INTERNAL_RAND_SEED> | |
2760 | ||
2761 | If you configure perl with C<-Accflags=-DNO_PERL_INTERNAL_RAND_SEED>, | |
ab473f03 | 2762 | perl will ignore the C<PERL_INTERNAL_RAND_SEED> environment variable. |
d6295071 | 2763 | |
8e07c86e AD |
2764 | =head1 DOCUMENTATION |
2765 | ||
bfb7748a | 2766 | Read the manual entries before running perl. The main documentation |
b0a63d58 | 2767 | is in the F<pod/> subdirectory and should have been installed during the |
8e07c86e | 2768 | build process. Type B<man perl> to get started. Alternatively, you |
bfb7748a AD |
2769 | can type B<perldoc perl> to use the supplied perldoc script. This is |
2770 | sometimes useful for finding things in the library modules. | |
8e07c86e AD |
2771 | |
2772 | =head1 AUTHOR | |
2773 | ||
bfb7748a AD |
2774 | Original author: Andy Dougherty doughera@lafayette.edu , borrowing very |
2775 | heavily from the original README by Larry Wall, with lots of helpful | |
2776 | feedback and additions from the perl5-porters@perl.org folks. | |
fb73857a | 2777 | |
f5b3b617 AD |
2778 | If you have problems, corrections, or questions, please see |
2779 | L<"Reporting Problems"> above. | |
2780 | ||
2781 | =head1 REDISTRIBUTION | |
2782 | ||
2783 | This document is part of the Perl package and may be distributed under | |
d6baa268 | 2784 | the same terms as perl itself, with the following additional request: |
f5b3b617 | 2785 | If you are distributing a modified version of perl (perhaps as part of |
d6baa268 | 2786 | a larger package) please B<do> modify these installation instructions |
ba673321 DH |
2787 | and the contact information to match your distribution. Additional |
2788 | information for packagers is in F<PACKAGING>. |