summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDavid Mitchell <davem@iabyn.com>2014-12-17 15:17:35 +0000
committerDavid Mitchell <davem@iabyn.com>2014-12-17 15:17:35 +0000
commit44666fef8c2d4d5d8a9d01c027a377274e7c4f96 (patch)
tree299922bdd7b424f01535004d32b36aaf23575339
parent03b8f76dbe4c5bcb3ddb28509a7b21c1ab4af848 (diff)
downloadperl-44666fef8c2d4d5d8a9d01c027a377274e7c4f96.tar.gz
INSTALL: warning text has changed
Some text tells you about Note (probably harmless): No library found for -lsomething warnings, but the actual warning has now changed to Warning (mostly harmless): No library found for -lsomething
-rw-r--r--INSTALL6
1 files changed, 3 insertions, 3 deletions
diff --git a/INSTALL b/INSTALL
index 46d3c12bca..95ffb12e2e 100644
--- a/INSTALL
+++ b/INSTALL
@@ -1687,7 +1687,7 @@ error, as the header file is broken. There are two ways to deal with this
-extern int dbmclose __P((DBM *));
+extern int dbmclose __P((void));
-=item Note (probably harmless): No library found for -lsomething
+=item Warning (mostly 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),
@@ -1695,13 +1695,13 @@ then don't worry about the warning message. The extension
Makefile.PL goes looking for various libraries needed on various
systems; few systems will need all the possible libraries listed.
Most users will see warnings for the ones they don't have. The
-phrase 'probably harmless' is intended to reassure you that nothing
+phrase 'mostly 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
- Note (probably harmless): No library found for -lgdbm
+ Warning (mostly 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