1 If you read this file _as_is_, just ignore the funny characters you see.
2 It is written in the POD format (see pod/perlpod.pod) which is specially
3 designed to be readable as is.
7 README.macosx - Perl under Mac OS X
11 This document briefly describes perl under Mac OS X.
16 The latest Perl (5.8.1-RC3 as of this writing) builds without changes
17 under Mac OS X. Under the 10.3 "Panther" release, all self-tests pass,
18 and all standard features are supported.
20 Earlier Mac OS X releases did not include a completely thread-safe libc,
21 so threading is not fully supported. Also, earlier releases included a
22 somewhat buggy libdb, so some of the DB_File tests are known to fail on
26 =head2 Installation Prefix
28 The default installation location for this release uses the traditional
29 UNIX directory layout under /usr/local. This is the recommended location
30 for most users, and will leave the Apple-supplied Perl and its modules
33 Using an installation prefix of '/usr' will result in a directory layout
34 that mirrors that of Apple's default Perl, with core modules stored in
35 '/System/Library/Perl/${version}', CPAN modules stored in
36 '/Library/Perl/${version}', and the addition of
37 '/Network/Library/Perl/${version}' to @INC for modules that are stored
38 on a file server and used by many Macs.
41 =head2 libperl and Prebinding
43 Mac OS X ships with a dynamically-loaded libperl, but the default for
44 this release is to compile a static libperl. The reason for this is
45 pre-binding. Dynamic libraries can be pre-bound to a specific address in
46 memory in order to decrease load time. To do this, one needs to be aware
47 of the location and size of all previously-loaded libraries. Apple
48 collects this information as part of their overall OS build process, and
49 thus has easy access to it when building Perl, but ordinary users would
50 need to go to a great deal of effort to obtain the information needed
53 You can override the default and build a shared libperl if you wish
54 (S<Configure ... -Duseshrlib>), but the load time will be
55 significantly greater than either the static library, or Apple's
56 pre-bound dynamic library.
59 =head2 Updating Panther
61 As of this writing, the latest Perl release that has been tested and
62 approved for inclusion in the 10.3 "Panther" release of Mac OS X is
63 5.8.1 RC3. It is currently unknown whether the final 5.8.1 release will
64 be made in time to be tested and included with Panther.
66 If the final release of Perl 5.8.1 is not made in time to be included
67 with Panther, it is recommended that you wait for an official Apple
68 update to the OS, rather than attempting to update it yourself. In most
69 cases, if you need a newer Perl, it is preferable to install it in some
70 other location, such as /usr/local or /opt, rather than overwriting the
71 system Perl. The default location (no -Dprefix=... specified when running
72 Configure) is /usr/local.
74 If you find that you do need to update the system Perl, there is one
75 potential issue. If you upgrade using the default static libperl, you
76 will find that the dynamic libperl supplied by Apple will not be
77 deleted. If both libraries are present when an application that links
78 against libperl is built, ld will link against the dynamic library by
79 default. So, if you need to replace Apple's dynamic libperl with a
80 static libperl, you need to be sure to delete the older dynamic library
81 after you've installed the update.
83 Note that this is only an issue when updating from an older build of the
84 same Perl version. If you're updating from (for example) 5.8.1 to 5.8.2,
85 this issue won't affect you.
90 If you have installed extra libraries such as GDBM through Fink
91 (in other words, you have libraries under F</sw/lib>), or libdlcompat
92 to F</usr/local/lib>, you may need to be extra careful when running
93 Configure to not to confuse Configure and Perl about which libraries
94 to use. Being confused will show up for example as "dyld" errors about
95 symbol problems, for example during "make test". The safest bet is to run
98 Configure ... -Uloclibpth -Dlibpth=/usr/lib
100 to make Configure look only into the system libraries. If you have some
101 extra library directories that you really want to use (such as newer
102 Berkeley DB libraries in pre-Panther systems), add those to the libpth:
104 Configure ... -Uloclibpth -Dlibpth='/usr/lib /opt/lib'
106 The default of building Perl statically may cause problems with complex
107 applications like Tk: in that case consider building shared Perl
109 Configure ... -Duseshrplib
111 but remember that there's a startup cost to pay in that case (see above
112 "libperl and Prebinding").
114 Starting with Tiger (Mac OS X 10.4), Apple shipped broken locale files for
115 the eu_ES locale (Basque-Spain). When testing Perl, this will show up as
116 test failues in the tests C<..lib/locale>. Unless you require the
117 eu_ES locale, you should be OK to install Perl. If you do need this
118 locale, you should contact Apple support.
122 Quite a bit has been written about MacPerl, the Perl distribution for
123 "Classic MacOS" - that is, versions 9 and earlier of MacOS. Because it
124 runs in environment that's very different from that of UNIX, many things
125 are done differently in MacPerl. Modules are installed using a different
126 procedure, Perl itself is built differently, path names are different,
129 From the perspective of a Perl programmer, Mac OS X is more like a
130 traditional UNIX than Classic MacOS. If you find documentation that
131 refers to a special procedure that's needed for MacOS that's drastically
132 different from the instructions provided for UNIX, the MacOS
133 instructions are quite often intended for MacPerl on Classic MacOS. In
134 that case, the correct procedure on Mac OS X is usually to follow the
135 UNIX instructions, rather than the MacPerl instructions.
140 MacPerl ships with a number of modules that are used to access the
141 classic MacOS toolbox. Many of these modules have been updated to use
142 Mac OS X's newer "Carbon" toolbox, and are available from CPAN in the
143 "Mac::Carbon" module.
148 There are two ways to use Cocoa from Perl. Apple's PerlObjCBridge
149 module, included with Mac OS X, can be used by standalone scripts to
150 access Foundation (i.e. non-GUI) classes and objects.
152 An alternative is CamelBones, a framework that allows access to both
153 Foundation and AppKit classes and objects, so that full GUI applications
154 can be built in Perl. CamelBones can be found on SourceForge, at
155 L<http://www.sourceforge.net/projects/camelbones/>.
158 =head1 Starting From Scratch
160 Unfortunately it is not that difficult somehow manage to break one's
161 Mac OS X Perl rather severely. If all else fails and you want to
162 really, B<REALLY>, start from scratch and remove even your Apple Perl
163 installation (which has become corrupted somehow), the following
164 instructions should do it. B<Please think twice before following
165 these instructions: they are much like conducting brain surgery to
166 yourself. Without anesthesia.> We will B<not> come to fix your system
169 First, get rid of the libperl.dylib:
171 # cd /System/Library/Perl/darwin/CORE
174 Then delete every .bundle file found anywhere in the folders:
179 You can find them for example by
181 # find /System/Library/Perl /Library/Perl -name '*.bundle' -print
183 After this you can either copy Perl from your operating system CDs
184 (you will need at least the /System/Library/Perl and /usr/bin/perl),
185 or rebuild Perl from the source code with C<Configure -Dprefix=/usr
186 -Dusershrplib> NOTE: the C<-Dprefix=/usr> to replace the system Perl
187 works much better with Perl 5.8.1 and later, in Perl 5.8.0 the
188 settings were not quite right.
193 This README was written by Sherm Pendley E<lt>sherm@dot-app.orgE<gt>.
194 The "Starting From Scratch" recipe was contributed by John Montbriand
195 E<lt>montbriand@apple.comE<gt>.
199 Last modified 2003-09-08.