win11-msys2-perl-pr18492-configure

$  sh Configure -de -Dusedevel -Dprefix=$HOME/myperl -DDEBUGGING -Dman1dir=none -Dman3dir=none

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.

Every time 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 (https://github.com/Perl/perl5/issues) 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 /usr/bin/cat.
chmod is in /usr/bin/chmod.
comm is in /usr/bin/comm.
cp is in /usr/bin/cp.
echo is in /usr/bin/echo.
expr is in /usr/bin/expr.
grep is in /usr/bin/grep.
ls is in /usr/bin/ls.
mkdir is in /usr/bin/mkdir.
rm is in /usr/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/bin/ar.
bison is in /usr/bin/bison.
I don't see byacc out there, offhand.
cpp is in /usr/bin/cpp.
I don't see csh out there, either.
date is in /usr/bin/date.
egrep is in /usr/bin/egrep.
I don't see gmake out there, either.
gzip is in /usr/bin/gzip.
less is in /usr/bin/less.
ln is in /usr/bin/ln.
make is in /usr/bin/make.
more is in /usr/bin/more.
nm is in /usr/bin/nm.
nroff is in /usr/bin/nroff.
perl is in /usr/bin/perl.
pg is in /usr/bin/pg.
test is in /usr/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 /usr/bin/echo.exe 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...
/usr/bin/ln: failed to create symbolic link 'sym': No such file or directory
Your builtin 'test -h' may be broken.
Trying external '/usr/bin/test -h'.
External '/usr/bin/test -h' is broken, too.
I do not know how you can test for symbolic links.
Checking for cross-compile
No targethost for running compiler tests against defined, running locally

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:

aix           dragonfly       irix_4            ncr_tower     sco_2_3_3
aix_3         dynix           irix_5            netbsd        sco_2_3_4
aix_4         dynixptx        irix_6            newsos4       solaris_2
altos486      epix            irix_6_0          nonstopux     stellar
amigaos       esix4           irix_6_1          openbsd       sunos_4_0
atheos        fps             isc               opus          sunos_4_1
aux_3         freebsd         isc_2             os2           super-ux
bitrig        freemint        linux-android     os390         svr4
bsdos         gnu             linux             os400         svr5
catamount     gnukfreebsd     lynxos            posix-bc      ti1500
convexos      gnuknetbsd      midnightbsd       qnx           umips
cxux          greenhills      minix             riscos        unicos
cygwin        haiku           mips              sco           unicosmk
darwin        hpux            mirbsd            sco_2_3_0     unisysdynix
dcosx         i386            mpc               sco_2_3_1     utekv
dec_osf       interix         msys              sco_2_3_2     vos

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

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

Operating system version? [3.3.6-341.x86_64]

By default, perl5 will be installed in /home/hakon/myperl/bin, manual pages
under /home/hakon/myperl/man, etc..., i.e. with /home/hakon/myperl 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) [/home/hakon/myperl]
Directory /home/hakon/myperl doesn't exist.  Use that name anyway? [y]

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 (/home/hakon/myperl) 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) [/home/hakon/myperl]
Directory /home/hakon/myperl doesn't exist.  Use that name anyway? [y]

Perl can be built to offer a form of threading support on some systems
To do so, Configure can be run with -Dusethreads.

Note that Perl built with threading support runs slightly slower
and uses slightly more memory than plain Perl.

If this doesn't make any sense to you, just accept the default 'y'.
Build a threading Perl? [y]
(Your platform does not have any specific hints for threaded builds.
 Assuming POSIX threads, then.)

Perl can be built so that multiple Perl interpreters can coexist
within the same Perl executable.
This multiple interpreter support is required for interpreter-based threads.

Use which C compiler? [gcc]

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...
Configure: line 4606: ./try: cannot execute binary file: Exec format error
You are not using GNU cc.
Configure: line 4726: ./try: cannot execute binary file: Exec format error
Configure: line 4726: ./try: cannot execute binary file: Exec format error
Configure: line 4726: ./try: cannot execute binary file: Exec format error
Your C compiler doesn't seem to be able to compile C99 code
Do you really want to continue? [n]