HTTPS clone URL
Subversion checkout URL
Perl C Shell Prolog C++ Objective-C
blead briandfoy/english briandfoy/perlexperiment briandfoy/perlfaq briandfoy/poddupes briandfoy/slashN chip/bind2 chip/view2 chip/5.14.1-docs dagolden/install-stripped dual/Safe greerga/cygwin_g++ maint-1.0 maint-5.004 maint-5.005 maint-5.6 maint-5.8 maint-5.10 maint-5.12 maint-5.14 mauve merijn/useperlio nicholas/arenas rafl/ld_export smoke-me/Shut-It! smoke-me/arenas smoke-me/avar/useperlio smoke-me/blead smoke-me/cpan smoke-me/eu_typemap smoke-me/greerga/cygwin_g++ smoke-me/gsoc-pod smoke-me/inet_aton smoke-me/khw-inversions smoke-me/ld_export smoke-me/nan_inf_str smoke-me/podcheck3 smoke-me/rafl/pod-in-dists smoke-me/remove_qw_hack smoke-me/runperl smoke-me/the-late-tmpgv smueller/eu_typemap smueller/perllocal_eucmd smueller/perllocal smueller/strictpxs_fixups tonyc/cygwin-rebase tonyc/staticcwd tux/5.8-dor vadim/cross zefram/fake_first_line zefram/gvsv_empty zefram/pad_api zefram/remove_qw_hack
Nothing to show
Nothing to show
Fetching latest commit...
Cannot retrieve the latest commit at this time.
|Failed to load latest commit information.|
Perl Kit, Version 2.0 Copyright (c) 1988, Larry Wall You may copy the perl kit in whole or in part as long as you don't try to make money off it, or pretend that you wrote it. -------------------------------------------------------------------------- Perl is a language that combines some of the features of C, sed, awk and shell. See the manual page for more hype. Perl will probably not run on machines with a small address space. Please read all the directions below before you proceed any further, and then follow them carefully. Failure to do so may void your warranty. :-) After you have unpacked your kit, you should have all the files listed in MANIFEST. Installation 1) Run Configure. This will figure out various things about your system. Some things Configure will figure out for itself, other things it will ask you about. It will then proceed to make config.h, config.sh, and Makefile. You might possibly have to trim # comments from the front of Configure if your sh doesn't handle them, but all other # comments will be taken care of. (If you don't have sh, you'll have to copy the sample file config.H to config.h and edit the config.h to reflect your system's peculiarities.) 2) Glance through config.h to make sure system dependencies are correct. Most of them should have been taken care of by running the Configure script. If you have any additional changes to make to the C definitions, they can be done in the Makefile, or in config.h. Bear in mind that they will get undone next time you run Configure. 3) make depend This will look for all the includes and modify Makefile accordingly. Configure will offer to do this for you. 4) make This will attempt to make perl in the current directory. 5) make test This will run the regression tests on the perl you just made. If it doesn't say "All tests successful" then something went wrong. See the README in the t subdirectory. Note that you can't run it in background if this disables opening of /dev/tty. If in doubt, just cd to the t directory and run TEST by hand. 6) make install This will put perl into a public directory (normally /usr/local/bin). It will also try to put the man pages in a reasonable place. It will not nroff the man page, however. You may need to be root to do this. If you are not root, you must own the directories in question and you should ignore any messages about chown not working. 7) Read the manual entry before running perl. 8) Go down to the x2p directory and do a "make depend, a "make" and a "make install" to create the awk to perl and sed to perl translators. 9) IMPORTANT! Help save the world! Communicate any problems and suggested patches to me, email@example.com (Larry Wall), so we can keep the world in sync. If you have a problem, there's someone else out there who either has had or will have the same problem. If possible, send in patches such that the patch program will apply them. Context diffs are the best, then normal diffs. Don't send ed scripts-- I've probably changed my copy since the version you have. Watch for perl patches in comp.sources.bugs. Patches will generally be in a form usable by the patch program. If you are just now bringing up perl and aren't sure how many patches there are, write to me and I'll send any you don't have. Your current patch level is shown in patchlevel.h.