Re: Weird problem on -current from today

[Robert Elz <kre%munnari.OZ.AU@localhost>]

    Date:        Sat, 12 Oct 2024 22:12:26 +0100
    From:        Chavdar Ivanov <ci4ic4%gmail.com@localhost>
    Message-ID:  <CAG0OUxhrWw-mZ=H_bGkrysr11TuBDcdpUbWz4sftBTOUML+EJg%mail.gmail.com@localhost>

  | Any pkgsrc package containing a configure script bombs out with

  | configure: error: cannot run /bin/sh ./config.sub

Send me the config.sub file and I will have a look and see if
one of the recent sh changes broke it it some way.

But I won't be able to reply directly, gmail won't take mail
from me (I simply refuse to attempt to comply with their
idiotic rules).

  | Running '/bin/sh -xv ./configure' and capturing the output/error
  | stream doesn't suggest me at this moment:
  | ...
  |   # Make sure we can run config.sub.
  | $SHELL "${ac_aux_dir}config.sub" sun4 >/dev/null 2>&1 ||
  |   as_fn_error $? "cannot run $SHELL ${ac_aux_dir}config.sub" "$LINENO" 5
  | + /bin/sh ./config.sub sun4 >/dev/null 2>&1
  | + as_fn_error 1 'cannot run /bin/sh ./config.sub' 3583 5

No, you'd need to run config.sub with -x to see what it is doing.
Or repeat your manual execution, add -X (capital X) and direct stderr
to a file, and remember to give it its required "sun4" arg

	sh -X config.sub sun4 2>/tmp/STDERR

and if that means you're doing this on a sparc system, then
you might need to provide the debugging, as I can't duplicate that)

Then send me (or the list if it is small enough) that file (/tmp/STDERR).

I'm also very surprised any config script anywhere is ever going to
want to run anything with sh's -q option.   That's unexpected, and weird.

kre