diff options
| author | Raphael Manfredi <Raphael_Manfredi@grenoble.hp.com> | 1997-03-06 14:10:38 +0100 |
|---|---|---|
| committer | Chip Salzenberg <chip@atlantic.net> | 1997-03-01 18:40:49 +1200 |
| commit | 385588b3949e695a02c8ea1dd00fe789d6044de3 (patch) | |
| tree | 3ee9ff5bd5715756399a102b042284ec5e88881b /INSTALL | |
| parent | 1db9566f513791929f1e21e86206e5669d5b11c2 (diff) | |
| download | perl-385588b3949e695a02c8ea1dd00fe789d6044de3.tar.gz | |
HP-UX hint update
Quoting Chip Salzenberg:
:If you have a second, please look them over and see if anything
:important is out or anything broken is in.
I don't see my hint/hpux.sh patch. Here it is again (in unified format
this time):
p5p-msgid: 1479.857653838@lyon.grenoble.hp.com
Diffstat (limited to 'INSTALL')
| -rw-r--r-- | INSTALL | 9 |
1 files changed, 4 insertions, 5 deletions
@@ -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 Note (probably harmless): No library found for -lsomething +=item Warning (will try anyway): No library found for -lposix 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,14 +987,13 @@ 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 phrase 'probably harmless' is intended to -reassure you that nothing unusual is happening, and the build -process is continuing. +they don't have. The message 'will try anyway' is intended to +reassure you that the 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 (will try anyway): 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 |