Обсуждение: run_check problem

Hi all,

I'm getting an error in run_check.sh on Solaris.


MULTIBYTE=;export MULTIBYTE; \
/bin/sh ./run_check.sh solaris_sparc
awk: syntax error near line 1
awk: illegal statement near line 1
awk: syntax error near line 2
awk: illegal statement near line 2
=============== Create ./tmp_check directory           ================
.
.


This is due to 2 problems.

1) The awk script is broken over 2 lines.
2) Solaris's awk does not seem to understand REs in split(). (nawk's OK)

1 is easy to fix, 2 is tricky - to remain portable.

Keith.

>
> Hi all,
>
> I'm getting an error in run_check.sh on Solaris.
>
>
> MULTIBYTE=;export MULTIBYTE; \
> /bin/sh ./run_check.sh solaris_sparc
> awk: syntax error near line 1
> .
> .
>
> 1) The awk script is broken over 2 lines.
> 2) Solaris's awk does not seem to understand REs in split(). (nawk's OK)

    Argh  -  now  I remember why we tried to avoid awk as much as
    possible.  Why do the sun guy's ship such a crippled  version
    for  a  good  old UNIX V7 tool? I rememver that MINIX already
    had a better one! DAMNED BLOODY MOTHERF...

    And I discovered  another  problem  with  it  too.  The  path
    replacements  in  various  scripts  (especially those loading
    shared objects at runtime) need to use the ones from the temp
    installation. But that's surely hackable.


Jan

--

#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#========================================= wieck@debis.com (Jan Wieck) #

Keith Parks <emkxp01@mtcc.demon.co.uk> writes:
> This is due to 2 problems.
> 1) The awk script is broken over 2 lines.
> 2) Solaris's awk does not seem to understand REs in split(). (nawk's OK)

I don't think so --- the exact same split() construct is there in the
old regress.sh test driver, same as it ever was.  I can believe the line
break is a problem, but if there's another problem then you need to
keep digging.

Comparing the two scripts, I wonder if Jan broke it by adding '/bin/sh'
to the invocation of config.guess.  Doesn't seem very likely, but...
        regards, tom lane