PERLMODINSTALL(1)

πŸ’– PERLMODINSTALL πŸ’–

okay so this is perlmodinstall, from the Perl Programmers Reference Guide bestie, and it's literally your whole guide to installing CPAN modules. no cap. let's go πŸ¦‹


✨ NAME ✨

perlmodinstall β€” installing CPAN modules, the whole vibe, start to finish πŸ’…


🌸 DESCRIPTION 🌸

so think of a module as the fundamental unit of reusable Perl code β€” peek at perlmod if you want the lore. whenever somebody writes a chunk of Perl code and is like "the world needs this", they register as a Perl developer at <https://www.cpan.org/modules/04pause.html> so they can upload their code to the CPAN. and the CPAN? that's the Comprehensive Perl Archive Network, accessible at <https://www.cpan.org/> and searchable at <https://metacpan.org/>. iconic, honestly. πŸ‘‘

this doc is for the girlies who want to download CPAN modules and install them on their own computer. that's you. you got this.

πŸŽ€ PREAMBLE πŸŽ€

first things first bestie β€” are you sure the module isn't already on your system?? like. check. try:

perl -MFoo -e 1

(replace Foo with the name of the module; for instance, perl -MCGI::Carp -e 1.)

no error message? you already have the module, slay, go home. (if you do see an error message, it's still possible you have the module, but that it's not in your path β€” you can display your path with perl -e "print qq(@INC)".) for the rest of this document we're gonna assume you really honestly truly lack an installed module, but have found it on the CPAN. 🫢

so now you have a file ending in .tar.gz (or, less often, .zip). you know there's a tasty module inside. there are four steps you must now take:

  1. DECOMPRESS the file
  2. UNPACK the file into a directory
  3. BUILD the module (sometimes unnecessary)
  4. INSTALL the module.

here's how to do each step for each operating system. and this is not a substitute for reading the README and INSTALL files that might have come with your module!! read those. fr fr.

also note that these instructions are tailored for installing the module into your system's repository of Perl modules, but you can install modules into any directory you wish. for instance, where it says perl Makefile.PL, you can substitute perl Makefile.PL PREFIX=/my/perl_directory to install the modules into /my/perl_directory. then you can use the modules from your Perl programs with:

use lib "/my/perl_directory/lib/site_perl";

or sometimes just:

use "/my/perl_directory";

if you're on a system that requires superuser/root access to install modules into the directories you see when you type perl -e "print qq(@INC)", you'll want to install them into a local directory (such as your home directory) and use this approach. lowkey the move.


  • if you're on a Unix or Unix-like system 🐧

you can use Andreas Koenig's CPAN module (<https://metacpan.org/release/CPAN>) to automate the following steps, from DECOMPRESS through INSTALL. automation is self care.

A. DECOMPRESS

decompress the file with:

gzip -d yourmodule.tar.gz

you can get gzip from <ftp://prep.ai.mit.edu/pub/gnu/>

or, you can combine this step with the next one to save disk space:

gzip -dc yourmodule.tar.gz | tar -xof -

B. UNPACK

unpack the result with:

tar -xof yourmodule.tar

C. BUILD

go into the newly-created directory and type:

perl Makefile.PL
make test

or:

perl Makefile.PL PREFIX=/my/perl_directory

to install it locally. (remember that if you do this, you'll have to put use lib "/my/perl_directory"; near the top of the program that is to use this module.)

D. INSTALL

while still in that directory, type:

make install

make sure you have the appropriate permissions to install the module in your Perl 5 library directory. often, you'll need to be root.

that's all you need to do on Unix systems with dynamic linking. most Unix systems have dynamic linking. if yours doesn't, or if for another reason you have a statically-linked perl, and the module requires compilation, you'll need to build a new Perl binary that includes the module. again, you'll probably need to be root. 😭

  • if you're running ActivePerl (Win95/98/2K/NT/XP, Linux, Solaris) πŸͺŸ

first, type ppm from a shell and see whether ActiveState's PPM repository has your module. if so, you can install it with ppm and you won't have to bother with any of the other steps here. ✨ you might be able to use the CPAN instructions from the "Unix or Linux" section above as well; give it a try. otherwise, you'll have to follow the steps below.

A. DECOMPRESS

you can use the open source 7-zip (<https://www.7-zip.org/>) or the shareware Winzip (<https://www.winzip.com>) to decompress and unpack modules.

B. UNPACK

if you used WinZip, this was already done for you. πŸ’…

C. BUILD

you'll need either nmake or gmake.

does the module require compilation (i.e. does it have files that end in .xs, .c, .h, .y, .cc, .cxx, or .C)? if it does, life is now officially tough for you, because you have to compile the module yourself (no easy feat on Windows). you'll need a compiler such as Visual C++. alternatively, you can download a pre-built PPM package from ActiveState:

http://aspn.activestate.com/ASPN/Downloads/ActivePerl/PPM/

go into the newly-created directory and type:

perl Makefile.PL
nmake test

D. INSTALL

while still in that directory, type:

nmake install
  • if you're on OS/2 πŸ’™

get the EMX development suite and gzip/tar from Hobbes (<http://hobbes.nmsu.edu/h-browse.php?dir=/pub/os2/dev/emx/v0.9d>), and then follow the instructions for Unix.

  • if you're on VMS πŸ¦‹

when downloading from CPAN, save your file with a .tgz extension instead of .tar.gz. all other periods in the filename should be replaced with underscores. for example, Your-Module-1.33.tar.gz should be downloaded as Your-Module-1_33.tgz.

A. DECOMPRESS

type:

gzip -d Your-Module.tgz

or, for zipped modules, type:

unzip Your-Module.zip

executables for gzip, zip, and VMStar:

http://www.hp.com/go/openvms/freeware/

and their source code:

http://www.fsf.org/order/ftp.html

note that GNU's gzip/gunzip is not the same as Info-ZIP's zip/unzip package. the former is a simple compression tool; the latter permits creation of multi-file archives. different vibes entirely.

B. UNPACK

if you're using VMStar:

VMStar xf Your-Module.tar

or, if you're fond of VMS command syntax:

tar/extract/verbose Your_Module.tar

C. BUILD

make sure you have MMS (from Digital) or the freeware MMK (available from MadGoat at <http://www.madgoat.com>). then type this to create the DESCRIP.MMS for the module:

perl Makefile.PL

now you're ready to build:

mms test

substitute mmk for mms above if you're using MMK.

D. INSTALL

type:

mms install

substitute mmk for mms above if you're using MMK.

  • if you're on MVS ⭐

introduce the .tar.gz file into an HFS as binary; don't translate from ASCII to EBCDIC.

A. DECOMPRESS

decompress the file with:

gzip -d yourmodule.tar.gz

you can get gzip from <http://www.s390.ibm.com/products/oe/bpxqp1.html>

B. UNPACK

unpack the result with:

pax -o to=IBM-1047,from=ISO8859-1 -r < yourmodule.tar

the BUILD and INSTALL steps are identical to those for Unix. some modules generate Makefiles that work better with GNU make, which is available from <http://www.mks.com/s390/gnu/>


🌈 PORTABILITY 🌈

heads up bestie β€” not all modules will work on all platforms. see perlport for more info on portability issues. read the documentation to see if the module will work on your system. there are basically three categories of modules that will not work "out of the box" with all platforms (with some possibility of overlap):

  • those that should, but don't. these need to be fixed; consider contacting the author and possibly writing a patch. be the change 🫢
  • those that need to be compiled, where the target platform doesn't have compilers readily available. (these modules contain .xs or .c files, usually.) you might be able to find existing binaries on the CPAN or elsewhere, or you might want to try getting compilers and building it yourself, and then release the binary for other poor souls to use.
  • those that are targeted at a specific platform. (such as the Win32:: modules.) if the module is targeted specifically at a platform other than yours, you're out of luck, most likely. πŸ’€

check the CPAN Testers if a module should work with your platform but it doesn't behave as you'd expect, or you aren't sure whether or not a module will work under your platform. if the module you want isn't listed there, you can test it yourself and let CPAN Testers know, you can join CPAN Testers, or you can request it be tested.

https://cpantesters.org/

πŸ’œ HEY πŸ’œ

if you have any suggested changes for this page, let me know. please don't send me mail asking for help on how to install your modules. there are too many modules, and too few Orwants, for me to be able to answer or even acknowledge all your questions. contact the module author instead, ask someone familiar with Perl on your operating system, or if all else fails, file a ticket at <https://rt.cpan.org/>. i'm begging πŸ™ˆ


πŸ‘‘ AUTHOR πŸ‘‘

Jon Orwant

orwant@medita.mit.edu

with invaluable help from Chris Nandor, and valuable help from Brandon Allbery, Charles Bailey, Graham Barr, Dominic Dunlop, Jarkko Hietaniemi, Ben Holzman, Tom Horsley, Nick Ing-Simmons, Tuomas J. Lukka, Laszlo Molnar, Alan Olsen, Peter Prymmer, Gurusamy Sarathy, Christoph Spalinger, Dan Sugalski, Larry Virden, and Ilya Zakharevich.

first version July 22, 1998; last revised November 21, 2001.


copyright (C) 1998, 2002, 2003 Jon Orwant. all rights reserved.

this document may be distributed under the same terms as Perl itself.


and that's the whole page bestie!! this one's from perl v5.42.3, dated 2026-08-03, and it's literally called PERLMODINSTALL(1) πŸ’– now go install something, you absolute icon βœ¨πŸ¦‹πŸ’…
πŸ“¦ where this page comes from