App-Staticperl v1.46 Perl 5 v5.40.0 aarch64-freebsd

Status: Fail
From: Slaven Rezić
Dist: App-Staticperl v1.46
Platform: Perl 5 v5.40.0 aarch64-freebsd
Date: 2024-10-16 02:14:35
ID: 6385e140-8b64-11ef-af6f-a3426e8775ea

This distribution has been tested as part of the CPAN Testers
project, supporting the Perl programming language. See
http://wiki.cpantesters.org/ for more information or email
questions to cpan-testers-discuss@perl.org

--
Dear Marc A. Lehmann,

This is a computer-generated report for App-Staticperl-1.46
on perl 5.40.0, created by CPAN-Reporter-1.2019.

Thank you for uploading your work to CPAN. However, there was a problem
testing your distribution.

If you think this report is invalid, please consult the CPAN Testers Wiki
for suggestions on how to avoid getting FAIL reports for missing library
or binary dependencies, unsupported operating systems, and so on:

http://wiki.cpantesters.org/wiki/CPANAuthorNotes

Sections of this report:

* Tester comments
* Program output
* Prerequisites
* Environment and other context

------------------------------
TESTER COMMENTS
------------------------------

Additional comments from tester:

none provided

------------------------------
PROGRAM OUTPUT
------------------------------

Output from '/usr/bin/make test':

PERL_DL_NONLAZY=1 "/usr/perl5.40.0/bin/perl" "-MExtUtils::Command::MM" "-MTest::Harness" "-e" "undef *Test::Harness::Switches; test_harness(0, 'blib/lib', 'blib/arch')" t/*.t

# FAILED #2 exit status 0x0100 (sh bin/staticperl install)

# OUTPUT:
0K .......... .......... .......... .......... .......... 73% 446M 0s
8850K .......... .......... .......... .......... .......... 73% 152M 0s
8900K .......... .......... .......... .......... .......... 74% 453M 0s
8950K .......... .......... .......... .......... .......... 74% 132M 0s
9000K .......... .......... .......... .......... .......... 75% 2.27T 0s
9050K .......... .......... .......... .......... .......... 75% 453M 0s
9100K .......... .......... .......... .......... .......... 75% 136M 0s
9150K .......... .......... .......... .......... .......... 76% 445M 0s
9200K .......... .......... .......... .......... .......... 76% 142M 0s
9250K .......... .......... .......... .......... .......... 77% 443M 0s
9300K .......... .......... .......... .......... .......... 77% 61.2M 0s
9350K .......... .......... .......... .......... .......... 77% 42.9M 0s
9400K .......... .......... .......... .......... .......... 78% 2.27T 0s
9450K .......... .......... .......... .......... .......... 78% 386M 0s
9500K .......... .......... .......... .......... .......... 79% 113M 0s
9550K .......... .......... .......... .......... .......... 79% 111M 0s
9600K .......... .......... .......... .......... .......... 80% 605M 0s
9650K .......... .......... .......... .......... .......... 80% 124M 0s
9700K .......... .......... .......... .......... .......... 80% 135M 0s
9750K .......... .......... .......... .......... .......... 81% 92.7M 0s
9800K .......... .......... .......... .......... .......... 81% 127M 0s
9850K .......... .......... .......... .......... .......... 82% 2.27T 0s
9900K .......... .......... .......... .......... .......... 82% 40.2M 0s
9950K .......... .......... .......... .......... .......... 82% 451M 0s
10000K .......... .......... .......... .......... .......... 83% 117M 0s
10050K .......... .......... .......... .......... .......... 83% 414M 0s
10100K .......... .......... .......... .......... .......... 84% 149M 0s
10150K .......... .......... .......... .......... .......... 84% 418M 0s
10200K .......... .......... .......... .......... .......... 84% 144M 0s
10250K .......... .......... .......... .......... .......... 85% 2.27T 0s
10300K .......... .......... .......... .......... .......... 85% 121M 0s
10350K .......... .......... .......... .......... .......... 86% 2.27T 0s
10400K .......... .......... .......... .......... .......... 86% 420M 0s
10450K .......... .......... .......... .......... .......... 87% 171M 0s
10500K .......... .......... .......... .......... .......... 87% 494M 0s
10550K .......... .......... .......... .......... .......... 87% 151M 0s
10600K .......... .......... .......... .......... .......... 88% 463M 0s
10650K .......... .......... .......... .......... .......... 88% 152M 0s
10700K .......... .......... .......... .......... .......... 89% 457M 0s
10750K .......... .......... .......... .......... .......... 89% 156M 0s
10800K .......... .......... .......... .......... .......... 89% 2.27T 0s
10850K .......... .......... .......... .......... .......... 90% 391M 0s
10900K .......... .......... .......... .......... .......... 90% 49.5M 0s
10950K .......... .......... .......... .......... .......... 91% 75.6M 0s
11000K .......... .......... .......... .......... .......... 91% 2.27T 0s
11050K .......... .......... .......... .......... .......... 92% 89.3M 0s
11100K .......... .......... .......... .......... .......... 92% 2.27T 0s
11150K .......... .......... .......... .......... .......... 92% 158M 0s
11200K .......... .......... .......... .......... .......... 93% 58.1M 0s
11250K .......... .......... .......... .......... .......... 93% 2.27T 0s
11300K .......... .......... .......... .......... .......... 94% 349M 0s
11350K .......... .......... .......... .......... .......... 94% 67.1M 0s
11400K .......... .......... .......... .......... .......... 94% 76.5M 0s
11450K .......... .......... .......... .......... .......... 95% 62.7M 0s
11500K .......... .......... .......... .......... .......... 95% 2.27T 0s
11550K .......... .......... .......... .......... .......... 96% 193M 0s
11600K .......... .......... .......... .......... .......... 96% 82.9M 0s
11650K .......... .......... .......... .......... .......... 97% 338M 0s
11700K .......... .......... .......... .......... .......... 97% 71.2M 0s
11750K .......... .......... .......... .......... .......... 97% 2.27T 0s
11800K .......... .......... .......... .......... .......... 98% 281M 0s
11850K .......... .......... .......... .......... .......... 98% 317M 0s
11900K .......... .......... .......... .......... .......... 99% 247M 0s
11950K .......... .......... .......... .......... .......... 99% 2.27T 0s
12000K .......... .......... .......... .......... .......... 99% 343M 0s
12050K .......... 100% 507G=0.1s

2024-10-15 20:12:22 (79.1 MB/s) - 'perl-5.12.4.tar.bz2~' saved [12350353/12350353]

***
*** unpacking perl
***

***
*** configuring /tmp/staticperltest9935/src/perl
***

Configure: use '-U symbol=', not '-D symbol='.
Configure: ignoring -D optimize=
Configure: use '-U symbol=', not '-D symbol='.
Configure: ignoring -D ldflags=

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) 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.
chmod is in /bin/chmod.
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/local/bin/grep.
ls is in /bin/ls.
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...
ar is in /usr/local/bin/ar.
I don't see bison out there, offhand.
byacc is in /usr/bin/byacc.
cpp is in /usr/bin/cpp.
csh is in /bin/csh.
date is in /bin/date.
egrep is in /usr/local/bin/egrep.
gmake is in /usr/local/bin/gmake.
gzip is in /usr/local/bin/gzip.
less is in /usr/bin/less.
ln is in /bin/ln.
make is in /usr/bin/make.
more is in /usr/bin/more.
nm is in /usr/local/bin/nm.
nroff is in /usr/local/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.
Substituting less -R for less.
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.
The following message is sponsored by

Dresden.pm<--The stars should be here.

Dear Perl user, system administrator or package
maintainer, the Perl community sends greetings to
you. Do you (emblematical) greet back [Y/n]? n

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 dos_djgpp irix_6 openbsd sunos_4_1
aix dragonfly irix_6_0 opus super-ux
aix_3 dynix irix_6_1 os2 svr4
aix_4 dynixptx isc os390 svr5
altos486 epix isc_2 os400 ti1500
amigaos esix4 linux posix-bc titanos
apollo fps lynxos powerux ultrix_4
atheos freebsd midnightbsd qnx umips
aux_3 genix mips rhapsody unicos
beos gnu mirbsd riscos unicosmk
bsdos gnukfreebsd mpc sco unisysdynix
catamount gnuknetbsd mpeix sco_2_3_0 utekv
convexos greenhills ncr_tower sco_2_3_1 uts
cxux haiku netbsd sco_2_3_2 uwin
cygwin hpux newsos4 sco_2_3_3 vmesa
darwin i386 next_3 sco_2_3_4 vos
dcosx interix next_3_0 solaris_2
dec_osf irix_4 next_4 stellar
dgux irix_5 nonstopux sunos_4_0

You may give one or more space-separated answers, or "none" if appropriate.
If you have a handcrafted Policy.sh file or a Policy.sh file generated by a
previous run of Configure, you may specify it as well as or instead of
OS-specific hints. If hints are provided for your OS, you should use them:
although Perl can probably be built without hints on many platforms, using
hints often improve performance and may enable features that Configure can't
set up on its own. If there are no hints that match your OS, specify "none";
DO NOT give a wrong version or a wrong OS.

Which of these apply, if any? [freebsd]

Some users have reported that Configure halts when testing for
the O_NONBLOCK symbol with a syntax error. This is apparently a
sh error. Rerunning Configure with ksh apparently fixes the
problem. Try
ksh Configure [your options]

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? [freebsd]

Operating system version? [14.1-stable]

By default, perl5 will be installed in /tmp/staticperltest9935/perl/bin, manual pages
under /tmp/staticperltest9935/perl/man, etc..., i.e. with /tmp/staticperltest9935/perl 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) [/tmp/staticperltest9935/perl]

AFS does not seem to be running...

In some special cases, particularly when building perl5 for distribution,
it is convenient to distinguish the directory in which files should be
installed from the directory (/tmp/staticperltest9935/perl) 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)
[/tmp/staticperltest9935/perl]

Perl can be built to use the SOCKS proxy protocol library. To do so,
Configure must be run with -Dusesocks. If you use SOCKS you also need
to use the PerlIO abstraction layer, this will be implicitly selected.

If this doesn't make any sense to you, just accept the default 'n'.
Build Perl for SOCKS? [n]

Previous version of perl5 used the standard IO mechanisms as
defined in <stdio.h>. Versions 5.003_02 and later of perl5 allow
alternate IO mechanisms via the PerlIO abstraction layer, but the
stdio mechanism is still available if needed. The 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.

If this doesn't make any sense to you, just accept the default 'y'.
Use the PerlIO abstraction layer? [y]

Getting the current patchlevel...
egrep: warning: egrep is obsolescent; using /usr/local/bin/ggrep -E
(You have perl5 version 12 subversion 4.)

Perl can be built to take advantage of threads on some systems.
To do so, Configure can be run with -Dusethreads.

Note that Perl built with threading support runs slightly slower
and uses more memory than plain Perl. The current implementation
is believed to be stable, but it is fairly new, and so should be
treated with caution.

If this doesn't make any sense to you, just accept the default 'n'.
Build a threading Perl? [n]
Your platform has some specific hints regarding threaded builds, using them...

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]

Use which C compiler? [cc]

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...

Checking for GNU cc in disguise and/or its version number...
You are using GNU cc FreeBSD Clang 18.1.6 (https://github.com/llvm/llvm-project.git llvmorg-18.1.6-0-g1118c2e05e67).

Hmm... Doesn't look like a MIPS system.

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.

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? [/usr/local/lib /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 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 for optional libraries...
No -lsfio.
No -lsocket.
No -lbind.
No -linet.
No -lnsl.
No -lnm.
No -lndbm.
Found -lgdbm (shared).
No -ldbm.
No -ldb.
Found -ldl (shared).
No -ldld.
No -lld.
No -lsun.
Found -lm (shared).
Found -lcrypt (shared).
No -lsec.
Found -lutil (shared).
Found -lc (shared).
No -lcposix.
No -lposix.
No -lucb.
No -lbsd.
No -lBSD.

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? [-lgdbm -ldl -lm -lcrypt -lutil -lc]

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.

Checking if your compiler accepts -pipe
Yes, it does.

Checking if your compiler accepts -fno-stack-protector
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 -pipe -fno-stack-protector -I/usr/local/include]

Let me guess what the preprocessor flags are...
They appear to be: -fno-strict-aliasing -pipe -fno-stack-protector -I/usr/local/include

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
/usr/local/lib /lib /usr/lib
To use no flags, specify the word "none".

Any additional ld flags (NOT including libraries)?
[ -fno-stack-protector -L/usr/local/lib]

Checking your choice of C compiler and flags for coherency...
OK, that should do.

Computing filename position in cpp output for #include directives...
Your cpp writes the filename in the third field of the line.

<stdlib.h> found.

Checking to see how big your integers are...
Your integers are 4 bytes long.
Your long integers are 8 bytes long.
Your short integers are 2 bytes long.

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.)

<inttypes.h> found.

Checking to see if you have int64_t...
You have int64_t.

Checking which 64-bit integer type we could use...
We could use 'long' for 64-bit integers.

You have natively 64-bit long integers.
Hmm. Based on the hints in hints/freebsd.sh,
the recommended value for $use64bitint on this machine was "undef"!
Keep the recommended value? [y]

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'.
(The default has been chosen based on your configuration.)
Try to use maximal 64-bit support, if available? [y]

Since you have chosen a maximally 64-bit build, I'm also turning on
the use of 64-bit integers.

Checking to see how big your double precision numbers are...
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 16 bytes long.

What is your architecture name [arm64-freebsd]
This architecture is naturally 64-bit, not changing architecture name.
Perlio selected.

Pathname where the public executables will reside? (~name ok)
[/tmp/staticperltest9935/perl/bin]
Directory /tmp/staticperltest9935/perl/bin doesn't exist. Use that name anyway?
[y]

Would you like to build Perl so that the installation is relocatable, so that
library paths in @INC are determined relative to the path of the perl binary?
This is not advised for system Perl installs, or if you need to run setid
scripts or scripts under taint mode.

If this doesn't make any sense to you, just accept the default 'n'.
Use relocatable @INC? [n]

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)
[/tmp/staticperltest9935/perl/lib]

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)
[/tmp/staticperltest9935/perl/lib]

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]
Looking for a previously installed perl5.005 or later...
Using /usr/local/bin/perl.

After perl5 is installed, you may wish to install various
add-on modules and utilities. Typically, these add-ons will
be installed under /tmp/staticperltest9935/perl 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)
[/tmp/staticperltest9935/perl]

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)
[/tmp/staticperltest9935/perl/lib]

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 /tmp/staticperltest9935/perl. Specify here
the list of earlier versions that this version of perl should check.
If Configure detected no earlier versions of perl installed under
/tmp/staticperltest9935/perl, 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]

<malloc/malloc.h> NOT found.

<malloc.h> found.

Checking to see how well your C compiler groks the void type...
Good. It appears to support void to the level perl5 wants.

Checking to see how big your pointers are...
Your pointers are 8 bytes long.

Do you wish to wrap malloc calls to protect against potential overflows? [y]

Do you wish to attempt to use the malloc that comes with perl5? [n]

Your system wants malloc to return 'void *', it would seem.
Your system uses void free(), it would seem.

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)
[/tmp/staticperltest9935/perl/lib]

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
/tmp/staticperltest9935/perl/lib
/tmp/staticperltest9935/perl/lib

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.

Perl can be built to support DTrace on platforms that support it.
DTrace is a diagnosis and performance analysis tool from Sun.

If this doesn't make any sense to you, just accept the default 'none'.
Support DTrace if available? [n]

Perl can be built with extra modules or bundles of modules which
will be fetched from the CPAN and installed alongside Perl.

Notice that you will need access to the CPAN; either via the Internet,
or a local copy, for example a CD-ROM or a local CPAN mirror. (You will
be asked later to configure the CPAN.pm module which will in turn do
the installation of the rest of the extra modules or bundles.)

Notice also that if the modules require any external software such as
libraries and headers (the libz library and the zlib.h header for the
Compress::Zlib module, for example) you MUST have any such software
already installed, this configuration process will NOT install such
things for you.

If this doesn't make any sense to you, just accept the default 'n'.
Install any extra modules (y or n)? [n]

If you wish to install html files for programs in Perl5, indicate
the appropriate directory here. To skip installing html files,
answer "none".
Directory for the main Perl5 html pages? (~name ok) [none]

If you wish to install html files for modules associated with Perl5,
indicate the appropriate directory here. To skip installing html files,
answer "none".
Directory for the Perl5 module html pages? (~name ok) [none]

Many scripts expect perl to be installed as /usr/bin/perl.

If you want to, I can install the perl you are about to compile
as /usr/bin/perl (in addition to /tmp/staticperltest9935/perl/bin/perl).

However, please note that because you already have a /usr/bin/perl,
overwriting that with a new Perl would very probably cause problems.
Therefore I'm assuming you don't want to do that (unless you insist).

Do you want to install perl as /usr/bin/perl? [n]

Checking for GNU C Library...
You are not using the GNU C Library
egrep: warning: egrep is obsolescent; using /usr/local/bin/ggrep -E

I can use /usr/local/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/local/bin/nm to extract C symbols from the libraries? [y]

egrep: warning: egrep is obsolescent; using /usr/local/bin/ggrep -E
egrep: warning: egrep is obsolescent; using /usr/local/bin/ggrep -E
Your (shared) C library seems to be in /lib/libc.so.7.

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.7]

Extracting names from the following files for later perusal:

/lib/libc.so.7
/lib/libcrypt.so.5
/lib/libm.so.5
/lib/libutil.so.9
/usr/lib/libdl.so.1
/usr/local/lib/libgdbm.so.6.0.0

This may take a while...................
/usr/local/bin/nm didn't seem to work right. Trying /usr/local/bin/ar instead...
/usr/local/bin/ar: /lib/libc.so.7: file format not recognized
/usr/local/bin/ar didn't seem to work right.
Maybe this is a Cray...trying bld instead...
Configure: bld: not found
That didn't work either. Giving up.

***
*** Configure failed - see above for the exact error message(s).
***
*** Most commonly, this is because the default PERL_CCFLAGS or PERL_OPTIMIZE
*** flags are not supported by your compiler. Less often, this is because
*** PERL_LIBS either contains a library not available on your system (such as
*** -lcrypt), or because it lacks a required library (e.g. -lsocket or -lnsl).
***
*** You can provide your own flags by creating a ~/.staticperlrc file with
*** variable assignments. For example (these are the actual values used):
***

PERL_CC="cc"
PERL_CCFLAGS=""
PERL_OPTIMIZE=""
PERL_LDFLAGS=""
PERL_LIBS="-lm -lcrypt"

# FAILED #3 exit status 0x0100 (sh bin/staticperl instcpan Games::Go::SimpleBoard)

# OUTPUT:

***
*** configuring /tmp/staticperltest9935/src/perl
***

Configure: use '-U symbol=', not '-D symbol='.
Configure: ignoring -D optimize=
Configure: use '-U symbol=', not '-D symbol='.
Configure: ignoring -D ldflags=

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...

Would you like to see the instructions? [n]