Current-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Weird problem on -current from today



Hi,

I did a full rebuild of -current amd64 today, I have

❯ uname -a
NetBSD ym1r.lorien.lan 10.99.12 NetBSD 10.99.12 (GENERIC) #1: Sat Oct
12 15:25:39 BST 2024
root%ym1r.lorien.lan@localhost:/bd/sysbuild/amd64/obj/home/sysbuild/src/sys/arch/amd64/compile/GENERIC
amd64

Any pkgsrc package containing a configure script bombs out with

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

Manually running the above works as expected:

❯ /bin/sh ./config.sub
config.sub: missing argument
Try `config.sub --help' for more information.

If I replace - for a moment - /bin/sh with /bin/ksh (not expecting the
builds to finish of course, just for the test) - the configure
continues further (but fails on, e.g.

--- Programs/python.o ---
sh: sh: -q: unknown option
sh:
*** [Programs/python.o] Error code 1

make: stopped making "all" in /bd/pkgsrc/lang/python312/work/Python-3.12.7
make: 2 errors )

which is expected, I guess, as ksh doesn't have -q option.

Has anybody seen behaviour like that? Just in case, I recreated the
current pkgsrc tree, to no effect. I imagine the system rebuild with
fail as well after that, so I might have to reinstall this system...

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
+ as_status=1
+ test 1 -eq 0
+ test 5
+ as_lineno=3583 as_lineno_stack=as_lineno_stack=
+ printf '%s\n' 'configure:3583: error: cannot run /bin/sh ./config.sub' >&5
+ printf '%s\n' 'configure: error: cannot run /bin/sh ./config.sub' >&2
configure: error: cannot run /bin/sh ./config.sub
+ as_fn_exit 1
+ set +e
+ as_fn_set_status 1
+ return 1
+ exit 1
+ exit_status=1
+ IFS='
....

I booted the system with the previous kernel from 01/10, this did not
change anything (by the way, before today's system rebuild I had also
a full pkg_rolling-replace without any problems).


As otherwise the system works OK (I just rebuilt and tested

zig version
0.14.0-dev.1888+7e530c13b

off pkgsrc tree using again off-pkgsec llvm 19.1.0), I might resort to
eventually getting a known good -current from releng server.

If that matters, the machine is a guest on a ProxMox server and has
been running for some six months now, replacing my former NetBSD box.

Chavdar




-- 
----


Home | Main Index | Thread Index | Old Index