[MacPorts] #58569: bazel @0.26.1 build failure: unrecognized command line option '-fobjc-link-runtime'

[MacPorts]

#58569: bazel @0.26.1 build failure: unrecognized command line option '-fobjc-link-
runtime'
---------------------+--------------------------
  Reporter:  dbl001  |      Owner:  cjones051073
      Type:  defect  |     Status:  assigned
  Priority:  Normal  |  Milestone:
 Component:  ports   |    Version:  2.5.4
Resolution:          |   Keywords:
      Port:  bazel   |
---------------------+--------------------------

Comment (by cjones051073):

 One other thing. Please run the build again, let it fail, then from the
 port work area ('port work bazel') dig out the file
 external/local_config_cc/cc_wrapper.sh and post it here. That script is
 auto-generated, so I need to see what *you* have in it... its seemingly
 this script that is trying to run gcc

 {{{
 :info:build   external/local_config_cc/cc_wrapper.sh -lc++ -fobjc-link-
 runtime -Wl,-S -o bazel-out/host/bin/third_party/protobuf/3.6.1/protoc
 bazel-out/host/bin/third_party/protobuf/3.6.1/_objs/protoc/main.o bazel-
 out/host/bin/third_party/protobuf/3.6.1/libprotoc_lib.a bazel-
 out/host/bin/third_party/protobuf/3.6.1/libprotobuf.a bazel-
 out/host/bin/third_party/protobuf/3.6.1/libprotobuf_lite.a
 -headerpad_max_install_names -lpthread -lm -lpthread -lm -lpthread -lm
 -lpthread -lm -no-canonical-prefixes '-mmacosx-version-min=10.12')
 }}

 which fails with

 error: unrecognized command line option '-fobjc-link-runtime'

 as that is a clang-only option...

 I also need to see what `which gcc` gives for you, as I suspicion is you
 might have `port selected` a gcc version, which means for you this is a
 real gcc compiler, rather than the clang wrapper the system provides.

-- 
Ticket URL: <https://trac.macports.org/ticket/58569#comment:5>
MacPorts <https://www.macports.org/>
Ports system for macOS