OS X: tests failing with "unrecognized command line option"

I’m running OS X, El Capitan (10.11.5) with MacPorts. Installed Tensorflow a couple months ago.

Tonight I installed bazel via the binary installer. Then ran…

bash-3.2$ bazel test //magenta:all
WARNING: /private/var/tmp/_bazel_myusername/ddd9d9dc1e025ace939596b3e248324a/external/protobuf/WORKSPACE:1: Workspace name in /private/var/tmp/_bazel_myusername/ddd9d9dc1e025ace939596b3e248324a/external/protobuf/WORKSPACE (@__main__) does not match the name given in the repository's definition (@protobuf); this will cause a build error in future versions.
INFO: Found 9 targets and 6 test targets...
ERROR: /private/var/tmp/_bazel_myusername/ddd9d9dc1e025ace939596b3e248324a/external/protobuf/BUILD:228:1: C++ compilation of rule '@protobuf//:protoc_lib' failed: cc_wrapper.sh failed: error executing command external/local_config_cc/cc_wrapper.sh -U_FORTIFY_SOURCE '-D_FORTIFY_SOURCE=1' -fstack-protector -Wall -Wthread-safety -Wself-assign -Wno-free-nonheap-object -fno-omit-frame-pointer -g0 -O2 -DNDEBUG ... (remaining 36 argument(s) skipped): com.google.devtools.build.lib.shell.BadExitStatusException: Process exited with status 1.
cc1plus: error: unrecognized command line option "-Wthread-safety"
cc1plus: error: unrecognized command line option "-Wself-assign"
cc1plus: warning: unrecognized command line option "-Wno-free-nonheap-object"
INFO: Elapsed time: 4.480s, Critical Path: 1.87s
//magenta:basic_one_hot_encoder_test                                  NO STATUS
//magenta:convert_midi_dir_to_note_sequences_test                     NO STATUS
//magenta:melodies_lib_test                                           NO STATUS
//magenta:midi_io_test                                                NO STATUS
//magenta:note_sequence_io_test                                       NO STATUS
//magenta:sequence_to_melodies_test                                   NO STATUS

Executed 0 out of 6 tests: 6 were skipped.
bash-3.2$ 

Any suggestions? Perhaps it’s some kind of compiler mismatch? Usually, build scripts will pull from the environment to use the MacPorts compilers, but the default ‘gcc’ just points to Apple’s…

bash-3.2$ which gcc
/Applications/XCode.app/Contents/Developer/usr/bin/gcc
bash-3.2$ set | grep CC
CC=/opt/local/bin/gcc-mp-4.4
bash-3.2$ set | grep CXX
CXX=/opt/local/bin/g++-mp-4.4

Thanks.

[drscotthawley]

% python --version Python 2.7.11

[drscotthawley]

Sorry, my laptop died recently and I’m just getting going again on a new one. Did not get it solved, with MacPorts, however with the new laptop I’m trying HomeBrew instead, and got the tests to pass.