summaryrefslogtreecommitdiff
path: root/NOTES.PERL
diff options
context:
space:
mode:
authorMatt Caswell <matt@openssl.org>2016-06-02 11:09:13 +0100
committerMatt Caswell <matt@openssl.org>2016-06-03 17:10:16 +0100
commit073b1b72f61d81f3cf8bc1728d35f9e7e734bbd2 (patch)
treee5f0be095b2abfce1ac89a4463d66c1151b97e9b /NOTES.PERL
parent8c4f8039df25c930f9120eca4ccd9cfd225ad7ef (diff)
downloadopenssl-new-073b1b72f61d81f3cf8bc1728d35f9e7e734bbd2.tar.gz
Tweaks to NOTES.PERL
Fix some typos and other minor amendments to NOTES.PERL. Reviewed-by: Rich Salz <rsalz@openssl.org> Reviewed-by: Richard Levitte <levitte@openssl.org>
Diffstat (limited to 'NOTES.PERL')
-rw-r--r--NOTES.PERL9
1 files changed, 5 insertions, 4 deletions
diff --git a/NOTES.PERL b/NOTES.PERL
index eda812dc8e..46d585acca 100644
--- a/NOTES.PERL
+++ b/NOTES.PERL
@@ -35,7 +35,8 @@
MinGW and Cygwin. The key recommendation is to use "matching" Perl,
one that matches build environment. For example, if you will build
on Cygwin be sure to use the Cygwin package manager to install Perl.
- For VC-* builds we recommend ActiveState Perl, available from
+ For MSYS builds use the MSYS provided Perl. For VC-* builds we
+ recommend ActiveState Perl, available from
http://www.activestate.com/ActivePerl.
Notes on Perl on VMS
@@ -43,7 +44,7 @@
You will need to install Perl separately. One way to do so is to
download the source from http://perl.org/, unpacking it, reading
- README.vms and follow instructions. Another way is to download a
+ README.vms and follow the instructions. Another way is to download a
.PCSI file from http://www.vmsperl.com/ and install it using the
POLYCENTER install tool.
@@ -99,9 +100,9 @@
$ cpan -i Text::Template
- Note that this runs all the tests that the module to be install
+ Note that this runs all the tests that the module to be installed
comes with. This is usually a smooth operation, but there are
- platforms where a failure is indicate even though the actual tests
+ platforms where a failure is indicated even though the actual tests
were successful. Should that happen, you can force an
installation regardless (that should be safe since you've already
seen the tests succeed!):