+ case "${usergroup_phase}" in
+ local run_cmd
+ run_cmd=run_su
+ shift
+ run_su /opt/pkg/bin/bmake configure BATCH=1 DEPENDS_TARGET=/nonexistent WRKLOG=/tmp/bulklog/premake5-5.0.0.b6/work.log
+ su pbulk -c '"$@"' make /opt/pkg/bin/bmake configure BATCH=1 DEPENDS_TARGET=/nonexistent WRKLOG=/tmp/bulklog/premake5-5.0.0.b6/work.log
=> Checksum BLAKE2s OK for premake-5.0.0-beta6-src.zip
=> Checksum SHA512 OK for premake-5.0.0-beta6-src.zip
===> Installing dependencies for premake5-5.0.0.b6
==========================================================================
The following variables will affect the build process of this package,
premake5-5.0.0.b6. Their current value is shown below:
* CURSES_DEFAULT = ncurses
* READLINE_DEFAULT = readline
* SSLBASE (defined)
* SSLCERTBUNDLE (not defined)
* SSLCERTS = /etc/opt/pkg/openssl/certs
* SSLDIR = /etc/opt/pkg/openssl
* SSLKEYS = /etc/opt/pkg/openssl/private
Based on these variables, the following variables have been set:
* CURSES_TYPE = ncurses
* READLINE_TYPE = readline
* TERMCAP_TYPE = curses
You may want to abort the process now with CTRL-C and change the value
of variables in the first group before continuing. Be sure to run
`/opt/pkg/bin/bmake clean' after the changes.
==========================================================================
=> Tool dependency gmake>=3.81: found gmake-4.4.1
=> Tool dependency unzip-[0-9]*: found unzip-6.0nb10
=> Tool dependency cwrappers>=20150314: found cwrappers-20220403
=> Tool dependency checkperms>=1.1: found checkperms-1.12
=> Full dependency lua53-socket-[0-9]*: found lua53-socket-3.0rc1nb5
=> Full dependency curl>=8.13.0nb2: found curl-8.13.0nb2
=> Full dependency libzip>=1.11.3nb1: found libzip-1.11.4
=> Full dependency lua53>=5.3.0<5.4: found lua53-5.3.6
=> Full dependency mbedtls3>=3.4.0nb1: found mbedtls3-3.6.3
=> Full dependency zlib>=1.2.3: found zlib-1.3.1
=> Full dependency bzip2>=1.0.1: found bzip2-1.0.8
=> Full dependency gettext-lib>=0.22: found gettext-lib-0.22.5
=> Full dependency libiconv>=1.9.1: found libiconv-1.17
=> Full dependency libidn2>=2.0.0: found libidn2-2.3.7
=> Full dependency libunistring>=0.9.3: found libunistring-1.2
=> Full dependency libxml2>=2.6.2: found libxml2-2.14.2nb2
=> Full dependency ncurses>=5.3nb1: found ncurses-6.5
=> Full dependency nghttp2>=1.0.0: found nghttp2-1.65.0nb1
=> Full dependency openssl>=1.1.1: found openssl-3.4.1
=> Full dependency readline>=2.2: found readline-8.2nb2
=> Full dependency xz>=5.0.0: found xz-5.8.1
===> Overriding tools for premake5-5.0.0.b6
===> Extracting for premake5-5.0.0.b6
===> Patching for premake5-5.0.0.b6
=> Applying pkgsrc patches for premake5-5.0.0.b6
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/devel/premake5/patches/patch-modules_gmake_tests_test__gmake__ldflags.lua
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/devel/premake5/patches/patch-modules_gmake_tests_test__gmake__ldflags.lua
Hmm... Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-modules_gmake_tests_test__gmake__ldflags.lua,v 1.1 2025/05/13 14:21:57 triaxx Exp $
|
|Remove the hardcoded -L/usr/lib and -L/usr/lib64
|This is not needed, and will cause issues:
|https://github.com/gentoo/gentoo/pull/25825#issuecomment-1179497476
|
|--- modules/gmake/tests/test_gmake_ldflags.lua.orig 2022-09-03 20:03:02.000000000 +0000
|+++ modules/gmake/tests/test_gmake_ldflags.lua
--------------------------
Patching file modules/gmake/tests/test_gmake_ldflags.lua using Plan A...
Hunk #1 succeeded at 56.
Hunk #2 succeeded at 65.
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/devel/premake5/patches/patch-modules_gmakelegacy_tests_cpp_test__ldflags.lua
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/devel/premake5/patches/patch-modules_gmakelegacy_tests_cpp_test__ldflags.lua
Hmm... Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-modules_gmakelegacy_tests_cpp_test__ldflags.lua,v 1.1 2025/05/13 14:21:57 triaxx Exp $
|
|Remove the hardcoded -L/usr/lib and -L/usr/lib64
|This is not needed, and will cause issues:
|https://github.com/gentoo/gentoo/pull/25825#issuecomment-1179497476
|
|--- modules/gmakelegacy/tests/cpp/test_ldflags.lua.orig 2022-09-03 20:03:02.000000000 +0000
|+++ modules/gmakelegacy/tests/cpp/test_ldflags.lua
--------------------------
Patching file modules/gmakelegacy/tests/cpp/test_ldflags.lua using Plan A...
Hunk #1 succeeded at 55.
Hunk #2 succeeded at 64.
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/devel/premake5/patches/patch-src_host_premake.h
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/devel/premake5/patches/patch-src_host_premake.h
Hmm... Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-src_host_premake.h,v 1.1 2025/05/13 14:21:57 triaxx Exp $
|
|Fix header paths to be consistent with include directories provided by pkgsrc.
|
|--- src/host/premake.h.orig 2025-05-13 13:51:10.681237075 +0000
|+++ src/host/premake.h
--------------------------
Patching file src/host/premake.h using Plan A...
Hunk #1 succeeded at 10.
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/devel/premake5/patches/patch-src_tools_gcc.lua
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/devel/premake5/patches/patch-src_tools_gcc.lua
Hmm... Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-src_tools_gcc.lua,v 1.1 2025/05/13 14:21:57 triaxx Exp $
|
|Remove the hardcoded -L/usr/lib and -L/usr/lib64
|This is not needed, and will cause issues:
|https://github.com/gentoo/gentoo/pull/25825#issuecomment-1179497476
|
|--- src/tools/gcc.lua.orig 2022-09-03 20:03:02.000000000 +0000
|+++ src/tools/gcc.lua
--------------------------
Patching file src/tools/gcc.lua using Plan A...
Hunk #1 succeeded at 536.
done
===> Creating toolchain wrappers for premake5-5.0.0.b6
===> Configuring for premake5-5.0.0.b6
=> Checking for portability problems in extracted files
ERROR: [check-portability] => Found test ... == ...:
ERROR: [check-portability] binmodules/luasocket/gem/myps2pdf:42: if [ $best == 1 ]
Explanation:
===========================================================================
The "test" command, as well as the "[" command, are not required to know
the "==" operator. Only a few implementations like bash and some
versions of ksh support it.
When you run "test foo == foo" on a platform that does not support the
"==" operator, the result will be "false" instead of "true". This can
lead to unexpected behavior.
There are two ways to fix this error message. If the file that contains
the "test ==" is needed for building the package, you should create a
patch for it, replacing the "==" operator with "=". If the file is not
needed, add its name to the CHECK_PORTABILITY_SKIP variable in the
package Makefile.
===========================================================================
ERROR: [check-portability] => Found test ... == ...:
ERROR: [check-portability] binmodules/luasocket/gem/myps2pdf:76: if [ $rot == 1 ]
Explanation:
===========================================================================
The "test" command, as well as the "[" command, are not required to know
the "==" operator. Only a few implementations like bash and some
versions of ksh support it.
When you run "test foo == foo" on a platform that does not support the
"==" operator, the result will be "false" instead of "true". This can
lead to unexpected behavior.
There are two ways to fix this error message. If the file that contains
the "test ==" is needed for building the package, you should create a
patch for it, replacing the "==" operator with "=". If the file is not
needed, add its name to the CHECK_PORTABILITY_SKIP variable in the
package Makefile.
===========================================================================
ERROR: [check-portability] => Found test ... == ...:
ERROR: [check-portability] binmodules/luasocket/gem/myps2pdf:81: if [ $eps == 1 ]
Explanation:
===========================================================================
The "test" command, as well as the "[" command, are not required to know
the "==" operator. Only a few implementations like bash and some
versions of ksh support it.
When you run "test foo == foo" on a platform that does not support the
"==" operator, the result will be "false" instead of "true". This can
lead to unexpected behavior.
There are two ways to fix this error message. If the file that contains
the "test ==" is needed for building the package, you should create a
patch for it, replacing the "==" operator with "=". If the file is not
needed, add its name to the CHECK_PORTABILITY_SKIP variable in the
package Makefile.
===========================================================================
ERROR: [check-portability] => Found test ... == ...:
ERROR: [check-portability] binmodules/luasocket/gem/myps2pdf:88: if [ $a4 == 1 ]
Explanation:
===========================================================================
The "test" command, as well as the "[" command, are not required to know
the "==" operator. Only a few implementations like bash and some
versions of ksh support it.
When you run "test foo == foo" on a platform that does not support the
"==" operator, the result will be "false" instead of "true". This can
lead to unexpected behavior.
There are two ways to fix this error message. If the file that contains
the "test ==" is needed for building the package, you should create a
patch for it, replacing the "==" operator with "=". If the file is not
needed, add its name to the CHECK_PORTABILITY_SKIP variable in the
package Makefile.
===========================================================================
ERROR: [check-portability] => Found test ... == ...:
ERROR: [check-portability] binmodules/luasocket/gem/myps2pdf:107: if [ $do_opt == 1 ]
Explanation:
===========================================================================
The "test" command, as well as the "[" command, are not required to know
the "==" operator. Only a few implementations like bash and some
versions of ksh support it.
When you run "test foo == foo" on a platform that does not support the
"==" operator, the result will be "false" instead of "true". This can
lead to unexpected behavior.
There are two ways to fix this error message. If the file that contains
the "test ==" is needed for building the package, you should create a
patch for it, replacing the "==" operator with "=". If the file is not
needed, add its name to the CHECK_PORTABILITY_SKIP variable in the
package Makefile.
===========================================================================
*** Error code 1
Stop.
bmake[1]: stopped making "configure" in /data/jenkins/workspace/pkgsrc-upstream-trunk/devel/premake5
*** Error code 1
Stop.
bmake: stopped making "configure" in /data/jenkins/workspace/pkgsrc-upstream-trunk/devel/premake5