summaryrefslogtreecommitdiff
path: root/INSTALL
diff options
context:
space:
mode:
authorChip Salzenberg <chip@perl.com>1997-03-01 05:28:12 +1200
committerChip Salzenberg <chip@atlantic.net>1997-03-01 18:40:49 +1200
commitf8b3e957194312420089105d39c0b37773519523 (patch)
tree51febe6e0703cf92da9c9e8f65c73412600cb511 /INSTALL
parent9158562d45c9c138456404fd25cc877b5bd3746f (diff)
downloadperl-f8b3e957194312420089105d39c0b37773519523.tar.gz
Change 'continuing anyway' to 'probably harmless'
Diffstat (limited to 'INSTALL')
-rw-r--r--INSTALL9
1 files changed, 5 insertions, 4 deletions
diff --git a/INSTALL b/INSTALL
index 25069c91ff..470acfccbe 100644
--- a/INSTALL
+++ b/INSTALL
@@ -978,7 +978,7 @@ specific rule.
SCO prior to 3.2.4 may be missing dbmclose(). An upgrade to 3.2.4
that includes libdbm.nfs (which includes dbmclose()) may be available.
-=item Warning (will try anyway): No library found for -lposix
+=item Note (probably harmless): No library found for -lsomething
If you see such a message during the building of an extension, but
the extension passes its tests anyway (see L<"make test"> below),
@@ -987,13 +987,14 @@ Makefile.PL goes looking for various libraries needed on various
systems; few systems will need all the possible libraries listed.
For example, a system may have -lcposix or -lposix, but it's
unlikely to have both, so most users will see warnings for the one
-they don't have. The message 'will try anyway' is intended to
-reassure you that the process is continuing.
+they don't have. The phrase 'probably harmless' is intended to
+reassure you that nothing unusual is happening, and the build
+process is continuing.
On the other hand, if you are building GDBM_File and you get the
message
- Warning (will try anyway): No library found for -lgdbm
+ Note (probably harmless): No library found for -lgdbm
then it's likely you're going to run into trouble somewhere along
the line, since it's hard to see how you can use the GDBM_File