Zeek upgrade problem

ogogon · Oct 5, 2024

Colleagues, I'm trying to update Zeek using portupgrade. The update is interrupted with diagnostics, the meaning of which I do not understand.
Please tell me what my problem is.

sh:

[ 38% 659/1705] /usr/bin/c++ -DDOCTEST_CONFIG_SUPER_FAST_ASSERTS -I/usr/ports/security/zeek/work/zeek-7.0.3/auxil/spicy/3rdparty/reproc/reproc++/include -I/usr/ports/security/zeek/work/.build/auxil/spicy/include -I/usr/ports/security/zeek/work/zeek-7.0.3/auxil/spicy/hilti/toolchain/include -I/usr/ports/security/zeek/work/zeek-7.0.3/auxil/spicy/3rdparty -I/usr/ports/security/zeek/work/zeek-7.0.3/auxil/spicy/hilti/runtime/include -O2 -pipe -fstack-protector-strong -fno-strict-aliasing -Wall -Wno-unused -funsigned-char -Wno-register -Werror=vla -funsigned-char -O2 -pipe -fstack-protector-strong -fno-strict-aliasing   -DNDEBUG -std=c++17 -fPIC -Wall -Wno-missing-braces -Wno-vla -MD -MT auxil/spicy/hilti/toolchain/CMakeFiles/hilti-objects.dir/src/compiler/printer.cc.o -MF auxil/spicy/hilti/toolchain/CMakeFiles/hilti-objects.dir/src/compiler/printer.cc.o.d -o auxil/spicy/hilti/toolchain/CMakeFiles/hilti-objects.dir/src/compiler/printer.cc.o -c /usr/ports/security/zeek/work/zeek-7.0.3/auxil/spicy/hilti/toolchain/src/compiler/printer.cc
[ 38% 659/1705] /usr/bin/c++ -DDOCTEST_CONFIG_SUPER_FAST_ASSERTS -I/usr/ports/security/zeek/work/zeek-7.0.3/auxil/spicy/3rdparty/reproc/reproc++/include -I/usr/ports/security/zeek/work/.build/auxil/spicy/include -I/usr/ports/security/zeek/work/zeek-7.0.3/auxil/spicy/hilti/toolchain/include -I/usr/ports/security/zeek/work/zeek-7.0.3/auxil/spicy/3rdparty -I/usr/ports/security/zeek/work/zeek-7.0.3/auxil/spicy/hilti/runtime/include -O2 -pipe -fstack-protector-strong -fno-strict-aliasing -Wall -Wno-unused -funsigned-char -Wno-register -Werror=vla -funsigned-char -O2 -pipe -fstack-protector-strong -fno-strict-aliasing   -DNDEBUG -std=c++17 -fPIC -Wall -Wno-missing-braces -Wno-vla -MD -MT auxil/spicy/hilti/toolchain/CMakeFiles/hilti-objects.dir/src/compiler/resolver.cc.o -MF auxil/spicy/hilti/toolchain/CMakeFiles/hilti-objects.dir/src/compiler/resolver.cc.o.d -o auxil/spicy/hilti/toolchain/CMakeFiles/hilti-objects.dir/src/compiler/resolver.cc.o -c /usr/ports/security/zeek/work/zeek-7.0.3/auxil/spicy/hilti/toolchain/src/compiler/resolver.cc
ninja: build stopped: subcommand failed.
===> Compilation failed unexpectedly.
Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to
the maintainer.
*** Error code 1

Stop.
make[1]: stopped in /usr/ports/security/zeek
*** Error code 1

Stop.
make: stopped in /usr/ports/security/zeek
egrep: empty (sub)expression
** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade20241005-2223-8mngzz env UPGRADE_TOOL=portupgrade UPGRADE_PORT=zeek-6.0.4_1 UPGRADE_PORT_VER=6.0.4_1 make
** Fix the problem and try again.
** Listing the failed packages (-:ignored / *:skipped / !:failed)
    ! security/zeek (zeek-6.0.4_1)    (unknown build error)

Thank you in advance,
Ogogon.

cracauer@ · Oct 5, 2024

You didn't copy the actual error message.

ogogon · Oct 6, 2024

cracauer@ said:
You didn't copy the actual error message.

Unfortunately, there were no other messages on the console. Where and how to get them?

tingo · Oct 6, 2024

Often there are build logs in the work directory. If not, you could start over ( make clean) and run the whole make session in script(1).

ogogon · Oct 6, 2024

tingo said:
Often there are build logs in the work directory. If not, you could start over ( make clean) and run the whole make session in script(1).

cracauer@ · Oct 6, 2024

Code:

In file included from /usr/ports/security/zeek/work/zeek-7.0.3/auxil/spicy/hilti/toolchain/src/compiler/plugin.cc:5:^M
/usr/ports/security/zeek/work/zeek-7.0.3/auxil/spicy/hilti/toolchain/include/hilti/compiler/coercer.h:163:23: error: unknown type name 'QualifiedType'^M
  163 |     CoercedExpression(QualifiedType* src, Expression* coerced)^M
      |                       ^^M
/usr/ports/security/zeek/work/zeek-7.0.3/auxil/spicy/hilti/toolchain/include/hilti/compiler/coercer.h:166:76: error: member reference type 'const hilti::Type' is not a pointer; did you mean to use '.'?^M
  166 |           consider_type_changed(src->type()->typeClass() != coerced->type()->type()->typeClass()) {}^M
      |                                                             ~~~~~~~~~~~~~~~^~^M
      |                                                                            .^M
/usr/ports/security/zeek/work/zeek-7.0.3/auxil/spicy/hilti/toolchain/include/hilti/compiler/coercer.h:166:78: error: no member named 'type' in 'hilti::Type'^M
  166 |           consider_type_changed(src->type()->typeClass() != coerced->type()->type()->typeClass()) {}^M
      |                                                             ~~~~~~~~~~~~~~~  ^^M
/usr/ports/security/zeek/work/zeek-7.0.3/auxil/spicy/hilti/toolchain/include/hilti/compiler/coercer.h:197:36: error: unknown type name 'Builder'^M
  197 | CoercedExpression coerceExpression(Builder* builder, Expression* e, QualifiedType* dst,^M
      |                                    ^^M
/usr/ports/security/zeek/work/zeek-7.0.3/auxil/spicy/hilti/toolchain/include/hilti/compiler/coercer.h:197:69: error: unknown type name 'QualifiedType'^M
  197 | CoercedExpression coerceExpression(Builder* builder, Expression* e, QualifiedType* dst,^M

ogogon · Oct 6, 2024

cracauer@ said:

Code:

In file included from /usr/ports/security/zeek/work/zeek-7.0.3/auxil/spicy/hilti/toolchain/src/compiler/plugin.cc:5:^M
/usr/ports/security/zeek/work/zeek-7.0.3/auxil/spicy/hilti/toolchain/include/hilti/compiler/coercer.h:163:23: error: unknown type name 'QualifiedType'^M
  163 |     CoercedExpression(QualifiedType* src, Expression* coerced)^M
      |                       ^^M
/usr/ports/security/zeek/work/zeek-7.0.3/auxil/spicy/hilti/toolchain/include/hilti/compiler/coercer.h:166:76: error: member reference type 'const hilti::Type' is not a pointer; did you mean to use '.'?^M
  166 |           consider_type_changed(src->type()->typeClass() != coerced->type()->type()->typeClass()) {}^M
      |                                                             ~~~~~~~~~~~~~~~^~^M
      |                                                                            .^M
/usr/ports/security/zeek/work/zeek-7.0.3/auxil/spicy/hilti/toolchain/include/hilti/compiler/coercer.h:166:78: error: no member named 'type' in 'hilti::Type'^M
  166 |           consider_type_changed(src->type()->typeClass() != coerced->type()->type()->typeClass()) {}^M
      |                                                             ~~~~~~~~~~~~~~~  ^^M
/usr/ports/security/zeek/work/zeek-7.0.3/auxil/spicy/hilti/toolchain/include/hilti/compiler/coercer.h:197:36: error: unknown type name 'Builder'^M
  197 | CoercedExpression coerceExpression(Builder* builder, Expression* e, QualifiedType* dst,^M
      |                                    ^^M
/usr/ports/security/zeek/work/zeek-7.0.3/auxil/spicy/hilti/toolchain/include/hilti/compiler/coercer.h:197:69: error: unknown type name 'QualifiedType'^M
  197 | CoercedExpression coerceExpression(Builder* builder, Expression* e, QualifiedType* dst,^M

Why does this error occur and how can I fix it?
An earlier version of Zeek compiled for me without problems.

cracauer@ · Oct 6, 2024

I haven't the foggiest

Some library or other dependency out of sync?

jbo@ · Oct 6, 2024

Just for reference: security/zeek 7.0.3 built just fine out-of-the-box here (stable/14 amd64 machine).

leres · Oct 6, 2024

You said offline that you're building on 13.4-p1; I am able to build zeek 7.0.3 in a 13.4-p1 poudriere jail. My guess would be that you've got some package installed that is installed and being used by the build in place of a port dependency.

ogogon · Oct 7, 2024

leres said:
You said offline that you're building on 13.4-p1; I am able to build zeek 7.0.3 in a 13.4-p1 poudriere jail. My guess would be that you've got some package installed that is installed and being used by the build in place of a port dependency.

Strange, very strange! On another machine, with the same operating system, the same history of binary version updates and the same version of the compiler, zeek compiled successfully. I don't even know what to assume...
When will there be a binary package for zeek 7.0.3?

leres · Oct 7, 2024

ogogon said:
Strange, very strange! On another machine, with the same operating system, the same history of binary version updates and the same version of the compiler, zeek compiled successfully. I don't even know what to assume...
When will there be a binary package for zeek 7.0.3?

You could build a package on the system that compiles and install it on the other system.

I don't know about the quarterly package builds, I would have expected a 2024Q4 branch to be created before October 7th...

leres · Oct 7, 2024

I just remembered, another thing you can try is to reinstall all packages:

pkg clean -ay ; pkg upgrade -yf ; pkg clean -ay

Zeek upgrade problem

Attachments