protobuf dependency will it build?

Finally we have found a package that will not build on joborun, is this good or bad?
When you construct a system you make certain choices, parameters if you like, or call it policy of the distribution of you will, and in joborun we build in a systemd/libsystemd/libelogind FREE environment, with as little as possible of zstd presence, dbus presence but not running, and ipv6 turned as much as "possible"

Since protobuf is not an uncommon dependency we thought of giving it a try instead of using the one from arch, which tends to break anything built with a previous edition. After 45' of building we run on this error and attempted to investigate what causes it and how it can be bypassed.
This is all #google stuff that has become common for many developers to use with little critical eye on trust on this corporation.

make[1]: Leaving directory '/src/pkg/extra2do/protobuf/src/build'
/usr/bin/cmake -E cmake_progress_start /src/pkg/extra2do/protobuf/src/build/CMakeFiles 0

Starting local Bazel server and connecting to it...
FATAL: Cannot get start time of process 32154: (error: 2): No such file or directory

https://stackoverflow.com/questions/50931045/cannot-connect-to-bazel-server

bazel server listens on IPv6 address of loopback interface. If you have 
firewall rules to drop IPv6 packets, you need to allow bazel traffic.

It seems it can't and you wouldn't know on any other system we know where ipv6 connectivity is by default on and functional. It takes a joborun to find this out.

So bottom line is we are happy to not be able to build this one ;)

If you were using arch, artix, obarun, you wouldn't know, would you?

#joborun