Perl For Mac Os X


Additional System Libraries¶. Apple does not include the GD library with Mac OS X. Bugzilla needs this if you want to display bug graphs, and you need to install it. The own Mac OS X Perl seams to be installed here: bash-3.2$ ls /Library/Perl/ 5.10 5.12 Updates bash-3.2$ ls /System/Library/Perl/ 5.10 5.12 Extras lib bash-3.2$ There is also a version here: bash-3.2$ ls /opt/local/lib/perl5/ 5.12.4 siteperl vendorperl I thought best is.

perlmacosx - Perl under Mac OS X

This document briefly describes Perl under Mac OS X.

The latest Perl release (5.32.0 as of this writing) builds without changes under all versions of Mac OS X from 10.3 'Panther' onwards.

The only instructions I could find point to Fink, which basically installs modules in a path that isn’t included in the Perl @INC variable, meaning you have to manually specify the full path to the modules in every script — which is not a lot of fun if you’re developing on OS X. Now, this is a Mac, so Perl is already installed and it's already in the path, so all I have to put here for the command is Perl and the name of the file that we're going to run, which is a meta name, because it's just going to run whatever script is open in the editor, so I put in '%F'.

In order to build your own version of Perl you will need 'make', which is part of Apple's developer tools - also known as Xcode. From Mac OS X 10.7 'Lion' onwards, it can be downloaded separately as the 'Command Line Tools' bundle directly from (you will need a free account to log in), or as a part of the Xcode suite, freely available at the App Store. Xcode is a pretty big app, so unless you already have it or really want it, you are advised to get the 'Command Line Tools' bundle separately from the link above. If you want to do it from within Xcode, go to Xcode -> Preferences -> Downloads and select the 'Command Line Tools' option.

Between Mac OS X 10.3 'Panther' and 10.6 'Snow Leopard', the 'Command Line Tools' bundle was called 'unix tools', and was usually supplied with Mac OS install DVDs.

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.

#Installation Prefix

The default installation location for this release uses the traditional UNIX directory layout under /usr/local. This is the recommended location for most users, and will leave the Apple-supplied Perl and its modules undisturbed.

Online scanner virus for mac. Scan your computer for malware for free with the ESET Online Scanner. Our free online virus scanner checks for any type of virus and helps you remove it. ESET’s Free Online Scanner. Free scan with ESET Online. ESET Cyber Security Pro. Advanced protection. ESET Cyber Security. Essential protection. See all for Mac. Antivirus for Mac Protect 1 Mac. Mobile Security iOS & Android. Home Network Security Total protection for your smart home. HouseCall ™ - Free Online Security Scan Detect and fix viruses, worms, spyware, and other malicious threats for free. Download FREE AVG antivirus software for Mac. Protection against viruses, malware & spyware. Easy-to-use virus scanning and clean up. Bitdefender Virus Scanner finds Mac malware as well as Windows viruses with ease. Scan running apps, scan critical locations, scan a specific location or scan the entire system, the award-winning Bitdefender engines will find that malware. Don't put your friends and family at risk by unknowingly passing malware.

Using an installation prefix of '/usr' will result in a directory layout that mirrors that of Apple's default Perl, with core modules stored in '/System/Library/Perl/${version}', CPAN modules stored in '/Library/Perl/${version}', and the addition of '/Network/Library/Perl/${version}' to @INC for modules that are stored on a file server and used by many Macs.

#SDK support

First, export the path to the SDK into the build environment:

Please make sure the SDK version (i.e. the numbers right before '.sdk') matches your system's (in this case, Mac OS X 10.8 'Mountain Lion'), as it is possible to have more than one SDK installed. Also make sure the path exists in your system, and if it doesn't please make sure the SDK is properly installed, as it should come with the 'Command Line Tools' bundle mentioned above. Finally, if you have an older Mac OS X (10.6 'Snow Leopard' and below) running Xcode 4.2 or lower, the SDK path might be something like '/Developer/SDKs/MacOSX10.3.9.sdk'.

You can use the SDK by exporting some additions to Perl's 'ccflags' and '.flags' config variables:

#Universal Binary support

Note: From Mac OS X 10.6 'Snow Leopard' onwards, Apple only supports Intel-based hardware. This means you can safely skip this section unless you have an older Apple computer running on ppc or wish to create a perl binary with backwards compatibility.

You can compile perl as a universal binary (built for both ppc and intel). In Mac OS X 10.4 'Tiger', you must export the 'u' variant of the SDK:

Mac OS X 10.5 'Leopard' and above do not require the 'u' variant.

In addition to the compiler flags used to select the SDK, also add the flags for creating a universal binary:

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.

#64-bit PPC support

Follow the instructions in INSTALL to build perl with support for 64-bit integers (use64bitint) or both 64-bit integers and 64-bit addressing (use64bitall). 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 Configure for further information. Please use to submit a problem report in the event that you encounter difficulties.

Perl Download Mac Os X

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 file to discover the architectures supported by a library:

Note that this issue precludes the building of many Macintosh-specific CPAN modules (Mac::*), 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 64-Bit Transition Guide at

#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 pre-binding. Dynamic libraries can be pre-bound to a specific address in memory in order to decrease load time. To do this, one needs to be aware of the location and size of all previously-loaded libraries. Apple collects this information as part of their overall OS build process, and 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 (Configure .. -Duseshrplib).

With Mac OS X 10.4 'Tiger' and newer, there is almost no performance penalty for non-prebound libraries. Earlier releases will suffer a greater load time than either the static library, or Apple's pre-bound dynamic library.

#Updating Apple's Perl

In a word - don't, at least not 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 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.

#Known problems

If you have installed extra libraries such as GDBM through Fink (in other words, you have libraries under /sw/lib), or libdlcompat to /usr/local/lib, 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

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:

The default of building Perl statically may cause problems with complex applications like Tk: in that case consider building shared Perl

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 lib/locale 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.


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 access Foundation (i.e. non-GUI) classes and objects.

An alternative is CamelBones, a framework that allows access to both Foundation and AppKit classes and objects, so that full GUI applications can be built in Perl. CamelBones can be found on SourceForge, at

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, REALLY, start from scratch and remove even your Apple Perl installation (which has become corrupted somehow), the following instructions should do it. Please think twice before following these instructions: they are much like conducting brain surgery to yourself. Without anesthesia. We will not come to fix your system if you do this.

First, get rid of the libperl.dylib:

Then delete every .bundle file found anywhere in the folders:

You can find them for example by

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 Configure -Dprefix=/usr -Duseshrplib NOTE: the -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 ( is a nice way to extract the Perl binaries from the OS media, without having to reinstall the entire OS.

This README was written by Sherm Pendley <[email protected]>, and subsequently updated by Dominic Dunlop <[email protected]> and Breno G. de Oliveira <[email protected]>. The 'Starting From Scratch' recipe was contributed by John Montbriand <[email protected]>.

Last modified 2013-04-29.


README - Carbon API for perl on Mac OS X

Mac::Carbon is a collection of perl modules for accessing the Carbon API under Mac OS X. It is a port of the Toolbox modules written by Matthias Neeracher for MacPerl.

See the documentation in Mac::Carbon for more implementation details, bugs, etc.

Mac::Carbon does not run under 64-bit perl. There are workarounds listed in '64-BIT PERL' in Mac::Carbon. It does build with a 'fat' 64-bit perl, for use with 32-bit mode.

There are probably a lot of bugs, especially in Carbon.h. Bugs are listed in 'Known Bugs' in Mac::Carbon; please feel free to report more. Patches are welcome, too, of course. For large patches, such as stuff for test suites and building, please do coordinate with me before spending much time on it.

Mac OS

These modules all build under Mac OS, but it is recommended you build them as a part of MacPerl itself, or at least under the MacPerl source (version 5.6.1 or greater). See for more information.

Under Mac OS, extra non-Carbon-compatible routines are available.

Mac OS X

To build these modules on Mac OS X, the Developer Tools are required.

Building these modules has been tested on Mac OS X 10.3 through 10.5, with perl 5.8 and 5.10, with gcc 3.1, 3.3, 4.0, and 4.2. Earlier versions have built under earlier versions of Mac OS X, perl, and gcc, but they have not been recently tested. gcc 3.3 and 4 are the most well-tested.

Mac OS X 10.6 has not yet been tested. Both Intel and PPC have been tested.

This tells you what version of gcc is in use, from the command line:

To change it, try one of the following (as root, or with sudo; sudo is used in the examples). '3' will give you 3.1, '3.3' will give you 3.3, '4.0' will give you 4.0.

The Test::More module is required for running tests.

The separate Mac::Errors module is not required, but is highly recommended, for providing more information from Mac system error codes.


Matthias added some extensions to XS for his Toolbox modules; they were never fully embraced by p5p, and as a result, we have a separate xsubpp for these additional XS macros. The Makefile.PLs will choose and use the appropriate xsubpp version for your version of perl.

You might want to run the test suite with make test TEST_VERBOSE=1. It's cool. For extra tests requiring the GUI, set MAC_CARBON_GUI=1 and MAC_CARBON_SOUND=1 in your environment.

Currently, only a subset of the modules are supported. The ported modules are:

Distributed separately on the CPAN and

And, coming someday, possibly:

There are currently no plans for the other (GUI) modules, including:

We could do these eventually, if there is enough interest. They don't port as easily as some of the others, for many reasons, not the least of which is that we need a framework to handle events etc., which for MacPerl is mostly implemented in macish.c / macish.h.

The Mac Toolbox modules were written by Matthias Neeracher <[email protected]>. They are currently maintained by Chris Nandor <[email protected]>.

$Id: README,v 1.15 2009/09/27 01:22:36 pudge Exp $

Linux For Mac Os X

To install README, copy and paste the appropriate command in to your terminal.

Using Perl Mac Os X

For more information on module installation, please visit the detailed CPAN module installation guide.