1PERLHPUX(1) Perl Programmers Reference Guide PERLHPUX(1)
2
6 README.hpux - Perl version 5 on Hewlett-Packard Unix (HP-UX) systems
7
9 This document describes various features of HP's Unix operating system
10 (HP-UX) that will affect how Perl version 5 (hereafter just Perl) is
11 compiled and/or runs.
12 Using perl as shipped with HP-UX
14 Application release September 2001, HP-UX 11.00 is the first to ship
16 with Perl. By the time it was perl-5.6.1 in /opt/perl. The first occur‐
17 rence is on CD 5012-7954 and can be installed using
18 swinstall -s /cdrom perl
20 assuming you have mounted that CD on /cdrom. In this version the fol‐
22 lowing modules were installed:
23 ActivePerl::DocTools-0.04 HTML::Parser-3.19 XML::DOM-1.25
25 Archive::Tar-0.072 HTML::Tagset-3.03 XML::Parser-2.27
26 Compress::Zlib-1.08 MIME::Base64-2.11 XML::Simple-1.05
27 Convert::ASN1-0.10 Net-1.07 XML::XPath-1.09
28 Digest::MD5-2.11 PPM-2.1.5 XML::XSLT-0.32
29 File::CounterFile-0.12 SOAP::Lite-0.46 libwww-perl-5.51
30 Font::AFM-1.18 Storable-1.011 libxml-perl-0.07
31 HTML-Tree-3.11 URI-1.11 perl-ldap-0.23
32 The build was a portable hppa-1.1 multithread build that supports large
34 files compiled with gcc-2.9-hppa-991112
35 If you perform a new installation, then Perl will be installed automat‐
37 ically.
38 More recent (preinstalled) HP-UX systems have more recent versions of
40 Perl and the updated modules.
41 Using perl from HP's porting centre
43 HP porting centre tries very hard to keep up with customer demand and
45 release updates from the Open Source community. Having precompiled Perl
46 binaries available is obvious.
47 The HP porting centres are limited in what systems they are allowed to
49 port to and they usually choose the two most recent OS versions avail‐
50 able. This means that at the moment of writing, there are only HP-UX
51 11.11 (pa-risc 2.0) and HP-UX 11.23 (Itanium 2) ports available on the
52 porting centres.
53 HP has asked the porting centre to move Open Source binaries from /opt
55 to /usr/local, so binaries produced since the start of July 2002 are
56 located in /usr/local.
57 One of HP porting centres URL's is http://hpux.connect.org.uk/ The port
59 currently available is built with GNU gcc.
60 Compiling Perl 5 on HP-UX
62 When compiling Perl, you must use an ANSI C compiler. The C compiler
64 that ships with all HP-UX systems is a K&R compiler that should only be
65 used to build new kernels.
66 Perl can be compiled with either HP's ANSI C compiler or with gcc. The
68 former is recommended, as not only can it compile Perl with no diffi‐
69 culty, but also can take advantage of features listed later that
70 require the use of HP compiler-specific command-line flags.
71 If you decide to use gcc, make sure your installation is recent and
73 complete, and be sure to read the Perl INSTALL file for more gcc-spe‐
74 cific details.
75 PA-RISC
77 HP's current Unix systems run on its own Precision Architecture
79 (PA-RISC) chip. HP-UX used to run on the Motorola MC68000 family of
80 chips, but any machine with this chip in it is quite obsolete and this
81 document will not attempt to address issues for compiling Perl on the
82 Motorola chipset.
83 The most recent version of PA-RISC at the time of this document's last
85 update is 2.0. HP PA-RISC systems are usually refered to with model
86 description "HP 9000".
87 A complete list of models at the time the OS was built is in the file
89 /usr/sam/lib/mo/sched.models. The first column corresponds to the last
90 part of the output of the "model" command. The second column is the
91 PA-RISC version and the third column is the exact chip type used.
92 (Start browsing at the bottom to prevent confusion ;-)
93 # model
95 9000/800/L1000-44
96 # grep L1000-44 /usr/sam/lib/mo/sched.models
97 L1000-44 2.0 PA8500
98 Portability Between PA-RISC Versions
100 An executable compiled on a PA-RISC 2.0 platform will not execute on a
102 PA-RISC 1.1 platform, even if they are running the same version of
103 HP-UX. If you are building Perl on a PA-RISC 2.0 platform and want
104 that Perl to also run on a PA-RISC 1.1, the compiler flags +DAportable
105 and +DS32 should be used.
106 It is no longer possible to compile PA-RISC 1.0 executables on either
108 the PA-RISC 1.1 or 2.0 platforms. The command-line flags are accepted,
109 but the resulting executable will not run when transferred to a PA-RISC
110 1.0 system.
111 PA-RISC 1.0
113 The original version of PA-RISC, HP no longer sells any system with
115 this chip.
116 The following systems contained PA-RISC 1.0 chips:
118 600, 635, 645, 808, 815, 822, 825, 832, 834, 835, 840, 842, 845, 850,
120 852, 855, 860, 865, 870, 890
121 PA-RISC 1.1
123 An upgrade to the PA-RISC design, it shipped for many years in many
125 different system.
126 The following systems contain with PA-RISC 1.1 chips:
128 705, 710, 712, 715, 720, 722, 725, 728, 730, 735, 742, 743, 744, 745,
130 747, 750, 755, 770, 777, 778, 779, 800, 801, 803, 806, 807, 809, 811,
131 813, 816, 817, 819, 821, 826, 827, 829, 831, 837, 839, 841, 847, 849,
132 851, 856, 857, 859, 867, 869, 877, 887, 891, 892, 897, A180, A180C,
133 B115, B120, B132L, B132L+, B160L, B180L, C100, C110, C115, C120,
134 C160L, D200, D210, D220, D230, D250, D260, D310, D320, D330, D350,
135 D360, D410, DX0, DX5, DXO, E25, E35, E45, E55, F10, F20, F30, G30,
136 G40, G50, G60, G70, H20, H30, H40, H50, H60, H70, I30, I40, I50, I60,
137 I70, J200, J210, J210XC, K100, K200, K210, K220, K230, K400, K410,
138 K420, S700i, S715, S744, S760, T500, T520
139 PA-RISC 2.0
141 The most recent upgrade to the PA-RISC design, it added support for
143 64-bit integer data.
144 As of the date of this document's last update, the following systems
146 contain PA-RISC 2.0 chips:
147 700, 780, 781, 782, 783, 785, 802, 804, 810, 820, 861, 871, 879, 889,
149 893, 895, 896, 898, 899, A400, A500, B1000, B2000, C130, C140, C160,
150 C180, C180+, C180-XP, C200+, C400+, C3000, C360, C3600, CB260, D270,
151 D280, D370, D380, D390, D650, J220, J2240, J280, J282, J400, J410,
152 J5000, J5500XM, J5600, J7000, J7600, K250, K260, K260-EG, K270, K360,
153 K370, K380, K450, K460, K460-EG, K460-XP, K470, K570, K580, L1000,
154 L2000, L3000, N4000, R380, R390, SD16000, SD32000, SD64000, T540,
155 T600, V2000, V2200, V2250, V2500, V2600
156 Just before HP took over Compaq, some systems were renamed. the link
158 that contained the explanation is dead, so here's a short summary:
159 HP 9000 A-Class servers, now renamed HP Server rp2400 series.
161 HP 9000 L-Class servers, now renamed HP Server rp5400 series.
162 HP 9000 N-Class servers, now renamed HP Server rp7400.
163 rp2400, rp2405, rp2430, rp2450, rp2470, rp3410, rp3440, rp4410,
165 rp4440, rp5400, rp5405, rp5430, rp5450, rp5470, rp7400, rp7405,
166 rp7410, rp7420, rp8400, rp8420, Superdome
167 The current naming convention is:
169 aadddd
171 ⎪⎪⎪⎪`+- 00 - 99 relative capacity & newness (upgrades, etc.)
172 ⎪⎪⎪`--- unique number for each architecture to ensure different
173 ⎪⎪⎪ systems do not have the same numbering across
174 ⎪⎪⎪ architectures
175 ⎪⎪`---- 1 - 9 identifies family and/or relative positioning
176 ⎪⎪
177 ⎪`----- c = ia32 (cisc)
178 ⎪ p = pa-risc
179 ⎪ x = ia-64 (Itanium & Itanium 2)
180 ⎪ h = housing
181 `------ t = tower
182 r = rack optimized
183 s = super scalable
184 b = blade
185 sa = appliance
186 Itanium Processor Family and HP-UX
188 HP-UX also runs on the new Itanium processor. This requires the use of
190 a different version of HP-UX (currently 11.23 or 11i v2), and with the
191 exception of a few differences detailed below and in later sections,
192 Perl should compile with no problems.
193 Although PA-RISC binaries can run on Itanium systems, you should not
195 attempt to use a PA-RISC version of Perl on an Itanium system. This is
196 because shared libraries created on an Itanium system cannot be loaded
197 while running a PA-RISC executable.
198 HP Itanium 2 systems are usually refered to with model description "HP
200 Integrity".
201 Itanium & Itanium 2
203 HP also ships servers with the 128-bit Itanium processor(s). As of the
205 date of this document's last update, the following systems contain Ita‐
206 nium or Itanium 2 chips (this is very likely to be out of date):
207 BL60p, rx1600, rx1620, rx2600, rx2600hptc, rx2620, rx4610, rx4640,
209 rx5670, rx7620, rx8620, rx9610
210 To see all about your machine, type
212 # model
214 ia64 hp server rx2600
215 # /usr/contrib/bin/machinfo
216 Building Dynamic Extensions on HP-UX
218 HP-UX supports dynamically loadable libraries (shared libraries).
220 Shared libraries end with the suffix .sl. On Itanium systems, they end
221 with the suffix .so.
222 Shared libraries created on a platform using a particular PA-RISC ver‐
224 sion are not usable on platforms using an earlier PA-RISC version by
225 default. However, this backwards compatibility may be enabled using
226 the same +DAportable compiler flag (with the same PA-RISC 1.0 caveat
227 mentioned above).
228 Shared libraries created on an Itanium platform cannot be loaded on a
230 PA-RISC platform. Shared libraries created on a PA-RISC platform can
231 only be loaded on an Itanium platform if it is a PA-RISC executable
232 that is attempting to load the PA-RISC library. A PA-RISC shared
233 library cannot be loaded into an Itanium executable nor vice-versa.
234 To create a shared library, the following steps must be performed:
236 1. Compile source modules with +z or +Z flag to create a .o module
238 which contains Position-Independent Code (PIC). The linker will
239 tell you in the next step if +Z was needed.
240 (For gcc, the appropriate flag is -fpic or -fPIC.)
241 2. Link the shared library using the -b flag. If the code calls
243 any functions in other system libraries (e.g., libm), it must
244 be included on this line.
245 (Note that these steps are usually handled automatically by the exten‐
247 sion's Makefile).
248 If these dependent libraries are not listed at shared library creation
250 time, you will get fatal "Unresolved symbol" errors at run time when
251 the library is loaded.
252 You may create a shared library that refers to another library, which
254 may be either an archive library or a shared library. If this second
255 library is a shared library, this is called a "dependent library". The
256 dependent library's name is recorded in the main shared library, but it
257 is not linked into the shared library. Instead, it is loaded when the
258 main shared library is loaded. This can cause problems if you build an
259 extension on one system and move it to another system where the
260 libraries may not be located in the same place as on the first system.
261 If the referred library is an archive library, then it is treated as a
263 simple collection of .o modules (all of which must contain PIC). These
264 modules are then linked into the shared library.
265 Note that it is okay to create a library which contains a dependent
267 library that is already linked into perl.
268 Some extensions, like DB_File and Compress::Zlib use/require prebuilt
270 libraries for the perl extensions/modules to work. If these libraries
271 are built using the default configuration, it might happen that you run
272 into an error like "invalid loader fixup" during load phase. HP is
273 aware of this problem. Search the HP-UX cxx-dev forums for discussions
274 about the subject. The short answer is that everything (all libraries,
275 everything) must be compiled with "+z" or "+Z" to be PIC (position
276 independent code). (For gcc, that would be "-fpic" or "-fPIC"). In
277 HP-UX 11.00 or newer the linker error message should tell the name of
278 the offending object file.
279 A more general approach is to intervene manually, as with an example
281 for the DB_File module, which requires SleepyCat's libdb.sl:
282 # cd .../db-3.2.9/build_unix
284 # vi Makefile
285 ... add +Z to all cflags to create shared objects
286 CFLAGS= -c $(CPPFLAGS) +Z -Ae +O2 +Onolimit \
287 -I/usr/local/include -I/usr/include/X11R6
288 CXXFLAGS= -c $(CPPFLAGS) +Z -Ae +O2 +Onolimit \
289 -I/usr/local/include -I/usr/include/X11R6
290 # make clean
292 # make
293 # mkdir tmp
294 # cd tmp
295 # ar x ../libdb.a
296 # ld -b -o libdb-3.2.sl *.o
297 # mv libdb-3.2.sl /usr/local/lib
298 # rm *.o
299 # cd /usr/local/lib
300 # rm -f libdb.sl
301 # ln -s libdb-3.2.sl libdb.sl
302 # cd .../DB_File-1.76
304 # make distclean
305 # perl Makefile.PL
306 # make
307 # make test
308 # make install
309 As of db-4.2.x it is no longer needed to do this by hand. Sleepycat has
311 changed the configuration process to add +z on HP-UX automatically.
312 # cd .../db-4.2.25/build_unix
314 # env CFLAGS=+DA2.0w LDFLAGS=+DA2.0w ../dist/configure
315 should work to generate 64bit shared libraries for HP-UX 11.00 and 11i.
317 It is no longer possible to link PA-RISC 1.0 shared libraries (even
319 though the command-line flags are still present).
320 PA-RISC and Itanium object files are not interchangeable. Although you
322 may be able to use ar to create an archive library of PA-RISC object
323 files on an Itanium system, you cannot link against it using an Itanium
324 link editor.
325 The HP ANSI C Compiler
327 When using this compiler to build Perl, you should make sure that the
329 flag -Aa is added to the cpprun and cppstdin variables in the config.sh
330 file (though see the section on 64-bit perl below). If you are using a
331 recent version of the Perl distribution, these flags are set automati‐
332 cally.
333 The GNU C Compiler
335 When you are going to use the GNU C compiler (gcc), and you don't have
337 gcc yet, you can either build it yourself from the sources (available
338 from e.g. http://www.gnu.ai.mit.edu/software/gcc/releases.html) or
339 fetch a prebuilt binary from the HP porting center. There are two
340 places where gcc prebuilds can be fetched; the first and best (for HP-
341 UX 11 only) is http://h21007.www2.hp.com/dspp/tech/tech_TechSoftwareDe‐
342 tailPage_IDX/1,1703,547,00.html the second is
343 http://hpux.cs.utah.edu/hppd/hpux/Gnu/ where you can also find the GNU
344 binutils package. (Browse through the list, because there are often
345 multiple versions of the same package available).
346 Above mentioned distributions are depots. H.Merijn Brand has made pre‐
348 built gcc binaries available on http://mirrors.develooper.com/hpux/
349 and/or http://www.cmve.net/~merijn/ for HP-UX 10.20, HP-UX 11.00, and
350 HP-UX 11.11 (HP-UX 11i) in both 32- and 64-bit versions. These are
351 bzipped tar archives that also include recent GNU binutils and GNU gdb.
352 Read the instructions on that page to rebuild gcc using itself.
353 On PA-RISC you need a different compiler for 32-bit applications and
355 for 64-bit applications. On PA-RISC, 32-bit objects and 64-bit objects
356 do not mix. Period. There is no different behaviour for HP C-ANSI-C or
357 GNU gcc. So if you require your perl binary to use 64-bit libraries,
358 like Oracle-64bit, you MUST build a 64-bit perl.
359 Building a 64-bit capable gcc on PA-RISC from source is possible only
361 when you have the HP C-ANSI C compiler or an already working 64-bit
362 binary of gcc available. Best performance for perl is achieved with
363 HP's native compiler.
364 Using Large Files with Perl on HP-UX
366 Beginning with HP-UX version 10.20, files larger than 2GB (2^31 bytes)
368 may be created and manipulated. Three separate methods of doing this
369 are available. Of these methods, the best method for Perl is to com‐
370 pile using the -Duselargefiles flag to Configure. This causes Perl to
371 be compiled using structures and functions in which these are 64 bits
372 wide, rather than 32 bits wide. (Note that this will only work with
373 HP's ANSI C compiler. If you want to compile Perl using gcc, you will
374 have to get a version of the compiler that supports 64-bit operations.
375 See above for where to find it.)
376 There are some drawbacks to this approach. One is that any extension
378 which calls any file-manipulating C function will need to be recompiled
379 (just follow the usual "perl Makefile.PL; make; make test; make
380 install" procedure).
381 The list of functions that will need to recompiled is:
383 creat, fgetpos, fopen, freopen, fsetpos, fstat,
384 fstatvfs, fstatvfsdev, ftruncate, ftw, lockf, lseek,
385 lstat, mmap, nftw, open, prealloc, stat,
386 statvfs, statvfsdev, tmpfile, truncate, getrlimit, setrlimit
387 Another drawback is only valid for Perl versions before 5.6.0. This
389 drawback is that the seek and tell functions (both the builtin version
390 and POSIX module version) will not perform correctly.
391 It is strongly recommended that you use this flag when you run Config‐
393 ure. If you do not do this, but later answer the question about large
394 files when Configure asks you, you may get a configuration that cannot
395 be compiled, or that does not function as expected.
396 Threaded Perl on HP-UX
398 It is possible to compile a version of threaded Perl on any version of
400 HP-UX before 10.30, but it is strongly suggested that you be running on
401 HP-UX 11.00 at least.
402 To compile Perl with threads, add -Dusethreads to the arguments of Con‐
404 figure. Verify that the -D_POSIX_C_SOURCE=199506L compiler flag is
405 automatically added to the list of flags. Also make sure that
406 -lpthread is listed before -lc in the list of libraries to link Perl
407 with. The hints provided for HP-UX during Configure will try very hard
408 to get this right for you.
409 HP-UX versions before 10.30 require a separate installation of a POSIX
411 threads library package. Two examples are the HP DCE package, available
412 on "HP-UX Hardware Extensions 3.0, Install and Core OS, Release 10.20,
413 April 1999 (B3920-13941)" or the Freely available PTH package, avail‐
414 able on H.Merijn's site (http://mirrors.develooper.com/hpux/).
415 If you are going to use the HP DCE package, the library used for
417 threading is /usr/lib/libcma.sl, but there have been multiple updates
418 of that library over time. Perl will build with the first version, but
419 it will not pass the test suite. Older Oracle versions might be a com‐
420 pelling reason not to update that library, otherwise please find a
421 newer version in one of the following patches: PHSS_19739, PHSS_20608,
422 or PHSS_23672
423 reformatted output:
425 d3:/usr/lib 106 > what libcma-*.1
427 libcma-00000.1:
428 HP DCE/9000 1.5 Module: libcma.sl (Export)
429 Date: Apr 29 1996 22:11:24
430 libcma-19739.1:
431 HP DCE/9000 1.5 PHSS_19739-40 Module: libcma.sl (Export)
432 Date: Sep 4 1999 01:59:07
433 libcma-20608.1:
434 HP DCE/9000 1.5 PHSS_20608 Module: libcma.1 (Export)
435 Date: Dec 8 1999 18:41:23
436 libcma-23672.1:
437 HP DCE/9000 1.5 PHSS_23672 Module: libcma.1 (Export)
438 Date: Apr 9 2001 10:01:06
439 d3:/usr/lib 107 >
440 If you choose for the PTH package, use swinstall to install pth in the
442 default location (/opt/pth), and then make symbolic links to the
443 libraries from /usr/lib
444 # cd /usr/lib
446 # ln -s /opt/pth/lib/libpth* .
447 For building perl to support Oracle, it needs to be linked with libcl
449 and libpthread. So even if your perl is an unthreaded build, these
450 libraries might be required. See "Oracle on HP-UX" below.
451 64-bit Perl on HP-UX
453 Beginning with HP-UX 11.00, programs compiled under HP-UX can take
455 advantage of the LP64 programming environment (LP64 means Longs and
456 Pointers are 64 bits wide), in which scalar variables will be able to
457 hold numbers larger than 2^32 with complete precision. Perl has proven
458 to be consistent and reliable in 64bit mode since 5.8.1 on all HP-UX
459 11.xx.
460 As of the date of this document, Perl is fully 64-bit compliant on HP-
462 UX 11.00 and up for both cc- and gcc builds. If you are about to build
463 a 64-bit perl with GNU gcc, please read the gcc section carefully.
464 Should a user have the need for compiling Perl in the LP64 environment,
466 use the -Duse64bitall flag to Configure. This will force Perl to be
467 compiled in a pure LP64 environment (with the +DD64 flag for HP
468 C-ANSI-C, with no additional options for GNU gcc 64-bit on PA-RISC, and
469 with -mlp64 for GNU gcc on Itanium). If you want to compile Perl using
470 gcc, you will have to get a version of the compiler that supports
471 64-bit operations.)
472 You can also use the -Duse64bitint flag to Configure. Although there
474 are some minor differences between compiling Perl with this flag versus
475 the -Duse64bitall flag, they should not be noticeable from a Perl
476 user's perspective. When configuring -Duse64bitint using a 64bit gcc on
477 a pa-risc architecture, -Duse64bitint is silently promoted to
478 -Duse64bitall.
479 In both cases, it is strongly recommended that you use these flags when
481 you run Configure. If you do not use do this, but later answer the
482 questions about 64-bit numbers when Configure asks you, you may get a
483 configuration that cannot be compiled, or that does not function as
484 expected.
485 Oracle on HP-UX
487 Using perl to connect to Oracle databases through DBI and DBD::Oracle
489 has caused a lot of people many headaches. Read README.hpux in the
490 DBD::Oracle for much more information. The reason to mention it here is
491 that Oracle requires a perl built with libcl and libpthread, the latter
492 even when perl is build without threads. Building perl using all
493 defaults, but still enabling to build DBD::Oracle later on can be
494 achieved using
495 Configure -A prepend:libswanted='cl pthread ' ...
497 Do not forget the space before the trailing quote.
499 Also note that this does not (yet) work with all configurations, it is
501 known to fail with 64-bit versions of GCC.
502 GDBM and Threads on HP-UX
504 If you attempt to compile Perl with threads on an 11.X system and also
506 link in the GDBM library, then Perl will immediately core dump when it
507 starts up. The only workaround at this point is to relink the GDBM
508 library under 11.X, then relink it into Perl.
509 NFS filesystems and utime[1m(2) on HP-UX
511 If you are compiling Perl on a remotely-mounted NFS filesystem, the
513 test io/fs.t may fail on test #18. This appears to be a bug in HP-UX
514 and no fix is currently available.
515 perl -P and // and HP-UX
517 If HP-UX Perl is compiled with flags that will cause problems if the -P
519 flag of Perl (preprocess Perl code with the C preprocessor before perl
520 sees it) is used. The problem is that "//", being a C++-style until-
521 end-of-line comment, will disappear along with the remainder of the
522 line. This means that common Perl constructs like
523 s/foo//;
525 will turn into illegal code
527 s/foo
529 The workaround is to use some other quoting separator than "/", like
531 for example "!":
532 s!foo!!;
534 HP-UX Kernel Parameters (maxdsiz) for Compiling Perl
536 By default, HP-UX comes configured with a maximum data segment size of
538 64MB. This is too small to correctly compile Perl with the maximum
539 optimization levels. You can increase the size of the maxdsiz kernel
540 parameter through the use of SAM.
541 When using the GUI version of SAM, click on the Kernel Configuration
543 icon, then the Configurable Parameters icon. Scroll down and select
544 the maxdsiz line. From the Actions menu, select the Modify Config‐
545 urable Parameter item. Insert the new formula into the Formula/Value
546 box. Then follow the instructions to rebuild your kernel and reboot
547 your system.
548 In general, a value of 256MB (or "256*1024*1024") is sufficient for
550 Perl to compile at maximum optimization.
551
553 You may get a bus error core dump from the op/pwent or op/grent tests.
554 If compiled with -g you will see a stack trace much like the following:
555 #0 0xc004216c in () from /usr/lib/libc.2
557 #1 0xc00d7550 in __nss_src_state_destr () from /usr/lib/libc.2
558 #2 0xc00d7768 in __nss_src_state_destr () from /usr/lib/libc.2
559 #3 0xc00d78a8 in nss_delete () from /usr/lib/libc.2
560 #4 0xc01126d8 in endpwent () from /usr/lib/libc.2
561 #5 0xd1950 in Perl_pp_epwent () from ./perl
562 #6 0x94d3c in Perl_runops_standard () from ./perl
563 #7 0x23728 in S_run_body () from ./perl
564 #8 0x23428 in perl_run () from ./perl
565 #9 0x2005c in main () from ./perl
566 The key here is the "nss_delete" call. One workaround for this bug
568 seems to be to create add to the file /etc/nsswitch.conf (at least) the
569 following lines
570 group: files
572 passwd: files
573 Whether you are using NIS does not matter. Amazingly enough, the same
575 bug also affects Solaris.
576
578 Jeff Okamoto <okamoto@corp.hp.com> H.Merijn Brand <h.m.brand@xs4all.nl>
579 With much assistance regarding shared libraries from Marc Sabatella.
581
583 Version 0.7.6: 2005-12-20
584perl v5.8.8 2006-01-07 PERLHPUX(1)