X-Git-Url: https://perl5.git.perl.org/perl5.git/blobdiff_plain/9ff7b177b9087b27a95fa3e41960f92cc39f5aa1..7baadcd09acc8f332e8235cc586cedcaa3f4616c:/README.macosx diff --git a/README.macosx b/README.macosx index 27921e0..0501b1f 100644 --- a/README.macosx +++ b/README.macosx @@ -4,26 +4,37 @@ designed to be readable as is. =head1 NAME -README.macosx - Perl under Mac OS X +perlmacosx - Perl under Mac OS X =head1 SYNOPSIS -This document briefly describes perl under Mac OS X. +This document briefly describes Perl under Mac OS X. + curl http://www.cpan.org/src/perl-5.12.3.tar.gz > perl-5.12.3.tar.gz + tar -xzf perl-5.12.3.tar.gz + cd perl-5.12.3 + ./Configure -des -Dprefix=/usr/local/ + make + make test + sudo make install =head1 DESCRIPTION -The latest Perl (5.8.1-RC3 as of this writing) builds without changes -under Mac OS X. Under the 10.3 "Panther" release, all self-tests pass, -and all standard features are supported. +The latest Perl release (5.12.3 as of this writing) builds without changes +under all versions of Mac OS X from 10.3 "Panther" onwards. -Earlier Mac OS X releases did not include a completely thread-safe libc, -so threading is not fully supported. Also, earlier releases included a -somewhat buggy libdb, so some of the DB_File tests are known to fail on -those releases. +In order to build your own version of Perl you will need 'make' +this is part of the Apples developer tools (you only need the 'unix tools'), +usually supplied with Mac OS install DVDs. You do not need the latest +version of Xcode (which is now charged for) in order to install make. +Earlier Mac OS X releases (10.2 "Jaguar" and older) did not include a +completely thread-safe libc, so threading is not fully supported. Also, +earlier releases included a buggy libdb, so some of the DB_File tests +are known to fail on those releases. -=head1 INSTALLATION PREFIX + +=head2 Installation Prefix The default installation location for this release uses the traditional UNIX directory layout under /usr/local. This is the recommended location @@ -38,7 +49,81 @@ that mirrors that of Apple's default Perl, with core modules stored in on a file server and used by many Macs. -=head1 LIBPERL AND PREBINDING +=head2 SDK support + +First, export the path to the SDK into the build environment: + + export SDK=/Developer/SDKs/MacOSX10.3.9.sdk + +Use an SDK by exporting some additions to Perl's 'ccflags' and '..flags' +config variables: + + ./Configure -Accflags="-nostdinc -B$SDK/usr/include/gcc \ + -B$SDK/usr/lib/gcc -isystem$SDK/usr/include \ + -F$SDK/System/Library/Frameworks" \ + -Aldflags="-Wl,-syslibroot,$SDK" \ + -de + +=head2 Universal Binary support + +To compile perl as a universal binary (built for both ppc and intel), export +the SDK variable as above, selecting the 10.4u SDK: + + export SDK=/Developer/SDKs/MacOSX10.4u.sdk + +In addition to the compiler flags used to select the SDK, also add the flags +for creating a universal binary: + + ./Configure -Accflags="-arch i686 -arch ppc -nostdinc -B$SDK/usr/include/gcc \ + -B$SDK/usr/lib/gcc -isystem$SDK/usr/include \ + -F$SDK/System/Library/Frameworks" \ + -Aldflags="-arch i686 -arch ppc -Wl,-syslibroot,$SDK" \ + -de + +In Leopard (MacOSX 10.5.6 at the time of this writing) you must use the 10.5 SDK: + + export SDK=/Developer/SDKs/MacOSX10.5.sdk + +You can use the same compiler flags you would use with the 10.4u SDK. + +Keep in mind that these compiler and linker settings will also be used when +building CPAN modules. For XS modules to be compiled as a universal binary, any +libraries it links to must also be universal binaries. The system libraries that +Apple includes with the 10.4u SDK are all universal, but user-installed libraries +may need to be re-installed as universal binaries. + +=head2 64-bit PPC support + +Follow the instructions in F to build perl with support for 64-bit +integers (C) or both 64-bit integers and 64-bit addressing +(C). In the latter case, the resulting binary will run only +on G5-based hosts. + +Support for 64-bit addressing is experimental: some aspects of Perl may be +omitted or buggy. Note the messages output by F for further +information. Please use C to submit a problem report in the +event that you encounter difficulties. + +When building 64-bit modules, it is your responsibility to ensure that linked +external libraries and frameworks provide 64-bit support: if they do not, +module building may appear to succeed, but attempts to use the module will +result in run-time dynamic linking errors, and subsequent test failures. +You can use C to discover the architectures supported by a library: + + $ file libgdbm.3.0.0.dylib + libgdbm.3.0.0.dylib: Mach-O fat file with 2 architectures + libgdbm.3.0.0.dylib (for architecture ppc): Mach-O dynamically linked shared library ppc + libgdbm.3.0.0.dylib (for architecture ppc64): Mach-O 64-bit dynamically linked shared library ppc64 + +Note that this issue precludes the building of many Macintosh-specific CPAN +modules (C), as the required Apple frameworks do not provide PPC64 +support. Similarly, downloads from Fink or Darwinports are unlikely to provide +64-bit support; the libraries must be rebuilt from source with the appropriate +compiler and linker flags. For further information, see Apple's +I<64-Bit Transition Guide> at +L. + +=head2 libperl and Prebinding Mac OS X ships with a dynamically-loaded libperl, but the default for this release is to compile a static libperl. The reason for this is @@ -50,66 +135,67 @@ thus has easy access to it when building Perl, but ordinary users would need to go to a great deal of effort to obtain the information needed for pre-binding. -You can override the default and build a shared libperl if you wish, but -the load time will be significantly greater than either the static -library, or Apple's pre-bound dynamic library. +You can override the default and build a shared libperl if you wish +(S), but the load time on pre-10.4 OS +releases will be greater than either the static library, or Apple's +pre-bound dynamic library. + +With 10.4 "Tiger" and newer, Apple has all but eliminated the performance +penalty for non-prebound libraries. -=head1 UPDATING PANTHER +=head2 Updating Apple's Perl -As of this writing, the latest Perl release that has been tested and -approved for inclusion in the 10.3 "Panther" release of Mac OS X is -5.8.1 RC3. It is currently unknown whether the final 5.8.1 release will -be made in time to be tested and included with Panther. +In a word - don't, at least without a *very* good reason. Your scripts +can just as easily begin with "#!/usr/local/bin/perl" as with +"#!/usr/bin/perl". Scripts supplied by Apple and other third parties as +part of installation packages and such have generally only been tested +with the /usr/bin/perl that's installed by Apple. -If the final release of Perl 5.8.1 is not made in time to be included -with Panther, it is recommended that you wait for an official Apple -update to the OS, rather than attempting to update it yourself. In most -cases, if you need a newer Perl, it is preferable to install it in some -other location, such as /usr/local or /opt, rather than overwriting the -system Perl. +If you find that you do need to update the system Perl, one issue worth +keeping in mind is the question of static vs. dynamic libraries. If you +upgrade using the default static libperl, you will find that the dynamic +libperl supplied by Apple will not be deleted. If both libraries are +present when an application that links against libperl is built, ld will +link against the dynamic library by default. So, if you need to replace +Apple's dynamic libperl with a static libperl, you need to be sure to +delete the older dynamic library after you've installed the update. -If you find that you do need to update the system Perl, there is one -potential issue. If you upgrade using the default static libperl, you -will find that the dynamic libperl supplied by Apple will not be -deleted. If both libraries are present when an application that links -against libperl is built, ld will link against the dynamic library by -default. So, if you need to replace Apple's dynamic libperl with a -static libperl, you need to be sure to delete the older dynamic library -after you've installed the update. -Note that this is only an issue when updating from an older build of the -same Perl version. If you're updating from (for example) 5.8.1 to 5.8.2, -this issue won't affect you. +=head2 Known problems +If you have installed extra libraries such as GDBM through Fink +(in other words, you have libraries under F), or libdlcompat +to F, you may need to be extra careful when running +Configure to not to confuse Configure and Perl about which libraries +to use. Being confused will show up for example as "dyld" errors about +symbol problems, for example during "make test". The safest bet is to run +Configure as -=head1 MACPERL + Configure ... -Uloclibpth -Dlibpth=/usr/lib -Quite a bit has been written about MacPerl, the Perl distribution for -"Classic MacOS" - that is, versions 9 and earlier of MacOS. Because it -runs in environment that's very different from that of UNIX, many things -are done differently in MacPerl. Modules are installed using a different -procedure, Perl itself is built differently, path names are different, -etc. +to make Configure look only into the system libraries. If you have some +extra library directories that you really want to use (such as newer +Berkeley DB libraries in pre-Panther systems), add those to the libpth: -From the perspective of a Perl programmer, Mac OS X is more like a -traditional UNIX than Classic MacOS. If you find documentation that -refers to a special procedure that's needed for MacOS that's drastically -different from the instructions provided for UNIX, the MacOS -instructions are quite often intended for MacPerl on Classic MacOS. In -that case, the correct procedure on Mac OS X is usually to follow the -UNIX instructions, rather than the MacPerl instructions. + Configure ... -Uloclibpth -Dlibpth='/usr/lib /opt/lib' +The default of building Perl statically may cause problems with complex +applications like Tk: in that case consider building shared Perl -=head1 CARBON + Configure ... -Duseshrplib -MacPerl ships with a number of modules that are used to access the -classic MacOS toolbox. Many of these modules have been updated to use -Mac OS X's newer "Carbon" toolbox, and are available from CPAN in the -"Mac::Carbon" module. +but remember that there's a startup cost to pay in that case (see above +"libperl and Prebinding"). +Starting with Tiger (Mac OS X 10.4), Apple shipped broken locale files for +the eu_ES locale (Basque-Spain). In previous releases of Perl, this resulted in +failures in the F test. These failures have been suppressed +in the current release of Perl by making the test ignore the broken locale. +If you need to use the eu_ES locale, you should contact Apple support. -=head1 COCOA + +=head2 Cocoa There are two ways to use Cocoa from Perl. Apple's PerlObjCBridge module, included with Mac OS X, can be used by standalone scripts to @@ -121,10 +207,50 @@ can be built in Perl. CamelBones can be found on SourceForge, at L. +=head1 Starting From Scratch + +Unfortunately it is not that difficult somehow manage to break one's +Mac OS X Perl rather severely. If all else fails and you want to +really, B, start from scratch and remove even your Apple Perl +installation (which has become corrupted somehow), the following +instructions should do it. B We will B come to fix your system +if you do this. + +First, get rid of the libperl.dylib: + + # cd /System/Library/Perl/darwin/CORE + # rm libperl.dylib + +Then delete every .bundle file found anywhere in the folders: + + /System/Library/Perl + /Library/Perl + +You can find them for example by + + # find /System/Library/Perl /Library/Perl -name '*.bundle' -print + +After this you can either copy Perl from your operating system media +(you will need at least the /System/Library/Perl and /usr/bin/perl), +or rebuild Perl from the source code with C NOTE: the C<-Dprefix=/usr> to replace the system Perl +works much better with Perl 5.8.1 and later, in Perl 5.8.0 the +settings were not quite right. + +"Pacifist" from CharlesSoft (L) is a nice +way to extract the Perl binaries from the OS media, without having to +reinstall the entire OS. + + =head1 AUTHOR -This README was written by Sherm Pendley Esherm@dot-app.orgE. +This README was written by Sherm Pendley Esherm@dot-app.orgE, +and subsequently updated by Dominic Dunlop Edomo@computer.orgE. +The "Starting From Scratch" recipe was contributed by John Montbriand +Emontbriand@apple.comE. =head1 DATE -Last modified 2003.07.31. +Last modified 2006-02-24.