Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 19 Mar 2022 16:40:41 +0000
From:      bugzilla-noreply@freebsd.org
To:        ports-bugs@FreeBSD.org
Subject:   [Bug 262216] devel/bazel 5.0.0 does not work after successful installation on freebsd 13.0
Message-ID:  <bug-262216-7788-iTzPqPDfec@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-262216-7788@https.bugs.freebsd.org/bugzilla/>
References:  <bug-262216-7788@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D262216

--- Comment #19 from Klaus Aehlig <aehlig@linta.de> ---
(In reply to Ulas SAYGIN from comment #18)

I get the error quoted below. One of the interesting things is the
--tool_java_runtime_version=3Dremotejdk_11 picked up from envoy's .bazelrc;=
 that
jdk is a problem anyway, as the remotejdk is defined by dispatching over the
supported operating systems (not including bazel). But that doesn't seem to=
 be
the only reference that prevents building against the locally installed jdk.


/memfs/tmp/envoy>bazel build --announce_rc -c opt envoy=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
(17:26:52) INFO: Reading 'startup' options from /memfs/tmp/envoy/.bazelrc:
--host_jvm_args=3D-Xmx2g
(17:26:52) INFO: Options provided by the client:
  Inherited 'common' options: --isatty=3D1 --terminal_columns=3D169
(17:26:52) INFO: Reading rc options for 'build' from /memfs/tmp/envoy/.baze=
lrc:
  Inherited 'common' options: --experimental_allow_tags_propagation
(17:26:52) INFO: Reading rc options for 'build' from
/crypto/general/aehlig/conf/.bazelrc:
  Inherited 'common' options: --experimental_ui_actions_shown 12
(17:26:52) INFO: Reading rc options for 'build' from
/usr/local/etc/bazel/bazel.bazelrc:
  'build' options: --strategy=3DJavac=3Dstandalone --java_runtime_version=
=3D11
--tool_java_runtime_version=3D11 --action_env=3DPATH=3D/bin:/usr/bin/:/usr/=
local/bin
(17:26:52) INFO: Reading rc options for 'build' from /memfs/tmp/envoy/.baze=
lrc:
  'build' options: --color=3Dyes --workspace_status_command=3Dbash
bazel/get_workspace_status --incompatible_strict_action_env
--host_force_python=3DPY3 --java_runtime_version=3Dremotejdk_11
--tool_java_runtime_version=3Dremotejdk_11 --enable_platform_specific_config
--define absl=3D1 --action_env=3DCC --action_env=3DCXX --action_env=3DLLVM_=
CONFIG
--action_env=3DPATH --test_env=3DHEAPCHECK=3Dnormal --test_env=3DPPROF_PATH
(17:26:52) INFO: Reading rc options for 'build' from
/crypto/general/aehlig/conf/.bazelrc:
  'build' options: --symlink_prefix=3D/ --show_progress_rate_limit=3D0.2
--show_timestamps --distdir=3D/home/aehlig/.cache/distdir
(17:26:52) INFO: Current date is 2022-03-19
(17:26:52) INFO: Build options --compilation_mode, --host_javabase,
--java_runtime_version, and 1 more have changed, discarding analysis cache.
(17:26:52) ERROR:
/crypto/general/aehlig/.cache/bazel/_bazel_aehlig/f8d4628c4218c908b0cf33cb4=
d5f53b8/external/bazel_tools/tools/jdk/BUILD:29:19:
While resolving toolchains for target
@bazel_tools//tools/jdk:current_java_runtime: no matching toolchains found =
for
types @bazel_tools//tools/jdk:runtime_toolchain_type
(17:26:52) ERROR: Analysis of target '//:envoy' failed; build aborted:=20
(17:26:52) INFO: Elapsed time: 0.328s
(17:26:52) INFO: 0 processes.
(17:26:52) FAILED: Build did NOT complete successfully (0 packages loaded, =
8547
targets configured)
    Fetching @boringssl; fetching
/memfs/tmp/envoy>

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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-262216-7788-iTzPqPDfec>