[Bug 262216] devel/bazel 5.0.0 does not work after successful installation on freebsd 13.0

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262216

            Bug ID: 262216
           Summary: devel/bazel 5.0.0 does not work after successful
                    installation on freebsd 13.0
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: Individual Port(s)
          Assignee: ports-bugs@FreeBSD.org
          Reporter: ulassayginim@gmail.com
                CC: aehlig@linta.de
             Flags: maintainer-feedback?(aehlig@linta.de)
                CC: aehlig@linta.de

Hi ,

i installed bazel 5.0.0 version with out problem by compiling from Freebsd port
tree.

when i test to bazel , i used envoy project and bazel example projects to test
it is function.

it failed and gived errors.

firstly, it didnt find python3 and pip3 tool which belongs to python 3.10
and i created symlink as pyhon3 to python 3.10 and then installed pip,
then started to working but now it gives error about jdk11 but jdk is perfectly
working conditions. i cant find the reason why it is not working.
are there someone who can test this? is it only related to me or port?
i also created issue on bazel github account but noone answered.

https://github.com/bazelbuild/bazel/issues/14891

you can see details about errors both for failing build attempt to envoy and
example c++ projects of bazel.

errors like


for envoyproxy from https://github.com/envoyproxy/envoy
    root@fbsd_bazel:~/envoy # bazel build //:envoy --sandbox_debug
--host_javabase=@local_jdk//:jdk
    WARNING: Option 'host_javabase' is deprecated
    INFO: Build option --host_javabase has changed, discarding analysis cache.
    ERROR:
/root/.cache/bazel/_bazel_root/4e47b77d977b209382cf04b3ae32963e/external/bazel_tools/tools/jdk/BUILD:432:8:
In rule 'proguard_whitelister_test', size 'medium' is not a valid size.
    ERROR:
/root/.cache/bazel/_bazel_root/4e47b77d977b209382cf04b3ae32963e/external/bazel_tools/tools/jdk/BUILD:432:8:
In rule 'proguard_whitelister_test', timeout 'illegal' is not a valid timeout.
    ERROR: Analysis of target '//:envoy' failed; build aborted: error loading
package '@bazel_tools//tools/jdk': Package 'tools/jdk' contains errors
    INFO: Elapsed time: 0,372s
    INFO: 0 processes.
    FAILED: Build did NOT complete successfully (1 packages loaded, 6 targets
configured)

https://docs.bazel.build/versions/main/tutorial/cpp.html

    examples/cpp-tutorial/stage1 # bazel build //main:hello-world
    WARNING: Running Bazel server needs to be killed, because the startup
options are different.
    Starting local Bazel server and connecting to it...
    ... still trying to connect to local Bazel server after 10 seconds ...
    ... still trying to connect to local Bazel server after 20 seconds ...
    ... still trying to connect to local Bazel server after 30 seconds ...
    ... still trying to connect to local Bazel server after 40 seconds ...
    ERROR:
/root/.cache/bazel/_bazel_root/033bfece9530ea7f1b2e1c399eea4938/external/bazel_tools/tools/jdk/BUILD:432:8:
In rule 'proguard_whitelister_test', size 'medium' is not a valid size.
    ERROR:
/root/.cache/bazel/_bazel_root/033bfece9530ea7f1b2e1c399eea4938/external/bazel_tools/tools/jdk/BUILD:432:8:
In rule 'proguard_whitelister_test', timeout 'illegal' is not a valid timeout.
    ERROR: Analysis of target '//main:hello-world' failed; build aborted: error
loading package '@bazel_tools//tools/jdk': Package 'tools/jdk' contains errors
    INFO: Elapsed time: 50,453s
    INFO: 0 processes.

-- 
You are receiving this mail because:
You are the assignee for the bug.