Re: port-alpha/17926 (perl 5.6.1 test generates core dump)

[Ray Phillips <r.phillips%uq.edu.au@localhost>]

The following reply was made to PR port-alpha/17926; it has been noted by GNATS.

From: Ray Phillips <r.phillips%uq.edu.au@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: 
Subject: Re: port-alpha/17926 (perl 5.6.1 test generates core dump)
Date: Wed, 5 Aug 2009 16:40:25 +1000

 >Synopsis: perl 5.6.1 test generates core dump
 >
 >State-Changed-From-To: open->feedback
 >State-Changed-By: dholland%NetBSD.org@localhost
 >State-Changed-When: Sat, 25 Jul 2009 06:36:09 +0000
 >State-Changed-Why:
 >Is this still an issue with gcc4?
 
 
 No, I tried to install it on a fresh NetBSD/alpha 5.0 installation 
 and it failed with a different error:
 
 
 % uname -a
 NetBSD xp1000 5.0 NetBSD 5.0 (GENERIC-$Revision: 1.325 $) #0: Sun Apr 
 26 06:39:06 UTC 2009 
 
builds%b4.netbsd.org@localhost:/home/builds/ab/netbsd-5-0-RELEASE/alpha/200904260229Z-obj/home/builds/ab/netbsd-5-0-RELEASE/src/sys/arch/alpha/compile/GENERIC
 
 alpha
 %
 % pwd
 /usr/home/ray/installers/perl/5.6.1/perl-5.6.1
 %
 % sh Configure
 
 Beginning of configuration questions for perl5.
 
 Checking echo to see how to suppress newlines...
 ...using -n.
 The star should be here-->*
 
 First let's make sure your kit is complete.  Checking...
 Looks good...
 
 
 This installation shell script will examine your system and ask you questions
 to determine how the perl5 package should be installed. If you get
 stuck on a question, you may use a ! shell escape to start a subshell or
 execute a command.  Many of the questions will have default answers in square
 brackets; typing carriage return will give you the default.
 
 On some of the questions which ask for file or directory names you are allowed
 to use the ~name construct to specify the login directory belonging to "name",
 even if you don't have a shell which knows about that.  Questions where this is
 allowed will be marked "(~name ok)".
 
 [Type carriage return to continue]
 
 The prompter used in this script allows you to use shell variables and
 backticks in your answers.  You may use $1, $2, etc...  to refer to the words
 in the default answer, as if the default line was a set of arguments given to a
 script shell.  This means you may also use $* to repeat the whole default line,
 so you do not have to re-type everything to add something to the default.
 
 Everytime there is a substitution, you will have to confirm.  If there is an
 error (e.g. an unmatched backtick), the default answer will remain unchanged
 and you will be prompted again.
 
 If you are in a hurry, you may run 'Configure -d'.  This will bypass nearly all
 the questions and use the computed defaults (or the previous answers if there
 was already a config.sh file). Type 'Configure -h' for a list of options.
 You may also start interactively and then answer '& -d' at any prompt to turn
 on the non-interactive behaviour for the remainder of the execution.
 
 [Type carriage return to continue]
 
 Much effort has been expended to ensure that this shell script will run on any
 Unix system.  If despite that it blows up on yours, your best bet is to edit
 Configure and run it again.  If you can't run Configure for some reason,
 you'll have to generate a config.sh file by hand.  Whatever problems you
 have, let me (perlbug%perl.org@localhost) know how I blew it.
 
 This installation script affects things in two ways:
 
 1) it may do direct variable substitutions on some of the files included
     in this kit.
 2) it builds a config.h file for inclusion in C programs.  You may edit
     any of these files as the need arises after running this script.
 
 If you make a mistake on a question, there is no easy way to back up to it
 currently.  The easiest thing to do is to edit config.sh and rerun all the SH
 files.  Configure will offer to let you do this before it runs the SH files.
 
 [Type carriage return to continue]
 
 Locating common programs...
 awk is in /usr/bin/awk.
 cat is in /bin/cat.
 comm is in /usr/bin/comm.
 cp is in /bin/cp.
 echo is in /bin/echo.
 expr is in /bin/expr.
 grep is in /usr/bin/grep.
 ls is in /bin/ls.
 make is in /usr/bin/make.
 mkdir is in /bin/mkdir.
 rm is in /bin/rm.
 sed is in /usr/bin/sed.
 sort is in /usr/bin/sort.
 touch is in /usr/bin/touch.
 tr is in /usr/bin/tr.
 uniq is in /usr/bin/uniq.
 
 Don't worry if any of the following aren't found...
 I don't see Mcc out there, offhand.
 ar is in /usr/bin/ar.
 I don't see bison out there, either.
 I don't see byacc out there, either.
 cpp is in /usr/bin/cpp.
 csh is in /bin/csh.
 date is in /bin/date.
 egrep is in /usr/bin/egrep.
 gzip is in /usr/bin/gzip.
 less is in /usr/bin/less.
 ln is in /bin/ln.
 more is in /usr/bin/more.
 nm is in /usr/bin/nm.
 nroff is in /usr/bin/nroff.
 I don't see pg out there, either.
 test is in /bin/test.
 uname is in /usr/bin/uname.
 I don't see zip out there, either.
 Using the test built into your sh.
 Using the test built into your sh.
 
 Checking compatibility between /bin/echo and builtin echo (if any)...
 They are compatible.  In fact, they may be identical.
 
 Symbolic links are supported.
 
 Checking how to test for symbolic links...
 You can test for symbolic links with 'test -h'.
 
 
 Good, your tr supports [:lower:] and [:upper:] to convert case.
 Using [:upper:] and [:lower:] to convert case.
 
 First time through, eh?  I have some defaults handy for some systems
 that need some extra help getting the Configure answers right:
 
 3b1             dynix           isc             nonstopux       stellar
 aix             dynixptx        isc_2           openbsd         sunos_4_0
 altos486        epix            linux           opus            sunos_4_1
 amigaos         esix4           lynxos          os2             svr4
 apollo          fps             machten         os390           svr5
 aux_3           freebsd         machten_2       posix-bc        ti1500
 beos            genix           mint            powerux         titanos
 bsdos           gnu             mips            qnx             ultrix_4
 convexos        greenhills      mpc             rhapsody        umips
 cxux            hpux            mpeix           sco             unicos
 cygwin          i386            ncr_tower       sco_2_3_0       unicosmk
 darwin          irix_4          netbsd          sco_2_3_1       unisysdynix
 dcosx           irix_5          newsos4         sco_2_3_2       utekv
 dec_osf         irix_6          next_3          sco_2_3_3       uts
 dgux            irix_6_0        next_3_0        sco_2_3_4       uwin
 dos_djgpp       irix_6_1        next_4          solaris_2       vmesa
 
 You may give one or more space-separated answers, or "none" if appropriate.
 A well-behaved OS will have no hints, so answering "none" or just "Policy"
 is a good thing.  DO NOT give a wrong version or a wrong OS.
 
 Which of these apply, if any? [netbsd]
 
 Configure uses the operating system name and version to set some defaults.
 The default value is probably right if the name rings a bell. Otherwise,
 since spelling matters for me, either accept the default or answer "none"
 to leave it blank.
 
 Operating system name? [netbsd]
 
 Operating system version? [5.0]
 
 Perl can be built to take advantage of threads on some systems.
 To do so, Configure can be run with -Dusethreads.
 
 Note that threading is a highly experimental feature, and
 some known race conditions still remain.  If you choose to try
 it, be very sure to not actually deploy it for production
 purposes.  README.threads has more details, and is required
 reading if you enable threads.
 
 If this doesn't make any sense to you, just accept the default 'n'.
 Build a threading Perl? [n]
 
 Perl can be built so that multiple Perl interpreters can coexist
 within the same Perl executable.
 
 If this doesn't make any sense to you, just accept the default 'n'.
 Build Perl for multiplicity? [n]
 
 Hmm...  Looks kind of like a BSD system, but we'll see...
 
 Congratulations.  You aren't running Eunice.
 
 It's not Xenix...
 
 Nor is it Venix...
 Use which C compiler? [cc]
 
 Checking for GNU cc in disguise and/or its version number...
 gccvers.c: In function 'main':
 gccvers.c:10: warning: incompatible implicit declaration of built-in 
 function 'exit'
 You are using GNU cc 4.1.3 20080704 prerelease (NetBSD nb2 20081120).
 
 Now, how can we feed standard input to your C preprocessor...
 Maybe "cc -E" will work...
 Nope...maybe "cc -E -" will work...
 Yup, it does.
 
 Hmm...  Doesn't look like a MIPS system.
 
 Some systems have incompatible or broken versions of libraries.  Among
 the directories listed in the question below, please remove any you
 know not to be holding relevant libraries, and add any that are needed.
 Say "none" for none.
 
 Directories to use for library searches? [/lib /usr/lib]
 
 On some systems, shared libraries may be available.  Answer 'none' if
 you want to suppress searching of shared libraries for the remainder
 of this configuration.
 
 What is the file extension used for shared libraries? [so]
 
 Perl can be built to use the SOCKS proxy protocol library.  To do so,
 Configure must be run with -Dusesocks.
 
 If this doesn't make any sense to you, just accept the default 'n'.
 Build Perl for SOCKS? [n]
 
 Checking for optional libraries...
 No -lsfio.
 No -lsocket.
 No -lbind.
 No -linet.
 No -lnsl.
 No -lnm.
 No -lndbm.
 No -lgdbm.
 No -ldbm.
 No -ldb.
 No -lmalloc.
 No -ldl.
 No -ldld.
 No -lld.
 No -lsun.
 Found -lm (shared).
 Found -lc (shared).
 No -lcposix.
 Found -lposix (shared).
 No -lndir.
 No -ldir.
 Found -lcrypt (shared).
 No -lsec.
 No -lucb.
 No -lbsd.
 No -lBSD.
 No -lPW.
 No -lx.
 No -liconv.
 Found -lutil (shared).
 
 In order to compile perl5 on your machine, a number of libraries
 are usually needed.  Include any other special libraries here as well.
 Say "none" for none.  The default list is almost always right.
 
 What libraries to use? [-lm -lc -lposix -lcrypt -lutil]
 
 By default, perl5 compiles with the -O flag to use the optimizer.
 Alternately, you might want to use the symbolic debugger, which uses
 the -g flag (on traditional Unix systems).  Either flag can be
 specified here.  To use neither flag, specify the word "none".
 
 What optimizer/debugger flag should be used? [-O]
 
 Checking if your compiler accepts -fno-strict-aliasing
 Yes, it does.
 
 Your C compiler may want other flags.  For this question you should include
 -I/whatever and -DWHATEVER flags and any other flags used by the C compiler,
 but you should NOT include libraries or ld flags like -lwhatever.  If you
 want perl5 to honor its debug switch, you should include -DDEBUGGING here.
 Your C compiler might also need additional flags, such as -D_POSIX_SOURCE.
 
 To use no flags, specify the word "none".
 
 Any additional cc flags? [-fno-strict-aliasing]
 
 Let me guess what the preprocessor flags are...
 They appear to be: -fno-strict-aliasing
 
 Your C linker may need flags.  For this question you should
 include -L/whatever and any other flags used by the C linker, but you
 should NOT include libraries like -lwhatever.
 
 Make sure you include the appropriate -L/path flags if your C linker
 does not normally search all of the directories you specified above,
 namely
          /lib /usr/lib
 To use no flags, specify the word "none".
 
 Any additional ld flags (NOT including libraries)? [none]
 
 Checking your choice of C compiler and flags for coherency...
 OK, that should do.
 
 Checking to see how big your integers are...
 intsize.c: In function 'main':
 intsize.c:7: warning: incompatible implicit declaration of built-in 
 function 'exit'
 Your integers are 4 bytes long.
 Your long integers are 8 bytes long.
 Your short integers are 2 bytes long.
 
 Looking for the type used for lseek's offset on this system.
 off_t found.
 
 Checking to see how big your file offsets are...
 Your file offsets are 8 bytes long.
 
 Looking for the type for file position used by fsetpos().
 fpos_t found.
 
 Checking the size of fpos_t...
 try.c: In function 'main':
 try.c:5: warning: incompatible implicit declaration of built-in function 'exit'
 Your fpos_t is 8 bytes long.
 
 You can have files larger than 2 gigabytes.
 
 You have natively 64-bit long integers.
 
 You may also choose to try maximal 64-bitness.  It means using as much
 64-bitness as possible on the platform.  This in turn means even more
 binary incompatibilities.  On the other hand, your platform may not
 have any more 64-bitness available than what you already have chosen.
 
 If this doesn't make any sense to you, just accept the default 'y'.
 Try to use maximal 64-bit support, if available? [y]
 
 Checking for GNU C Library...
 gnulibc.c: In function 'main':
 gnulibc.c:7: warning: incompatible implicit declaration of built-in 
 function 'exit'
 You are not using the GNU C Library
 
 I can use /usr/bin/nm to extract the symbols from your C libraries. This
 is a time consuming task which may generate huge output on the disk (up
 to 3 megabytes) but that should make the symbols extraction faster. The
 alternative is to skip the 'nm' extraction part and to compile a small
 test program instead to determine whether each symbol is present. If
 you have a fast C compiler and/or if your 'nm' output cannot be parsed,
 this may be the best solution.
 
 You probably shouldn't let me use 'nm' if you are using the GNU C Library.
 
 Shall I use /usr/bin/nm to extract C symbols from the libraries? [y]
 
 Your (shared) C library seems to be in /lib/libc.so.
 
 If the guess above is wrong (which it might be if you're using a strange
 compiler, or your machine supports multiple models), you can override it here.
 
 Where is your C library? [/lib/libc.so]
 
 Extracting names from the following files for later perusal:
 
          /lib/libc.so
          /lib/libcrypt.so.0.2
          /lib/libm.so.0.6
          /lib/libutil.so.7.15
          /usr/lib/libposix.so.0.1
 
 This may take a while.....done
 
 sqrtl() NOT found.
 
 Perl can be built to take advantage of long doubles which
 (if available) may give more accuracy and range for floating point numbers.
 
 If this doesn't make any sense to you, just accept the default 'n'.
 Try to use long doubles if available? [n]
 
 Checking to see how big your double precision numbers are...
 try.c: In function 'main':
 try.c:5: warning: incompatible implicit declaration of built-in function 'exit'
 Your double is 8 bytes long.
 
 Checking to see if you have long double...
 You have long double.
 
 Checking to see how big your long doubles are...
 Your long doubles are 8 bytes long.
 (That isn't any different from an ordinary double.)
 
 What is your architecture name [alpha-netbsd]
 This architecture is naturally 64-bit, not changing architecture name.
 
 By default, perl5 will be installed in /usr/local/bin, manual pages
 under /usr/local/man, etc..., i.e. with /usr/local as prefix for all
 installation directories. Typically this is something like /usr/local.
 If you wish to have binaries under /usr/bin but other parts of the
 installation under /usr/local, that's ok: you will be prompted
 separately for each of the installation directories, the prefix being
 only used to set the defaults.
 
 Installation prefix to use? (~name ok) [/usr/local]
 
 AFS does not seem to be running...
 
 In some special cases, particularly when building perl5 for distribution,
 it is convenient to distinguish between the directory in which files should
 be installed from the directory (/usr/local) in which they
 will eventually reside.  For most users, these two directories are the same.
 
 What installation prefix should I use for installing files? (~name ok)
 [/usr/local]
 
 Getting the current patchlevel...
 (You have perl5 version 6 subversion 1.)
 
 There are some auxiliary files for perl5 that need to be put into a
 private library directory that is accessible by everyone.
 
 Pathname where the private library files will reside? (~name ok)
 [/usr/local/lib/perl5/5.6.1]
 
 Perl5 contains architecture-dependent library files.  If you are
 sharing libraries in a heterogeneous environment, you might store
 these files in a separate location.  Otherwise, you can just include
 them with the rest of the public library files.
 
 Where do you want to put the public architecture-dependent libraries? 
 (~name ok)
 [/usr/local/lib/perl5/5.6.1/alpha-netbsd]
 
 This version of Perl can be compiled for binary compatibility with 5.005.
 If you decide to do so, you will be able to continue using most of the
 extensions that were compiled for Perl 5.005.
 
 Binary compatibility with Perl 5.005? [y]
 
 Some kernels have a bug that prevents setuid #! scripts from being
 secure.  Some sites have disabled setuid #! scripts because of this.
 
 First let's decide if your kernel supports secure setuid #! scripts.
 (If setuid #! scripts would be secure but have been disabled anyway,
 don't say that they are secure if asked.)
 
 If you are not sure if they are secure, I can check but I'll need a
 username and password different from the one you are using right now.
 If you don't have such a username or don't want me to test, simply
 enter 'none'.
 
 Other username to test security of setuid scripts with? [none]
 I'll assume setuid scripts are *not* secure.
 Does your kernel have *secure* setuid scripts? [n]
 
 Some systems have disabled setuid scripts, especially systems where
 setuid scripts cannot be secure.  On systems where setuid scripts have
 been disabled, the setuid/setgid bits on scripts are currently
 useless.  It is possible for perl5 to detect those bits and emulate
 setuid/setgid in a secure fashion.  This emulation will only work if
 setuid scripts have been disabled in your kernel.
 
 Do you want to do setuid/setgid emulation? [n]
 
 Computing filename position in cpp output for #include directives...
 Your cpp writes the filename in the third field of the line.
 
 <malloc.h> found.
 
 <stdlib.h> found.
 
 Do you wish to attempt to use the malloc that comes with perl5? [y]
 
 Your system wants malloc to return 'void *', it would seem.
 Your system uses void free(), it would seem.
 
 After perl5 is installed, you may wish to install various
 add-on modules and utilities.  Typically, these add-ons will
 be installed under /usr/local with the rest
 of this package.  However, you may wish to install such add-ons
 elsewhere under a different prefix.
 
 If you do not wish to put everything under a single prefix, that's
 ok.  You will be prompted for the individual locations; this siteprefix
 is only used to suggest the defaults.
 
 The default should be fine for most people.
 
 Installation prefix to use for add-on modules and utilities? (~name ok)
 [/usr/local]
 
 The installation process will create a directory for
 site-specific extensions and modules.  Most users find it convenient
 to place all site-specific files in this directory rather than in the
 main distribution directory.
 
 Pathname for the site-specific library files? (~name ok)
 [/usr/local/lib/perl5/site_perl/5.6.1]
 
 The installation process will also create a directory for
 architecture-dependent site-specific extensions and modules.
 
 Pathname for the site-specific architecture-dependent library files? (~name ok)
 [/usr/local/lib/perl5/site_perl/5.6.1/alpha-netbsd]
 
 The installation process will also create a directory for
 vendor-supplied add-ons.  Vendors who supply perl with their system
 may find it convenient to place all vendor-supplied files in this
 directory rather than in the main distribution directory.  This will
 ease upgrades between binary-compatible maintenance versions of perl.
 
 Of course you may also use these directories in whatever way you see
 fit.  For example, you might use them to access modules shared over a
 company-wide network.
 
 The default answer should be fine for most people.
 This causes further questions about vendor add-ons to be skipped
 and no vendor-specific directories will be configured for perl.
 
 Do you want to configure vendor-specific add-on directories? [n]
 
 Lastly, you can have perl look in other directories for extensions and
 modules in addition to those already specified.
 These directories will be searched after
          /usr/local/lib/perl5/site_perl/5.6.1/alpha-netbsd
          /usr/local/lib/perl5/site_perl/5.6.1
 
 Enter a colon-separated set of extra paths to include in perl's @INC
 search path, or enter 'none' for no extra paths.
 
 Colon-separated list of additional directories for perl to search? [none]
 
 Checking out function prototypes...
 Your C compiler appears to support function prototypes.
 
 Pathname where the public executables will reside? (~name ok)
 [/usr/local/bin]
 Looking for a previously installed perl5.005 or later...
 None found.  That's ok.
 
 In order to ease the process of upgrading, this version of perl
 can be configured to use modules built and installed with earlier
 versions of perl that were installed under $prefix.  Specify here
 the list of earlier versions that this version of perl should check.
 If Configure detected no earlier versions of perl installed under
 $prefix, then the list will be empty.  Answer 'none' to tell perl
 to not search earlier versions.
 
 The default should almost always be sensible, so if you're not sure,
 just accept the default.
 List of earlier versions to include in @INC? [none]
 
 Many scripts expect perl to be installed as /usr/bin/perl.
 I can install the perl you are about to compile also as /usr/bin/perl
 (in addition to /usr/local/bin/perl).
 Do you want to install perl as /usr/bin/perl? [n]
 
 <dld.h> NOT found.
 
 dlopen() found.
 
 Do you wish to use dynamic loading? [y]
 The following dynamic loading files are available:
 ext/DynaLoader/dl_aix.xs              ext/DynaLoader/dl_mac.xs
 ext/DynaLoader/dl_beos.xs             ext/DynaLoader/dl_mpeix.xs
 ext/DynaLoader/dl_dld.xs              ext/DynaLoader/dl_next.xs
 ext/DynaLoader/dl_dllload.xs          ext/DynaLoader/dl_none.xs
 ext/DynaLoader/dl_dlopen.xs           ext/DynaLoader/dl_vmesa.xs
 ext/DynaLoader/dl_dyld.xs             ext/DynaLoader/dl_vms.xs
 ext/DynaLoader/dl_hpux.xs
 Source file to use for dynamic loading [ext/DynaLoader/dl_dlopen.xs]
 
 Some systems may require passing special flags to cc -c to
 compile modules that will be used to create a shared library.
 To use no flags, say "none".
 
 Any special flags to pass to cc -c to compile shared library modules?
 [-DPIC -fPIC ]
 
 Some systems use ld to create libraries that can be dynamically loaded,
 while other systems (such as those using ELF) use cc.
 
 You appear to have ELF support.  I'll use cc to build dynamic libraries.
 What command should be used to create dynamic libraries? [cc]
 
 Some systems may require passing special flags to cc to create a
 library that can be dynamically loaded.  If your ld flags include
 -L/other/path options to locate libraries outside your loader's normal
 search path, you may need to specify those -L options here as well.  To
 use no flags, say "none".
 
 Any special flags to pass to cc to create a dynamically loaded library?
 [--whole-archive -shared ]
 
 Some systems may require passing special flags to cc to indicate that
 the resulting executable will use dynamic linking.  To use no flags,
 say "none".
 
 Any special flags to pass to cc to use dynamic linking? [-Wl,-E -Wl,-R/lib ]
 
 The perl executable is normally obtained by linking perlmain.c with
 libperl.a, any static extensions (usually just DynaLoader), and
 any other libraries needed on this system (such as -lm, etc.).  Since
 your system supports dynamic loading, it is probably possible to build
 a shared libperl.so.  If you will have more than one executable linked
 to libperl.so, this will significantly reduce the size of each
 executable, but it may have a noticeable affect on performance.  The
 default is probably sensible for your system.
 
 
 Build a shared libperl.so (y/n) [n]
 
 System manual is in /usr/share/man/man1.
 
 Perl5 has manual pages available in source form.
 If you don't want the manual sources installed, answer 'none'.
 
 Where do the main Perl5 manual pages (source) go? (~name ok)
 [/usr/local/man/man1]
 What suffix should be used for the main Perl5 man pages? [1]
 
 You can have filenames longer than 14 characters.
 
 Perl5 has manual pages for many of the library modules.
 If you don't want the manual sources installed, answer 'none'.
 
 Where do the perl5 library man pages (source) go? (~name ok)
 [/usr/local/man/man3]
 What suffix should be used for the perl5 library man pages? [3]
 
 Figuring out host name...
 Maybe "hostname" will work...
 Your host name appears to be "xp1000". Right? [y]
 (Trimming domain name from host name--host name is now xp1000)
 
 What is your domain name? []
 
 I need to get your e-mail address in Internet format if possible, i.e.
 something like user%host.domain.@localhost Please answer accurately since I 
have
 no easy means to double check it. The default value provided below
 is most probably close to reality but may not be valid from outside
 your organization...
 
 What is your e-mail address? [ray@xp1000]
 
 If you or somebody else will be maintaining perl at your site, please
 fill in the correct e-mail address here so that they may be contacted
 if necessary. Currently, the "perlbug" program included with perl
 will send mail to this address in addition to perlbug%perl.org.@localhost You 
may
 enter "none" for no administrator.
 
 Perl administrator e-mail address [ray@xp1000]
 
 Do you want to install only the version-specific parts of the perl
 distribution?  Usually you do *not* want to do this.
 Do you want to install only the version-specific parts of perl? [n]
 
 I can use the #! construct to start perl on your system. This will
 make startup of perl scripts faster, but may cause problems if you
 want to share those scripts and perl is not in a standard place
 (/usr/local/bin/perl) on all your platforms. The alternative is to force
 a shell by starting the script with a single ':' character.
 
 What shall I put after the #! to start up perl ("none" to not use #!)?
 [/usr/local/bin/perl]
 I'll use #!/usr/local/bin/perl to start perl scripts.
 
 Some installations have a separate directory just for executable scripts so
 that they can mount it across multiple architectures but keep the scripts in
 one spot.  You might, for example, have a subdirectory of /usr/share for this.
 Or you might just lump your scripts in with all your other executables.
 
 Where do you keep publicly executable scripts? (~name ok) [/usr/local/bin]
 Pathname where the add-on public executables should be installed? (~name ok)
 [/usr/local/bin]
 
 Previous version of perl5 used the standard IO mechanisms as defined
 in <stdio.h>.  Versions 5.003_02 and later of perl allow alternate IO
 mechanisms via a "PerlIO" abstraction, but the stdio mechanism is still
 the default.  This abstraction layer can use AT&T's sfio (if you already
 have sfio installed) or regular stdio.  Using PerlIO with sfio may cause
 problems with some extension modules.  Using PerlIO with stdio is safe,
 but it is slower than plain stdio and therefore is not the default.
 
 If this doesn't make any sense to you, just accept the default 'n'.
 Use the experimental PerlIO abstraction layer? [n]
 Ok, doing things the stdio way
 
 qgcvt() NOT found.
 
 Checking how to print long doubles...
 We will use %f.
 
 Checking for an efficient way to convert floats to strings.
 Trying gconvert...
 gconvert NOT found.
 Trying gcvt...
 gcvt NOT found.
 Trying sprintf...
 sprintf() found.
 I'll use sprintf to convert floats into a string.
 
 fwalk() found.
 
 access() found.
 
 <sys/file.h> defines the *_OK access constants.
 
 accessx() NOT found.
 
 alarm() found.
 
 atolf() NOT found.
 
 atoll() found.
 
 Checking whether your compiler can handle __attribute__ ...
 Your C compiler supports __attribute__.
 
 bcmp() found.
 
 bcopy() found.
 
 <unistd.h> found.
 
 getpgrp() found.
 
 Checking to see which flavor of getpgrp is in use...
 You have to use getpgrp() instead of getpgrp(pid).
 
 setpgrp() found.
 
 Checking to see which flavor of setpgrp is in use...
 You have to use setpgrp(pid,pgrp) instead of setpgrp().
 
 bzero() found.
 
 You have void (*signal())().
 
 Checking whether your C compiler can cast large floats to int32.
 try.c: In function 'blech':
 try.c:4: warning: incompatible implicit declaration of built-in function 'exit'
 try.c: In function 'main':
 try.c:28: warning: incompatible implicit declaration of built-in 
 function 'exit'
 Nope, it can't.
 
 Checking whether your C compiler can cast negative float to unsigned.
 try.c: In function 'blech':
 try.c:4: warning: incompatible implicit declaration of built-in function 'exit'
 try.c: In function 'blech_in_list':
 try.c:5: warning: incompatible implicit declaration of built-in function 'exit'
 try.c: In function 'main':
 try.c:56: warning: incompatible implicit declaration of built-in 
 function 'exit'
 Yup, it can.
 
 vprintf() found.
 Your vsprintf() returns (char*).
 
 chown() found.
 
 chroot() found.
 
 chsize() NOT found.
 
 Checking to see if your C compiler knows about "const"...
 Yup, it does.
 
 crypt() found.
 
 cuserid() NOT found.
 
 <limits.h> found.
 
 <float.h> found.
 
 DBL_DIG found.
 
 difftime() found.
 
 <dirent.h> found.
 
 Your directory entries are struct dirent.
 
 Good, your directory entry keeps length information in d_namlen.
 
 dlerror() found.
 
 <dlfcn.h> found.
 
 On a few systems, the dynamically loaded modules that perl generates and uses
 will need a different extension than shared libs. The default will probably
 be appropriate.
 
 What is the extension of dynamically loaded modules [so]
 
 Checking whether your dlsym() needs a leading underscore ...
 dlsym doesn't need a leading underscore.
 
 drand48() prototype found.
 
 dup2() found.
 
 eaccess() NOT found.
 
 endgrent() found.
 
 endhostent() found.
 
 endnetent() found.
 
 endprotoent() found.
 
 endpwent() found.
 
 endservent() found.
 
 <sys/file.h> defines the O_* constants...
 and you have the 3 argument form of open().
 
 Using <string.h> instead of <strings.h>.
 
 Figuring out the flag used by open() for non-blocking I/O...
 try.c: In function 'main':
 try.c:6: warning: incompatible implicit declaration of built-in function 'exit'
 Seems like we can use O_NONBLOCK.
 
 Let's see what value errno gets from read() on a O_NONBLOCK file...
 try.c: In function 'blech':
 try.c:20: warning: incompatible implicit declaration of built-in 
 function 'exit'
 try.c: In function 'main':
 try.c:36: warning: incompatible implicit declaration of built-in 
 function 'exit'
 try.c:72: warning: incompatible implicit declaration of built-in 
 function 'exit'
 A read() system call with no data present returns -1.
 Your read() sets errno to EAGAIN when no data is available.
 And it correctly returns 0 to signal EOF.
 
 fchmod() found.
 
 fchown() found.
 
 fcntl() found.
 
 Checking if fcntl-based file locking works...
 Yes, it seems to work.
 
 Hmm... Looks like you have Berkeley networking support.
 
 socketpair() found.
 
 Checking the availability of certain socket constants...
 
 <sys/select.h> found.
 
 Testing to see if we should include <time.h>, <sys/time.h> or both.
 I'm now running the test program....
 Succeeded with -DI_SYSTIME -DS_TIMEVAL
 We'll include <sys/time.h>.
 
 Checking to see how well your C compiler handles fd_set and friends ...
 Well, your system knows about the normal fd_set typedef...
 and you have the normal fd_set macros (just as I'd expect).
 
 fgetpos() found.
 
 flock() found.
 
 fork() found.
 
 pathconf() found.
 
 fpathconf() found.
 
 Checking to see if you have fpos64_t...
 You do not have fpos64_t.
 (Your fpos_t is 64 bits, so you could use that.)
 
 frexpl() NOT found.
 
 <sys/param.h> found.
 
 <sys/mount.h> found.
 
 <sys/types.h> found.
 
 Checking to see if your system supports struct fs_data...
 No, it doesn't.
 
 fseeko() found.
 (Your long is 64 bits, so you could use fseek.)
 
 fsetpos() found.
 
 fstatfs() found.
 
 statvfs() found.
 
 fstatvfs() found.
 
 fsync() found.
 
 ftello() found.
 (Your long is 64 bits, so you could use ftell.)
 
 getcwd() found.
 
 getespwnam() NOT found.
 
 getfsstat() found.
 
 getgrent() found.
 
 gethostbyaddr() found.
 
 gethostbyname() found.
 
 gethostent() found.
 
 gethostname() found.
 uname() found.
 
 Every now and then someone has a gethostname() that lies about the hostname
 but can't be fixed for political or economic reasons.  If you wish, I can
 pretend gethostname() isn't there and maybe compute hostname at run-time
 thanks to the 'hostname' command.
 
 Shall I ignore gethostname() from now on? [n]
 
 <netdb.h> found.
 
 gethostent() prototype found.
 
 getlogin() found.
 
 getmnt() NOT found.
 
 getmntent() NOT found.
 
 getnetbyaddr() found.
 
 getnetbyname() found.
 
 getnetent() found.
 
 getnetent() prototype found.
 
 getpagesize() found.
 
 getprotobyname() found.
 
 getprotobynumber() found.
 
 getprotoent() found.
 
 getpgid() found.
 
 getpgrp2() NOT found.
 
 getppid() found.
 
 getpriority() found.
 
 getprotoent() prototype found.
 
 getprpwnam() NOT found.
 
 getpwent() found.
 
 getservbyname() found.
 
 getservbyport() found.
 
 getservent() found.
 
 getservent() prototype found.
 
 getspnam() NOT found.
 
 gettimeofday() found.
 
 <grp.h> found.
 
 hasmntopt() NOT found.
 
 <netinet/in.h> found.
 
 <arpa/inet.h> found.
 
 htonl() found.
 
 iconv() found.
 
 strchr() found.
 
 inet_aton() found.
 
 <inttypes.h> found.
 
 Checking to see if you have int64_t...
 You have int64_t.
 
 isascii() found.
 
 isnan() found.
 
 isnanl() NOT found.
 
 killpg() found.
 
 lchown() found.
 
 LDBL_DIG found.
 
 link() found.
 
 localeconv() found.
 
 lockf() found.
 
 Checking to see if you have long long...
 You have long long.
 
 Checking to see how big your long longs are...
 Your long longs are 8 bytes long.
 (That isn't any different from an ordinary long.)
 
 lseek() prototype found.
 
 lstat() found.
 
 madvise() found.
 
 mblen() found.
 
 mbstowcs() found.
 
 mbtowc() found.
 
 memchr() found.
 
 memcmp() found.
 
 memcpy() found.
 
 memmove() found.
 
 memset() found.
 
 mkdir() found.
 
 mkdtemp() found.
 
 mkfifo() found.
 
 mkstemp() found.
 
 mkstemps() NOT found.
 
 mktime() found.
 
 <sys/mman.h> found.
 
 mmap() found.
 and it returns (void *).
 
 modfl() NOT found.
 
 mprotect() found.
 
 msgctl() found.
 
 msgget() found.
 
 msgsnd() found.
 
 msgrcv() found.
 
 You have the full msg*(2) library.
 
 msync() found.
 
 munmap() found.
 
 nice() found.
 
 Checking which 64-bit integer type we could use...
 We will use 'long' for 64-bit integers.
 
 Checking to see how big your characters are (hey, you never know)...
 try.c: In function 'main':
 try.c:5: warning: incompatible implicit declaration of built-in function 'exit'
 What is the size of a character (in bytes)? [1]
 
 Checking to see if your C compiler knows about "volatile"...
 Yup, it does.
 
 Choosing the C types to be used for Perl's internal types...
 (IV will be long, 8 bytes)
 (UV will be unsigned long, 8 bytes)
 (NV will be double, 8 bytes)
 Checking how many bits of your UVs your NVs can preserve...
 Your NVs can preserve only 53 bits of your UVs.
 
 Checking to see if you have off64_t...
 You do not have off64_t.
 (Your off_t is 64 bits, so you could use that.)
 
 <pthread.h> found.
 
 pause() found.
 
 pipe() found.
 
 poll() found.
 
 <pwd.h> found.
 
 readdir() found.
 
 seekdir() found.
 
 telldir() found.
 
 rewinddir() found.
 
 readlink() found.
 
 rename() found.
 
 rmdir() found.
 
 <memory.h> found.
 
 We won't be including <memory.h>.
 
 Checking to see if your bcopy() can do overlapping copies...
 Yes, it can.
 
 Checking to see if your memcpy() can do overlapping copies...
 Yes, it can.
 
 Checking if your memcmp() can compare relative magnitude...
 Yes, it can.
 
 sbrk() prototype found.
 
 select() found.
 
 semctl() found.
 
 semget() found.
 
 semop() found.
 
 You have the full sem*(2) library.
 
 You do not have union semun in <sys/sem.h>.
 
 You can use union semun for semctl IPC_STAT.
 You can also use struct semid_ds* for semctl IPC_STAT.
 
 setegid() found.
 
 seteuid() found.
 
 setgrent() found.
 
 sethostent() found.
 
 setlinebuf() found.
 
 setlocale() found.
 
 setnetent() found.
 
 setprotoent() found.
 
 setpgid() found.
 
 setpgrp2() NOT found.
 
 setpriority() found.
 
 setproctitle() found.
 
 setpwent() found.
 
 setregid() found.
 
 setresgid() NOT found.
 
 setreuid() found.
 
 setresuid() NOT found.
 
 setrgid() found.
 
 *** WHOA THERE!!! ***
      The recommended value for $d_setrgid on this machine was "undef"!
      Keep the recommended value? [y]
 
 setruid() found.
 
 *** WHOA THERE!!! ***
      The recommended value for $d_setruid on this machine was "undef"!
      Keep the recommended value? [y]
 
 setservent() found.
 
 setsid() found.
 
 setvbuf() found.
 
 <sfio.h> NOT found.
 libs = -lm -lc -lposix -lcrypt -lutil
 
 shmctl() found.
 
 shmget() found.
 
 shmat() found.
 and it returns (void *).
 
 shmdt() found.
 
 You have the full shm*(2) library.
 
 sigaction() found.
 try.c: In function 'main':
 try.c:10: warning: incompatible implicit declaration of built-in 
 function 'exit'
 
 POSIX sigsetjmp found.
 
 socks5_init() NOT found.
 
 <sys/stat.h> found.
 
 Checking to see if your struct stat has st_blocks field...
 
 <sys/vfs.h> NOT found.
 
 <sys/statfs.h> NOT found.
 
 Checking to see if your system supports struct statfs...
 No, it doesn't.
 No, it doesn't.
 
 (Looks like you have stdio.h from BSD.)
 Checking how std your stdio is...
 Your stdio acts pretty std.
 Checking to see what happens if we set the stdio ptr...
 Increasing ptr in your stdio leaves cnt unchanged.  Good.
 However, it seems to be lacking the _base field.
 Checking how to access stdio streams by file descriptor number...
 You can access stdio streams by file descriptor number by the __sF array.
 
 strcoll() found.
 
 Checking to see if your C compiler can copy structs...
 Yup, it can.
 
 strerror() found.
 (You also have sys_errlist[], so we could roll our own strerror.)
 
 strtod() found.
 
 strtol() found.
 
 strtold() found.
 
 strtoll() found.
 Checking whether your strtoll() works okay...
 Your strtoll() seems to be working okay.
 
 strtoul() found.
 
 strtoull() found.
 Checking whether your strtoull() works okay...
 Your strtoull() seems to be working okay.
 
 strtouq() found.
 
 strxfrm() found.
 
 symlink() found.
 
 syscall() found.
 
 sysconf() found.
 
 system() found.
 
 tcgetpgrp() found.
 
 tcsetpgrp() found.
 
 telldir() prototype found.
 
 <sys/times.h> found.
 
 times() found.
 
 Looking for the type returned by times() on this system.
 clock_t found.
 
 truncate() found.
 
 tzname[] found.
 
 umask() found.
 
 ustat() NOT found.
 
 vfork() found.
 
 
 Perl can only use a vfork() that doesn't suffer from strict
 restrictions on calling functions or modifying global data in
 the child.  For example, glibc-2.1 contains such a vfork()
 that is unsuitable.  If your system provides a proper fork()
 call, chances are that you do NOT want perl to use vfork().
 
 Do you still want to use vfork()? [n]
 Ok, we won't use vfork().
 
 <sys/dir.h> found.
 
 <sys/ndir.h> NOT found.
 
 closedir() found.
 
 Checking whether closedir() returns a status...
 Yes, it does.
 
 wait4() found.
 
 waitpid() found.
 
 wcstombs() found.
 
 wctomb() found.
 
 Checking alignment constraints...
 Doubles must be aligned on a how-many-byte boundary? [8]
 
 In the following, larger digits indicate more significance.  A big-endian
 machine like a Pyramid or a Motorola 680?0 chip will come out to 4321. A
 little-endian machine like a Vax or an Intel 80?86 chip would be 1234. Other
 machines may have weird orders like 3412.  A Cray will report 87654321,
 an Alpha will report 12345678. If the test program works the default is
 probably right.
 I'm now running the test program...
 (The test program ran ok.)
 byteorder=12345678
 
 Checking to see how your cpp does stuff like catenate tokens...
 Oh!  Smells like ANSI's been here.
 We can catify or stringify, separately or together!
 
 <db.h> found.
 
 Checking Berkeley DB version ...
 try.c: In function 'main':
 try.c:43: warning: incompatible implicit declaration of built-in 
 function 'exit'
 You have Berkeley DB Version 1
 Looks OK.
 
 Checking return type needed for hash for Berkeley DB ...
 Your version of Berkeley DB uses u_int32_t for hash.
 
 Checking return type needed for prefix for Berkeley DB ...
 Your version of Berkeley DB uses size_t for prefix.
 
 Checking to see how well your C compiler groks the void type...
 Good.  It appears to support void to the level perl5 wants.
 However, you might get some warnings that look like this:
 try.c: In function 'sub':
 try.c:17: warning: incompatible implicit declaration of built-in 
 function 'exit'
 try.c:20: warning: incompatible implicit declaration of built-in 
 function 'exit'
 
 Looking for a random number function...
 Good, found drand48().
 
 Use which function to generate random numbers? [drand48]
 
 Determining whether or not we are on an EBCDIC system...
 Nope, no EBCDIC, probably ASCII or some ISO Latin. Or UTF8.
 
 Checking how to flush all pending stdio output...
 Your fflush(NULL) works okay for output streams.
 Let's see if it clobbers input pipes...
 fflush(NULL) seems to behave okay with input streams.
 
 Looking for the type for group ids returned by getgid().
 gid_t found.
 
 Checking the size of gid_t...
 try.c: In function 'main':
 try.c:5: warning: incompatible implicit declaration of built-in function 'exit'
 Your gid_t is 4 bytes long.
 
 Checking the sign of gid_t...
 Your gid_t is unsigned.
 
 Checking how to print 64-bit integers...
 We will use %ld.
 
 Checking the format strings to be used for Perl's internal types...
 
 Checking the format string to be used for gids...
 
 getgroups() found.
 
 setgroups() found.
 
 What type of pointer is the second argument to getgroups() and setgroups()?
 Usually this is the same as group ids, gid_t, but not always.
 
 What type pointer is the second argument to getgroups() and setgroups()?
 [gid_t]
 
 Checking if your /usr/bin/make program sets $(MAKE)...
 Yup, it does.
 
 Looking for the type used for file modes for system calls (e.g. fchmod()).
 mode_t found.
 
 Looking for the type used for the length parameter for string functions.
 size_t found.
 
 Checking to see what type of arguments are accepted by gethostbyaddr().
 
 What is the type for the 1st argument to gethostbyaddr? [char *] What 
 is the type for the 2nd argument to gethostbyaddr? [size_t]
 
 Checking to see what type of argument is accepted by gethostbyname().
 Your system accepts const char *.
 
 Checking to see what type of 1st argument is accepted by getnetbyaddr().
 Your system accepts in_addr_t.
 
 What pager is used on your system? [/usr/bin/less]
 
 Looking for the type of process ids on this system.
 pid_t found.
 
 Checking to see how big your pointers are...
 try.c: In function 'main':
 try.c:6: warning: incompatible implicit declaration of built-in function 'exit'
 Your pointers are 8 bytes long.
 
 Checking how to generate random libraries on your machine...
 /usr/bin/ar appears to generate random libraries itself.
 
 Checking to see what type of arguments are accepted by select().
 Your system accepts fd_set *.
 
 Checking to see on how many bits at a time your select() operates...
 try.c: In function 'main':
 try.c:41: warning: incompatible implicit declaration of built-in 
 function 'exit'
 Your select() operates on 32 bits at a time.
 
 Generating a list of signal names and numbers...
 signal.c: In function 'main':
 signal.c:211: warning: incompatible implicit declaration of built-in 
 function 'exit'
 The following 64 signals are available:
 
 SIGZERO SIGHUP SIGINT SIGQUIT SIGILL SIGTRAP SIGABRT SIGEMT SIGFPE
 SIGKILL SIGBUS SIGSEGV SIGSYS SIGPIPE SIGALRM SIGTERM SIGURG SIGSTOP
 SIGTSTP SIGCONT SIGCHLD SIGTTIN SIGTTOU SIGIO SIGXCPU SIGXFSZ
 SIGVTALRM SIGPROF SIGWINCH SIGINFO SIGUSR1 SIGUSR2 SIGPWR SIGNUM33
 SIGNUM34 SIGNUM35 SIGNUM36 SIGNUM37 SIGNUM38 SIGNUM39 SIGNUM40
 SIGNUM41 SIGNUM42 SIGNUM43 SIGNUM44 SIGNUM45 SIGNUM46 SIGNUM47
 SIGNUM48 SIGNUM49 SIGNUM50 SIGNUM51 SIGNUM52 SIGNUM53 SIGNUM54
 SIGNUM55 SIGNUM56 SIGNUM57 SIGNUM58 SIGNUM59 SIGNUM60 SIGNUM61
 SIGNUM62 SIGNUM63 SIGIOT
 
 Checking the size of size_t...
 try.c: In function 'main':
 try.c:5: warning: incompatible implicit declaration of built-in function 'exit'
 Your size_t size is 8 bytes.
 
 Checking to see if you have socklen_t...
 You have socklen_t.
 
 <socks.h> NOT found.
 
 Checking to see what type is the last argument of accept().
 Your system accepts 'socklen_t *' for the last argument of accept().
 
 ssize.c: In function 'main':
 ssize.c:13: warning: incompatible implicit declaration of built-in 
 function 'exit'
 I'll be using ssize_t for functions returning a byte count.
 
 Your stdio uses signed chars.
 
 time() found.
 
 Looking for the type returned by time() on this system.
 time_t found.
 
 Looking for the type for user ids returned by getuid().
 uid_t found.
 
 Checking the size of uid_t...
 try.c: In function 'main':
 try.c:5: warning: incompatible implicit declaration of built-in function 'exit'
 Your uid_t is 4 bytes long.
 
 Checking the sign of uid_t...
 Your uid_t is unsigned.
 
 Checking the format string to be used for uids...
 
 Which compiler compiler (yacc) shall I use? [yacc]
 
 dbmclose() NOT found.
 We won't be including <dbm.h>
 
 <sys/file.h> found.
 
 We'll be including <sys/file.h>.
 
 <fcntl.h> found.
 
 We don't need to include <fcntl.h> if we include <sys/file.h>.
 
 <iconv.h> found.
 
 <ieeefp.h> found.
 
 <libutil.h> NOT found.
 
 <locale.h> found.
 
 <math.h> found.
 
 <mntent.h> NOT found.
 
 <ndbm.h> found.
 
 dbm_open() found.
 
 <net/errno.h> NOT found.
 
 <netinet/tcp.h> found.
 
 <poll.h> found.
 
 <prot.h> NOT found.
 
 Guessing which symbols your C compiler and preprocessor define...
 Your C pre-processor defines the following symbols:
 __ELF__
 __GNUC__
 __GNUC_MINOR__
 _LP64
 __LP64__
 __NetBSD__
 __STDC__
 __alpha
 __alpha__
 __unix__
 
 tcsetattr() found.
 
 You have POSIX termios.h... good!
 
 <shadow.h> NOT found.
 
 <stdarg.h> found.
 
 <varargs.h> found.
 
 We'll include <stdarg.h> to get va_dcl definition.
 
 <stddef.h> found.
 
 <sunmath.h> NOT found.
 
 <sys/access.h> NOT found.
 
 <sys/filio.h> found.
 
 <sys/ioctl.h> found.
 
 <syslog.h> found.
 
 <sys/mode.h> NOT found.
 
 <sys/resource.h> found.
 
 <sys/security.h> NOT found.
 
 <sys/statvfs.h> found.
 
 <sys/uio.h> found.
 
 <sys/un.h> found.
 
 <sys/utsname.h> found.
 
 <sys/wait.h> found.
 
 <ustat.h> NOT found.
 
 <utime.h> found.
 
 <values.h> NOT found.
 
 <gdbm.h> NOT found.
 
 Looking for extensions...
 A number of extensions are supplied with perl5.  You may choose to
 compile these extensions for dynamic loading (the default), compile
 them into the perl5 executable (static loading), or not include
 them at all.  Answer "none" to include no extensions.
 Note that DynaLoader is always built and need not be mentioned here.
 
 What extensions do you wish to load dynamically?
 [B ByteLoader DB_File Data/Dumper Devel/DProf Devel/Peek Fcntl 
 File/Glob IO IPC/SysV NDBM_File Opcode POSIX SDBM_File Socket 
 Sys/Hostname Sys/Syslog attrs re]
 What extensions do you wish to load statically? [none]
 
 
 End of configuration questions.
 
 
 Stripping down executable paths...
 
 Creating config.sh...
 
 If you'd like to make any changes to the config.sh file before I begin
 to configure things, do it as a shell escape now (e.g. !vi config.sh).
 
 Press return or use a shell escape to edit config.sh:
 
 Doing variable substitutions on .SH files...
 Extracting Makefile (with variable substitutions)
 Extracting Policy.sh (with variable substitutions)
 Extracting cflags (with variable substitutions)
 Extracting config.h (with variable substitutions)
 Extracting makeaperl (with variable substitutions)
 Extracting makedepend (with variable substitutions)
 Extracting makedir (with variable substitutions)
 Extracting myconfig (with variable substitutions)
 Extracting pod/Makefile (with variable substitutions)
 Extracting writemain (with variable substitutions)
 Extracting x2p/Makefile (with variable substitutions)
 Extracting x2p/cflags (with variable substitutions)
 
 Now you need to generate make dependencies by running "make depend".
 You might prefer to run it in background: "make depend > makedepend.out &"
 It can take a while, so you might not want to run it right now.
 
 Run make depend now? [y]
 sh ./makedepend MAKE=make
 sh writemain lib/auto/DynaLoader/DynaLoader.a  > writemain.tmp
 sh mv-if-diff writemain.tmp perlmain.c
 echo malloc.c av.c scope.c op.c doop.c doio.c dump.c hv.c mg.c perl.c 
 perly.c pp.c pp_hot.c pp_ctl.c pp_sys.c regcomp.c regexec.c utf8.c 
 gv.c sv.c taint.c toke.c util.c deb.c run.c universal.c xsutils.c 
 globals.c perlio.c perlapi.c miniperlmain.c perlmain.c | tr ' ' 
 '\n' >.clist
 ./makedepend: 1: Syntax error: Unterminated quoted string
 *** Error code 2
 
 Stop.
 make: stopped in /usr/home/ray/installers/perl/5.6.1/perl-5.6.1
 
 If you compile perl5 on a different machine or from a different object
 directory, copy the Policy.sh file from this object directory to the
 new one before you run Configure -- this will help you with most of
 the policy defaults.
 
 %