Two things ring alarm in the log you posted:

first, the output of sh -x Configure ...

+ + echo AIX
+ /usr/bin/sed -e s/[   ][      ]*/_/g
+ ./tr [A-Z] [a-z]
[download]

I am not acquainted much with the output of sh -x But I assume that what follows a plus sign is a command executed in current shell and whatever commands are preceded by two-or-more plus signs were executed in sub-shells therein. For example:

sh -x -e "echo abc | sed s'/a/b/'"

+ echo abc
+ sed s/a/b/
bbc
[download]

whereas,

sh -x -c 'z=`echo abc | sed "s/a/b/"`'

++ echo abc
++ sed s/a/b/
+ z=bbc
[download]

So, the output you posted has echo AIX in a sub-shell and following sed and tr commands are executed on current shell. But *if* that output is at corresponds to this Configure part:

rp="Operating system name?"
. ./myread
case "$ans" in
none)  osname='' ;;
*) osname=`echo "$ans" | $sed -e 's/[   ][      ]*/_/g' | ./tr '[A-Z]'
+ '[a-z]'`;;
esac
[download]

Then echo, sed, tr should have all been preceded by 2 plus signs as they are all part of one single `...`.

The second alarm is that $sed is a variable which refers to some sed executable I guess. But it is worth investigating what it actually contains. Also, ./tr is not the same as tr. It probably is another script created on the fly and it is used instead of /usr/bin/tr. So, it is also worth finding out what that ./tr file contains...

So, I suggest to add some debugging lines in Configure (sorry if that contradicts the other advice you got about not modifying that file, which is correct but this is special and once you sort things out you will go back to original Configure and discard any perl executable may have been produced). Something like this perhaps (untested):

rp="Operating system name?"
. ./myread
case "$ans" in
none)  osname='' ;;
*) echo "AAAA: ans='${ans}', sed='${sed}', Here is tr:"
cat ./tr
echo "BBBB: done cat tr"
osname=`echo "$ans" | $sed -e 's/[   ][      ]*/_/g' | ./tr '[A-Z]' '[
+a-z]'`
echo "CCCC: osname='${osname}'"
;;
esac
echo " "
echo "XXXXXX out of case with this osname='${osname}'"
[download]

bw, bliako

p.s. Although the log was posted in another node of this post, I chose to create a new comment/answer to avoid clutter.

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.