Closed liangfok closed 5 years ago
@david-german-tri please feel free to close if we're not planning on supporting Bazel + OSX.
Yes, we are supporting Bazel + OSX. Fixing warnings is not super high on the list though; making it support all Drake features comes first.
OK. There are a couple other types of warnings that flood my terminal when I build using Bazel on OSX. Here are samples:
ld: warning: could not create compact unwind for ___dmumps_parallel_analysis_MOD_dmumps_715: stack subq instruction is too different from dwarf stack size
ld: warning: could not create compact unwind for _write_float: stack subq instruction is too different from dwarf stack size
And:
INFO: From Linking drake/common/libcond.a:
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/libtool: file: bazel-out/osx-opt/bin/drake/common/_objs/cond/drake/common/cond.o has no symbols
warning: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/libtool: warning for library: bazel-out/osx-opt/bin/drake/common/libcond.a the table of contents is empty (no object file members in the library define global symbols)
The final item is a dup of #5145.
Is there a plan for adding OSX + Bazel to either Continuous Production or Nightly Production?
Or is it already there and I simply missed it? (I was trying to verify that the same warnings show up in CI).
Other than being opt-in for PRs (aka experimental
), it's only in https://drake-jenkins.csail.mit.edu/view/Bazel/job/mac-clang-bazel-nightly-release/ per https://drake-jenkins.csail.mit.edu/view/Bazel/. Yes, we are working on making it be production-supported in Continuous.
Thanks. I just confirmed that all aforementioned warnings show up in CI, which is good.
INFO: From Linking drake/automotive/liblane_direction.a:
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/libtool: file: bazel-out/osx-opt/bin/drake/automotive/_objs/lane_direction/drake/automotive/lane_direction.o has no symbols
warning: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/libtool: warning for library: bazel-out/osx-opt/bin/drake/automotive/liblane_direction.a the table of contents is empty (no object file members in the library define global symbols)
Reassigning to @soonho-tri.
Just noticed:
DEBUG: pkg_config.bzl:186:9: pkg-config of protobuf returned flags that we will ignore: ["-Qunused-arguments"]
Hence, targets that use protobuf
have the following:
clang: warning: argument unused during compilation: '-pthread'
Since I missed that for weeks, I would advocate having the DEBUG
message from pkg-config.bzl
having the text WARNING
in it so that CDash highlights and having a way to declare flags (such as -Qthread
) that we know we should ignore so that the warning can be suppressed.
Also, having a platform dependent way declare flags that should be ignored could strip out the bad -pthread
on Mac.
Per f2f, still waiting for bazelbuild
s upstream update. Any other warnings can be filtered out via CDash.
Per f2f, closing this generic issue as we have the xref'd specific issues that provide better insight.
For the record, also related is bazelbuild/bazel#5981, but I do not think it deserves a Drake issue or this issue being reopened.
Sample Output