[MacPorts] #64442: bazel build points to builder directory _opt_bblocal_var_buildworker_ports_build_ports_devel_bazel

[MacPorts]

#64442: bazel build points to builder directory
_opt_bblocal_var_buildworker_ports_build_ports_devel_bazel
-----------------------+-------------------------------------------
 Reporter:  essandess  |      Owner:  (none)
     Type:  defect     |     Status:  new
 Priority:  Normal     |  Milestone:
Component:  ports      |    Version:  2.7.1
 Keywords:             |       Port:  bazel, py-tensorflow-metadata
-----------------------+-------------------------------------------
 I’m trying to build/update {{{py-tensforflow-metadata}}} and am hitting
 this (bizarre) bazel issue.

 First, the build fails with the error:

 {{{
 :info:build Execution platform: @local_config_platform//:host
 :info:build Use --sandbox_debug to see verbose messages from the sandbox
 :info:build xcrun: error: can't exec
 '/opt/local/var/macports/build/_opt_bblocal_var_buildworker_ports_build_ports_devel_bazel/bazel-3.7/work/bazelwrap/cc'
 (errno=No such file or directory)
 }}}

 Weird that bazel wants to look in a MacPorts build directory.

 Searching for this string in {{{${worksrcpath}}}}, it appears in the file
 created during the build stage:

 {{{
 ${worksrcpath}/bazel_build/install/<hash>/embedded_tools/tools/osx/crosstool/wrapped_clang.cc:
 }}}

 {{{
   if (binary_name == "wrapped_clang_pp") {
     tool_name =
 "/opt/local/var/macports/build/_opt_bblocal_var_buildworker_ports_build_ports_devel_bazel/bazel-3.7/work/bazelwrap/cxx";
   } else if (binary_name == "wrapped_clang") {
     tool_name =
 "/opt/local/var/macports/build/_opt_bblocal_var_buildworker_ports_build_ports_devel_bazel/bazel-3.7/work/bazelwrap/cc";
 }}}

 This is not the file from
 https://github.com/bazelbuild/bazel/blob/master/tools/osx/crosstool/wrapped_clang.cc

 To be clear, I am not building {{{bazel-3.7}}} here. I am building {{{py38
 -tensorflow-metadata}}}, which uses {{{bazel-3.7}}}. I’ve attached the log
 file. It was produced with a build (please see attached Portfile) that
 adds {{{bazel.build_opts-append --sandbox_debug}}}, not that I see that
 helping a diagnosis.

 FWIW, I looked in the binary {{{/opt/local/libexec/bazel-3.7/bin/bazel}}}
 for the string
 {{{_opt_bblocal_var_buildworker_ports_build_ports_devel_bazel}}} but it’s
 not there, at least not in plain text. I have no idea how this path is
 being introduced at the build stage.

-- 
Ticket URL: <https://trac.macports.org/ticket/64442>
MacPorts <https://www.macports.org/>
Ports system for macOS