#58679 closed defect (fixed)
py37-tensorflow @1.14.0_2: Build error
Reported by: | mf2k (Frank Schima) | Owned by: | emcrisostomo (Enrico Maria Crisostomo) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | |
Keywords: | Cc: | cjones051073 (Chris Jones) | |
Port: | py-tensorflow |
Description (last modified by mf2k (Frank Schima))
I'm seeing the following error trying to build py37-tensorflow:
:info:build external/local_config_cc/cc_wrapper.sh -o bazel-out/host/bin/external/grpc/grpc_cpp_plugin bazel-out/host/bin/external/grpc/_objs/grpc_cpp_plugin/cpp_plugin.o bazel-out/host/bin/external/grpc/libgrpc_plugin_support.a bazel-out/host/bin/external/protobuf_archive/libprotoc_lib.a bazel-out/host/bin/external/protobuf_archive/libprotobuf.a bazel-out/host/bin/external/protobuf_archive/libprotobuf_lite.a bazel-out/host/bin/external/zlib_archive/libzlib.a -pthread -pthread -lpthread -lm -lpthread -lm -lpthread -lm -Wl,-S -undefined dynamic_lookup -headerpad_max_install_names -lstdc++ -lm '') :info:build ERROR: /opt/local/var/macports/build/_opt_local_var_macports_sources_github.com_macports_macports-ports_python_py-tensorflow/py37-tensorflow/work/60261d8adb0a7b542ce2e82cda02059b/external/grpc/BUILD:439:1: Linking of rule '@grpc//:grpc_cpp_plugin' failed (Exit 1) :info:build gcc: error: : No such file or directory
Attachments (1)
Change History (7)
Changed 5 years ago by mf2k (Frank Schima)
comment:1 Changed 5 years ago by mf2k (Frank Schima)
Description: | modified (diff) |
---|
comment:2 Changed 5 years ago by cjones051073 (Chris Jones)
comment:3 Changed 5 years ago by mf2k (Frank Schima)
$ port select gcc Available versions for gcc: mp-gcc8 (active) none
Yes I do. Of course a port should not be influenced by that. Thanks for the workaround.
comment:4 Changed 5 years ago by cjones051073 (Chris Jones)
Did it work then, with none selected ?
I totally agree ports should not be affected by a choice like this. bazel builds though, are really (REALLY) hard to control and stop stuff like this happening.
In fact, I have already been forced into putting a check into the bazel port itself to detect this and warn the user.
seems like, until someone can figure out how to control bazel to prevent this, I will have to do the same with tensorflow...
comment:5 Changed 5 years ago by Chris Jones <jonesc@…>
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
comment:6 Changed 5 years ago by mf2k (Frank Schima)
I finally checked on this. Yes, it works for me now.
Note: See
TracTickets for help on using
tickets.
Sorry, no idea. Don't have my 10.14 machine available at the moment (in for battery replacement) but the previous revision of 1.14.0 built fine.
http://packages.macports.org/py37-tensorflow/
One thought - Do you by chance have a gcc 'port selected' ? If so, please undo this (select none) and try again.