>>> Building on sparc64-0d under lang/verilator BDEPENDS = [devel/metaauto;devel/autoconf/2.72;lang/gcc/15,-c++;devel/gmake;lang/gcc/15,-libs;devel/bison;devel/help2man;lang/gcc/15] DIST = [lang/verilator:verilator-5.044.tar.gz] FULLPKGNAME = verilator-5.044 RDEPENDS = [lang/gcc/15,-libs] (Junk lock obtained for sparc64-0d at 1771634020.41) >>> Running depends in lang/verilator at 1771634020.52 last junk was in textproc/aspell/core /usr/sbin/pkg_add -aI -Drepair autoconf-2.72p0 bison-3.8.2p0 help2man-1.49.3 was: /usr/sbin/pkg_add -aI -Drepair autoconf-2.72p0 bison-3.8.2p0 g++-15.2.0p5 gcc-15.2.0p5 gcc-libs-15.2.0p5 gmake-4.4.1p0 help2man-1.49.3 metaauto-1.0p4 /usr/sbin/pkg_add -aI -Drepair autoconf-2.72p0 bison-3.8.2p0 help2man-1.49.3 >>> Running show-prepare-results in lang/verilator at 1771634036.27 ===> lang/verilator ===> Building from scratch verilator-5.044 ===> verilator-5.044 depends on: bison-* -> bison-3.8.2p0 ===> verilator-5.044 depends on: help2man-* -> help2man-1.49.3 ===> verilator-5.044 depends on: metaauto-* -> metaauto-1.0p4 ===> verilator-5.044 depends on: autoconf-2.72 -> autoconf-2.72p0 ===> verilator-5.044 depends on: gcc->=15,<16 -> gcc-15.2.0p5 ===> verilator-5.044 depends on: g++->=15,<16 -> g++-15.2.0p5 ===> verilator-5.044 depends on: gmake-* -> gmake-4.4.1p0 ===> verilator-5.044 depends on: gcc-libs->=15,<16 -> gcc-libs-15.2.0p5 ===> Verifying specs: c m estdc++>=21 pthread ===> found c.102.2 m.10.1 estdc++.21.0 pthread.28.1 autoconf-2.72p0 bison-3.8.2p0 g++-15.2.0p5 gcc-15.2.0p5 gcc-libs-15.2.0p5 gmake-4.4.1p0 help2man-1.49.3 metaauto-1.0p4 (Junk lock released for sparc64-0d at 1771634048.01) distfiles size=5474674 >>> Running patch in lang/verilator at 1771634048.14 ===> lang/verilator ===> Checking files for verilator-5.044 `/usr/ports/distfiles/verilator-5.044.tar.gz' is up to date. >> (SHA256) all files: OK ===> Extracting for verilator-5.044 ===> Patching for verilator-5.044 ===> Applying OpenBSD patch patch-bin_verilator Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |Index: bin/verilator |--- bin/verilator.orig |+++ bin/verilator -------------------------- Patching file bin/verilator using Plan A... Hunk #1 succeeded at 101. Hunk #2 succeeded at 124. Hunk #3 succeeded at 185. done ===> Applying OpenBSD patch patch-test_regress_driver_py Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |Index: test_regress/driver.py |--- test_regress/driver.py.orig |+++ test_regress/driver.py -------------------------- Patching file test_regress/driver.py using Plan A... Hunk #1 succeeded at 193. Hunk #2 succeeded at 1538. Hunk #3 succeeded at 1859. done ===> Compiler link: gcc -> /usr/local/bin/egcc ===> Compiler link: cc -> /usr/local/bin/egcc ===> Compiler link: c++ -> /usr/local/bin/eg++ ===> Compiler link: g++ -> /usr/local/bin/eg++ >>> Running configure in lang/verilator at 1771634056.66 ===> lang/verilator ===> Generating configure for verilator-5.044 Running autoconf-2.72 in /usr/obj/ports/verilator-5.044/verilator-5.044 ===> Configuring for verilator-5.044 Using /usr/obj/ports/verilator-5.044/config.site (generated) configure: WARNING: unrecognized options: --disable-gtk-doc configure: loading site script /usr/obj/ports/verilator-5.044/config.site configuring for Verilator 5.044 2026-01-01 checking whether to perform partial static linking of Verilator binary... yes checking whether to use AddressSanitizer... no checking whether to use tcmalloc... check checking whether to build for gcov code coverage collection... no checking whether to use hardcoded paths... yes checking whether to show and stop on compilation warnings... no checking whether to run long tests... no checking for z3... no checking for cvc5... no checking for cvc4... no checking for SMT solver... no compiler CXX inbound is set to... c++ checking for gcc... cc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... (cached) o checking whether the compiler supports GNU C... (cached) yes checking whether cc accepts -g... (cached) yes checking for cc option to enable C11 features... none needed checking whether the compiler supports GNU C++... (cached) yes checking whether c++ accepts -g... (cached) yes checking for c++ option to enable C++11 features... none needed checking for a BSD-compatible install... /usr/obj/ports/verilator-5.044/bin/install -c compiler version... c++ --version = eg++ (GCC) 15.2.0 checking that C++ compiler can compile simple program... yes checking for ar... ar checking for perl... (cached) /usr/bin/perl checking for python3... no configure: error: Cannot find "python3" in your PATH, please install it *** Error 1 in lang/verilator (/usr/ports/infrastructure/mk/bsd.port.mk:3024 'do-configure': @for d in /usr/obj/ports/verilator-5.044/verila...) *** Error 2 in lang/verilator (/usr/ports/infrastructure/mk/bsd.port.mk:3044 '/usr/obj/ports/verilator-5.044/.configure_done': @cd /usr/port...) *** Error 2 in lang/verilator (/usr/ports/infrastructure/mk/bsd.port.mk:2706 'configure': @lock=verilator-5.044; export _LOCKS_HELD=" veril...) ===> Exiting lang/verilator with an error *** Error 1 in /usr/ports (infrastructure/mk/bsd.port.subdir.mk:144 'configure': @: ${echo_msg:=echo}; : ${target:=configure}; for i in ; ...) >>> Ended at 1771634077.45 max_stuck=13.60/depends=15.75/show-prepare-results=11.86/patch=8.56/configure=20.86 Error: job failed with 512 on sparc64-0d at 1771634077