Penguin
Recent Changes
Blame: perlmachten(1)
EditPageHistoryDiffInfoLikePages
Annotated edit history of perlmachten(1) version 2, including all changes. View license author blame.
Rev Author # Line
1 perry 1 PERLMACHTEN
2 !!!PERLMACHTEN
3 NAME
4 DESCRIPTION
5 AUTHOR
6 DATE
7 ----
8 !!NAME
9
10
2 perry 11 README .machten - Perl version 5 on Power !MachTen systems
1 perry 12 !!DESCRIPTION
13
14
15 This document describes how to build Perl 5 on Power
2 perry 16 !MachTen systems, and discusses a few wrinkles in the
1 perry 17 implementation.
18
19
2 perry 20 __Compiling Perl 5 on !MachTen__
1 perry 21
22
2 perry 23 To compile perl under !MachTen 4.1.4 (and probably
1 perry 24 earlier versions):
25
26
27 ./Configure -de
28 make
29 make test
30 make install
2 perry 31 This builds and installs a statically-linked perl; !MachTen's dynamic linking facilities are not adequate to support Perl's use of dynamically linked libraries. (See ''hints/machten.sh'' for more information.)
1 perry 32
33
34 You should have at least 32 megabytes of free memory on
35 your system before running the make
36 command.
37
38
39 For much more information on building perl -- for
40 example, on how to change the default installation directory
41 -- see ''INSTALL'' .
42
43
44 __Failures during__ make
45 test
46
47
48 op/lexassign.t
49
50
51 This test may fail when first run after building perl.
52 It does not fail subsequently. The cause is
53 unknown.
54
55
56 pragma/warnings.t
57
58
59 Test 257 fails due to a failure to warn about attempts
60 to read from a filehandle which is a duplicate of stdout
61 when stdout is attached to a pipe. The output of the test
62 contains a block comment which discusses a different
2 perry 63 failure, not applicable to !MachTen.
1 perry 64
65
66 The root of the problem is that Machten does not assign
67 a file type to either end of a pipe (see stat), resulting,
68 among other things in Perl's -p test failing on
69 file descriptors belonging to pipes. As a result, perl
70 becomes confused, and the test for reading from a write-only
71 file fails. I am reluctant to patch perl to get around this,
72 as it's clearly an OS bug (about which Tenon has
73 been informed), and limited in its effect on practical Perl
74 programs.
75
76
77 __Building external modules__
78
79
80 To add an external module to perl, build in the normal
2 perry 81 way, which is documented in !ExtUtils::!MakeMaker, or which
1 perry 82 can be driven automatically by the CPAN module
83 (see CPAN ), which is part of the standard
84 distribution. If you want to install a module which
85 contains XS code (C or C ++ source
86 which compiles to object code for linking with perl), you
87 will have to replace your perl binary with a new version
88 containing the new statically-linked object module. The
89 build process tells you how to do this.
90
91
92 There is a gotcha, however, which users usually
93 encounter immediately they respond to CPAN 's
94 invitation to install Bundle::CPAN. When installing
95 a ''bundle'' -- a group of modules which together achieve
96 some particular purpose, the installation process for later
97 modules in the bundle tends to assume that earlier modules
98 have been fully installed and are available for use. This is
99 not true on a statically-linked system for earlier modules
100 which contain XS code. As a result the
101 installation of the bundle fails. The work-around is not to
102 install the bundle as a one-shot operation, but instead to
103 see what modules it contains, and install these
104 one-at-a-time by hand in the order given.
105 !!AUTHOR
106
107
108 Dominic Dunlop
109 !!DATE
110
111
112 Version 1.0.1 2000-03-27
113 ----
This page is a man page (or other imported legacy content). We are unable to automatically determine the license status of this page.