Open iame6162013 opened 7 years ago
Another error
+ bazel build --verbose_failures @grpc//:grpc_cpp_plugin
INFO: Found 1 target...
ERROR: /home/iame/.cache/bazel/_bazel_iame/88f8289dc53da1a7a11159bcedf3496d/external/protobuf/BUILD:113:1: undeclared inclusion(s) in rule '@protobuf//:protobuf':
this rule is missing dependency declarations for the following files included by 'external/protobuf/src/google/protobuf/io/strtod.cc':
'/usr/lib/gcc/x86_64-pc-linux-gnu/7.1.1/include/stddef.h'
'/usr/lib/gcc/x86_64-pc-linux-gnu/7.1.1/include/stdarg.h'
'/usr/lib/gcc/x86_64-pc-linux-gnu/7.1.1/include/stdint.h'
'/usr/lib/gcc/x86_64-pc-linux-gnu/7.1.1/include-fixed/limits.h'
'/usr/lib/gcc/x86_64-pc-linux-gnu/7.1.1/include-fixed/syslimits.h'.
In file included from /usr/lib/gcc/x86_64-pc-linux-gnu/7.1.1/../../../../include/c++/7.1.1/x86_64-pc-linux-gnu/bits/os_defines.h:39:0,
from /usr/lib/gcc/x86_64-pc-linux-gnu/7.1.1/../../../../include/c++/7.1.1/x86_64-pc-linux-gnu/bits/c++config.h:533,
from /usr/lib/gcc/x86_64-pc-linux-gnu/7.1.1/../../../../include/c++/7.1.1/cstdio:41,
from external/protobuf/src/google/protobuf/io/strtod.cc:33:
/usr/include/features.h:373:4: warning: #warning _FORTIFY_SOURCE requires compiling with optimization (-O) [-Wcpp]
# warning _FORTIFY_SOURCE requires compiling with optimization (-O)
^~~~~~~
Target @grpc//:grpc_cpp_plugin failed to build
INFO: Elapsed time: 1.720s, Critical Path: 0.33s
At least I made some warnings go away..
I am at the very same stage compiling in gentoo. Found a fix? Id love to contribute with an ebuild once i get this working
@trompa and @iame6162013 I am also stuck on the same error. Do let me know if you found a fix
Same issue here. I googled around, but couldn't figure out a solution.
It seems to be an issue with Bazel not liking the version of GCC? Others around the internet say that this problem crops up when they update their compilers...
Since coriander can run tests on arch without a problem, it's time to go for tf-coriander no? :)
(oh, should I make a separate issue for these? or keep it within one thread? )