Commit | Line | Data |
16d20bd9 |
1 | ------------- |
2 | Version 5.002 |
3 | ------------- |
4 | |
5 | Summary of user-visible Configure and build changes since 5.001: |
6 | |
7 | Yet more enhancements and fixes have been made to the Configure and |
8 | build process for perl. Most of these will not be visible to the |
9 | ordinary user--they just make the process more robust and likely to |
10 | work on a wider range of platforms. |
11 | |
12 | This is a brief summary of the most important changes: |
13 | |
14 | Include 5.000 - 5.001 upgrage notes :-) (see below). You might |
15 | want to read through them as well as these notes. |
16 | |
17 | Install documentation for perl modules and pod2* translators. You can |
18 | now view perl module documentation with either your system's man(1) |
19 | program or with the supplied perldoc script. |
20 | |
21 | Support Linux ELF dynamic loading. |
22 | |
23 | Many hint file updates. |
24 | |
4aa0a1f7 |
25 | Upgrade Traps and Pitfalls: |
26 | |
27 | Since a lot has changed in the build process, you are probably best off |
28 | starting with a fresh copy of the perl5.002 sources. In particular, |
29 | your 5.000 or 5.001 config.sh will contain several variables that are no |
30 | longer needed. Further, improvements in the Configure tests may mean |
31 | that some of the answers will be different than they were in previous |
32 | versions, and which answer to keep can be difficult to sort out. |
33 | Therefore, you are probably better off ignoring your old config.sh, as |
34 | in the following: |
35 | |
36 | make distclean # (if you've built perl before) |
37 | sh Configure [whatever options you like] |
38 | make depend |
39 | make |
40 | make test |
16d20bd9 |
41 | |
42 | ------------- |
43 | Version 5.001 |
44 | ------------- |
45 | |
46 | Summary of user-visible Configure and build changes since 5.000: |
47 | |
48 | A large number of enhancements and fixes have been made to the |
49 | Configure and build process for perl. Most of these will not be |
50 | visible to the ordinary user--they just make the process more robust |
51 | and likely to work on a wider range of platforms. |
52 | |
53 | This is a brief summary of the most important changes. |
54 | |
55 | Configure changes: |
56 | New and improved Configure command line options. -O now overrides |
57 | config.sh settings. -D options can now include spaces, if |
58 | protected in quotes (e.g. -Dcc='gcc -posix'). Type Configure -h |
59 | for a full listing of options. |
60 | |
61 | Users can now turn on the defaults for the rest of Configure by |
62 | typing &-d at any Configure prompt. This is useful if you just |
63 | want to change one or two answers. |
64 | |
65 | Support on (non-Sun) SVR4 systems for dynamic loading and shared |
66 | libperl.so |
67 | |
68 | Numerous new or updated hints files: PowerUnix, aix 3.x and 4.x, |
69 | bsd386, convexos, cxux, DEC OSF, Esix, FreeBSD, HP-UX (especially if |
70 | you're using the bundled compiler), irix 4.x, 5.x, and 6.x, Linux, |
71 | MPE/IX, NeXT 3.0 and 3.2, Solaris, SVR4, Ultrix (especially 4.3), |
72 | and Unicos. |
73 | |
74 | Improved generation of a suitable name for architecture-dependent |
75 | library files. NOTE: This may differ from the name you had from |
76 | your 5.000 installation. |
77 | |
78 | Many many portability enhancements and fixes. |
79 | |
80 | Build process: |
81 | |
82 | The process for building extensions has been extensively revised. See |
83 | lib/ExtUtils/MakeMaker.pm for complete documentation. Basically, with |
84 | just a simple Makefile.PL (such as the one generated by h2xs), you can |
85 | now build an extension from anywhere on your system, even if you've |
86 | deleted the perl source. |
87 | |
88 | Improved build/install documentation in README. A little. |
89 | |
90 | Improved dynamic loading on HP-UX. Support dynamic loading on SVR4. |
91 | |
92 | Installperl now gets the version correct :-) |
93 | |
94 | Installperl now saves the perl *.h files and the libperl.a library |
95 | in your architecture-dependent library directory so that you can |
96 | later build extensions without having to re-install the perl |
97 | source. |
98 | |
99 | Include x2p/a2p.c generated by byacc from x2p/a2p.y. |
100 | |
101 | Many many portability fixes. |
102 | |
103 | Upgrade Traps and Pitfalls: |
104 | |
105 | Since a lot has changed in the build process, you are probably best |
106 | off starting with a fresh copy of the perl5.000 sources. In particular, |
107 | your 5.000 config.sh will contain several variables that are no longer |
108 | needed. Further, improvements in the Configure tests may mean that some |
109 | of the answers will be different than they were in 5.000, and which answer |
110 | to keep can be difficult to sort out. Therefore, you are probably |
111 | better off ignoring your old config.sh. |
112 | |
113 | One big change is that architecture-dependent library files may well |
114 | be stored in a different location in 5.001. This is because the default |
115 | name used in the 5.000 release was not sufficiently specific to |
116 | distinguish incompatible architectures. The relevant variable is $archlib |
117 | in config.sh. Before you run ``make install'' you should rename your old |
118 | $archlib. Thus if your $archlib for version 5.000 was |
119 | /usr/local/lib/perl5/foo, and your new value for 5.001 is |
120 | /usr/local/lib/perl5/foo-bar, then you should |
121 | mv /usr/local/lib/perl5/foo /usr/local/lib/perl5/foo-bar |
122 | before running ``make install''. |
123 | |
124 | Alternatively, you could override Configure's default guess for $archlib |
125 | either by sh Configure -Darchname='foo', or by answering 'foo' when |
126 | prompted by Configure for the architecture name. |
127 | |
128 | The following is the sequence of steps to upgrade to 5.001: |
129 | cd perl5.000 |
130 | make realclean |
131 | rm config.sh |
132 | <apply 5.001 patch> |
133 | sh Configure |
134 | make depend |
135 | make |
136 | make test |
137 | <mv old architecture-dependent library to new location, if needed> |
138 | make install |
139 | |