X-Git-Url: https://perl5.git.perl.org/perl5.git/blobdiff_plain/ffb8d87aed2af02cd51b9c989d04b1c37420bea3..0a0c4b76b41cff6aaa3670fa19292a3e9248e69e:/README.macosx diff --git a/README.macosx b/README.macosx index 04f8d10..60a4b8d 100644 --- a/README.macosx +++ b/README.macosx @@ -8,20 +8,30 @@ README.macosx - 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.8 as of this writing) builds without changes -under Mac OS X. Under the 10.4 "Tiger" 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. -Mac OS X releases prior to 10.3 "Panther" did not include a completely -thread-safe libc, so threading is not fully supported when Perl is built -for these releases. 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. =head2 Installation Prefix @@ -39,6 +49,80 @@ that mirrors that of Apple's default Perl, with core modules stored in on a file server and used by many Macs. +=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 @@ -52,62 +136,31 @@ 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 -(S), but the load time will be -significantly greater than either the static library, or Apple's +(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. -=head2 Updating Apple-supplied Perl - -Apple ships a threaded build of perl 5.8.6 with Mac OS 10.4.x, "Tiger". -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. The default location (no -Dprefix=... specified when running -Configure) is /usr/local. - -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.6 to 5.8.8, -this issue won't affect you. - -=head2 64-bit Perl - -By default, perl is built to use 32-bit integers and pointers. The hints file, -F, provides experimental support for 64-bit integers -and pointers (on G5 processors only) when Configure is run with the -C<-Duse64bitall> option. Expect many compiler warnings and a number -of test failures. -=head2 Intel processor support +=head2 Updating Apple's Perl -At the time of writing, the Perl developers have no knowledge of the -behaviour (or misbehaviour) of the Perl build process when hosted by -an Intel-based Macintosh. As far as we know, Apple ships Perl 5.8.6 -with Intel developer builds of Mac OS X, so we presume that there -are few or no problems in building that version of Perl. (The source -package used by Apple may be found at L.) -If you encounter problems in building a later version of Perl for an -Intel-based Macintosh, please file a bug report, if possible by using -the following command in the build directory: +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. - ./perl -Ilib utils/perlbug +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. -=head2 Universal binaries - -Apple's Xcode development tools, version 2.1 and later, provide -support for the creation of I, which contain -code for both PowerPC and Intel architectures. (In the past, and on -other platforms, such executable files have been known as I.) Perl's build process currently provides no support for -the production of universal binaries. =head2 Known problems @@ -137,35 +190,10 @@ but remember that there's a startup cost to pay in that case (see above 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 C test. These failures have been supressed +failures in the C 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. -=head2 MacPerl - -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. - -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. - - -=head2 Carbon - -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. - =head2 Cocoa @@ -204,13 +232,17 @@ 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 CDs +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 +-Duseshrplib> 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 @@ -221,4 +253,4 @@ Emontbriand@apple.comE. =head1 DATE -Last modified 2005-11-07. +Last modified 2006-02-24.