FAILED: Build did NOT complete successfully

最新推荐文章于 2024-07-08 15:40:10 发布
最新推荐文章于 2024-07-08 15:40:10 发布
阅读量4.7k 收藏
点赞数
CC 4.0 BY-SA版权
分类专栏： PYTHON
本博客仅供免费阅读，不提供咨询服务。请勿私信。
本文链接：https://blog.youkuaiyun.com/durongze/article/details/84679301
在尝试构建TensorFlow Bigtable组件时遇到链接错误，详细信息显示在编译过程中出现了多个定义冲突，涉及到pb_common和pb_decode等函数。该问题可能源于grpc和nanopb库的不兼容或配置错误。

摘要生成于 C知道 ，由 DeepSeek-R1 满血版支持， 前往体验 >

ERROR: /home/pi/tensorflow-1.12.0/tensorflow/contrib/bigtable/BUILD:53:1: Linking of rule '//tensorflow/contrib/bigtable:python/ops/_bigtable.so' failed (Exit 1) gcc failed: error executing command /usr/bin/gcc -shared -o bazel-out/k8-fastbuild/bin/tensorflow/contrib/bigtable/python/ops/_bigtable.so ... (remaining 64 argument(s) skipped)

Use --sandbox_debug to see verbose messages from the sandbox
/usr/bin/ld.gold: error: bazel-out/k8-fastbuild/bin/external/grpc/_objs/grpc_nanopb/pb_common.pic.o: multiple definition of 'pb_field_iter_begin'
/usr/bin/ld.gold: bazel-out/k8-fastbuild/bin/external/grpc/third_party/nanopb/_objs/nanopb/pb_common.pic.o: previous definition here
/usr/bin/ld.gold: error: bazel-out/k8-fastbuild/bin/external/grpc/_objs/grpc_nanopb/pb_common.pic.o: multiple definition of 'pb_field_iter_next'
/usr/bin/ld.gold: bazel-out/k8-fastbuild/bin/external/grpc/third_party/nanopb/_objs/nanopb/pb_common.pic.o: previous definition here
/usr/bin/ld.gold: error: bazel-out/k8-fastbuild/bin/external/grpc/_objs/grpc_nanopb/pb_common.pic.o: multiple definition of 'pb_field_iter_find'
/usr/bin/ld.gold: bazel-out/k8-fastbuild/bin/external/grpc/third_party/nanopb/_objs/nanopb/pb_common.pic.o: previous definition here
/usr/bin/ld.gold: error: bazel-out/k8-fastbuild/bin/external/grpc/_objs/grpc_nanopb/pb_decode.pic.o: multiple definition of 'pb_read'
/usr/bin/ld.gold: bazel-out/k8-fastbuild/bin/external/grpc/third_party/nanopb/_objs/nanopb/pb_decode.pic.o: previous definition here
/usr/bin/ld.gold: error: bazel-out/k8-fastbuild/bin/external/grpc/_objs/grpc_nanopb/pb_decode.pic.o: multiple definition of 'pb_istream_from_buffer'
/usr/bin/ld.gold: bazel-out/k8-fastbuild/bin/external/grpc/third_party/nanopb/_objs/nanopb/pb_decode.pic.o: previous definition here
/usr/bin/ld.gold: error: bazel-out/k8-fastbuild/bin/external/grpc/_objs/grpc_nanopb/pb_decode.pic.o: multiple definition of 'pb_decode_varint'
/usr/bin/ld.gold: bazel-out/k8-fastbuild/bin/external/grpc/third_party/nanopb/_objs/nanopb/pb_decode.pic.o: previous definition here
/usr/bin/ld.gold: error: bazel-out/k8-fastbuild/bin/external/grpc/_objs/grpc_nanopb/pb_decode.pic.o: multiple definition of 'pb_decode_tag'
/usr/bin/ld.gold: bazel-out/k8-fastbuild/bin/external/grpc/third_party/nanopb/_objs/nanopb/pb_decode.pic.o: previous definition here
/usr/bin/ld.gold: error: bazel-out/k8-fastbuild/bin/external/grpc/_objs/grpc_nanopb/pb_decode.pic.o: multiple definition of 'pb_skip_field'
/usr/bin/ld.gold: bazel-out/k8-fastbuild/bin/external/grpc/third_party/nanopb/_objs/nanopb/pb_decode.pic.o: previous definition here
/usr/bin/ld.gold: error: bazel-out/k8-fastbuild/bin/external/grpc/_objs/grpc_nanopb/pb_decode.pic.o: multiple definition of 'pb_make_string_substream'
/usr/bin/ld.gold: bazel-out/k8-fastbuild/bin/external/grpc/third_party/nanopb/_objs/nanopb/pb_decode.pic.o: previous definition here
/usr/bin/ld.gold: error: bazel-out/k8-fastbuild/bin/external/grpc/_objs/grpc_nanopb/pb_decode.pic.o: multiple definition of 'pb_close_string_substream'
/usr/bin/ld.gold: bazel-out/k8-fastbuild/bin/external/grpc/third_party/nanopb/_objs/nanopb/pb_decode.pic.o: previous definition here
/usr/bin/ld.gold: error: bazel-out/k8-fastbuild/bin/external/grpc/_objs/grpc_nanopb/pb_decode.pic.o: multiple definition of 'pb_decode_noinit'
/usr/bin/ld.gold: bazel-out/k8-fastbuild/bin/external/grpc/third_party/nanopb/_objs/nanopb/pb_decode.pic.o: previous definition here
/usr/bin/ld.gold: error: bazel-out/k8-fastbuild/bin/external/grpc/_objs/grpc_nanopb/pb_decode.pic.o: multiple definition of 'pb_decode'
/usr/bin/ld.gold: bazel-out/k8-fastbuild/bin/external/grpc/third_party/nanopb/_objs/nanopb/pb_decode.pic.o: previous definition here
/usr/bin/ld.gold: error: bazel-out/k8-fastbuild/bin/external/grpc/_objs/grpc_nanopb/pb_decode.pic.o: multiple definition of 'pb_decode_delimited'
/usr/bin/ld.gold: bazel-out/k8-fastbuild/bin/external/grpc/third_party/nanopb/_objs/nanopb/pb_decode.pic.o: previous definition here
/usr/bin/ld.gold: error: bazel-out/k8-fastbuild/bin/external/grpc/_objs/grpc_nanopb/pb_decode.pic.o: multiple definition of 'pb_decode_svarint'
/usr/bin/ld.gold: bazel-out/k8-fastbuild/bin/external/grpc/third_party/nanopb/_objs/nanopb/pb_decode.pic.o: previous definition here
/usr/bin/ld.gold: error: bazel-out/k8-fastbuild/bin/external/grpc/_objs/grpc_nanopb/pb_decode.pic.o: multiple definition of 'pb_decode_fixed32'
/usr/bin/ld.gold: bazel-out/k8-fastbuild/bin/external/grpc/third_party/nanopb/_objs/nanopb/pb_decode.pic.o: previous definition here
/usr/bin/ld.gold: error: bazel-out/k8-fastbuild/bin/external/grpc/_objs/grpc_nanopb/pb_decode.pic.o: multiple definition of 'pb_decode_fixed64'
/usr/bin/ld.gold: bazel-out/k8-fastbuild/bin/external/grpc/third_party/nanopb/_objs/nanopb/pb_decode.pic.o: previous definition here
/usr/bin/ld.gold: error: bazel-out/k8-fastbuild/bin/external/grpc/_objs/grpc_nanopb/pb_encode.pic.o: multiple definition of 'pb_ostream_from_buffer'
/usr/bin/ld.gold: bazel-out/k8-fastbuild/bin/external/grpc/third_party/nanopb/_objs/nanopb/pb_encode.pic.o: previous definition here
/usr/bin/ld.gold: error: bazel-out/k8-fastbuild/bin/external/grpc/_objs/grpc_nanopb/pb_encode.pic.o: multiple definition of 'pb_write'
/usr/bin/ld.gold: bazel-out/k8-fastbuild/bin/external/grpc/third_party/nanopb/_objs/nanopb/pb_encode.pic.o: previous definition here
/usr/bin/ld.gold: error: bazel-out/k8-fastbuild/bin/external/grpc/_objs/grpc_nanopb/pb_encode.pic.o: multiple definition of 'pb_encode_tag'
/usr/bin/ld.gold: bazel-out/k8-fastbuild/bin/external/grpc/third_party/nanopb/_objs/nanopb/pb_encode.pic.o: previous definition here
/usr/bin/ld.gold: error: bazel-out/k8-fastbuild/bin/external/grpc/_objs/grpc_nanopb/pb_encode.pic.o: multiple definition of 'pb_encode_varint'
/usr/bin/ld.gold: bazel-out/k8-fastbuild/bin/external/grpc/third_party/nanopb/_objs/nanopb/pb_encode.pic.o: previous definition here
/usr/bin/ld.gold: error: bazel-out/k8-fastbuild/bin/external/grpc/_objs/grpc_nanopb/pb_encode.pic.o: multiple definition of 'pb_encode_tag_for_field'
/usr/bin/ld.gold: bazel-out/k8-fastbuild/bin/external/grpc/third_party/nanopb/_objs/nanopb/pb_encode.pic.o: previous definition here
/usr/bin/ld.gold: error: bazel-out/k8-fastbuild/bin/external/grpc/_objs/grpc_nanopb/pb_encode.pic.o: multiple definition of 'pb_encode'
/usr/bin/ld.gold: bazel-out/k8-fastbuild/bin/external/grpc/third_party/nanopb/_objs/nanopb/pb_encode.pic.o: previous definition here
/usr/bin/ld.gold: error: bazel-out/k8-fastbuild/bin/external/grpc/_objs/grpc_nanopb/pb_encode.pic.o: multiple definition of 'pb_encode_delimited'
/usr/bin/ld.gold: bazel-out/k8-fastbuild/bin/external/grpc/third_party/nanopb/_objs/nanopb/pb_encode.pic.o: previous definition here
/usr/bin/ld.gold: error: bazel-out/k8-fastbuild/bin/external/grpc/_objs/grpc_nanopb/pb_encode.pic.o: multiple definition of 'pb_encode_submessage'
/usr/bin/ld.gold: bazel-out/k8-fastbuild/bin/external/grpc/third_party/nanopb/_objs/nanopb/pb_encode.pic.o: previous definition here
/usr/bin/ld.gold: error: bazel-out/k8-fastbuild/bin/external/grpc/_objs/grpc_nanopb/pb_encode.pic.o: multiple definition of 'pb_get_encoded_size'
/usr/bin/ld.gold: bazel-out/k8-fastbuild/bin/external/grpc/third_party/nanopb/_objs/nanopb/pb_encode.pic.o: previous definition here
/usr/bin/ld.gold: error: bazel-out/k8-fastbuild/bin/external/grpc/_objs/grpc_nanopb/pb_encode.pic.o: multiple definition of 'pb_encode_svarint'
/usr/bin/ld.gold: bazel-out/k8-fastbuild/bin/external/grpc/third_party/nanopb/_objs/nanopb/pb_encode.pic.o: previous definition here
/usr/bin/ld.gold: error: bazel-out/k8-fastbuild/bin/external/grpc/_objs/grpc_nanopb/pb_encode.pic.o: multiple definition of 'pb_encode_fixed32'
/usr/bin/ld.gold: bazel-out/k8-fastbuild/bin/external/grpc/third_party/nanopb/_objs/nanopb/pb_encode.pic.o: previous definition here
/usr/bin/ld.gold: error: bazel-out/k8-fastbuild/bin/external/grpc/_objs/grpc_nanopb/pb_encode.pic.o: multiple definition of 'pb_encode_fixed64'
/usr/bin/ld.gold: bazel-out/k8-fastbuild/bin/external/grpc/third_party/nanopb/_objs/nanopb/pb_encode.pic.o: previous definition here
/usr/bin/ld.gold: error: bazel-out/k8-fastbuild/bin/external/grpc/_objs/grpc_nanopb/pb_encode.pic.o: multiple definition of 'pb_encode_string'
/usr/bin/ld.gold: bazel-out/k8-fastbuild/bin/external/grpc/third_party/nanopb/_objs/nanopb/pb_encode.pic.o: previous definition here
collect2: error: ld returned 1 exit status
Target //tensorflow/tools/pip_package:build_pip_package failed to build
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 215.210s, Critical Path: 12.14s, Remote (0.00% of the time): [queue: 0.00%, setup: 0.00%, process: 0.00%]
INFO: 178 processes: 178 processwrapper-sandbox.
FAILED: Build did NOT complete successfully

 

Linux MediaPipe C++版手势识别环境搭建与编译
xiongfeng4152的博客
12-09 3461
环境：Ubuntu18.04，gcc/g++ version>8.0, OpenCV version==3.4, Bazel version==3.7.2 1、安装Bazel 见官方文档：Installing Bazel using Bazelisk - Bazel main 2、下载MedianPipe源码 git clone https://github.com/google/mediapipe.git cd mediapipe 3、安装OpenCV和FFmpeg Median
dockerfile报错：“/bin/sh -c yum -y install vim net-tools wget“ did not complete successfully: exit code
weixin_47202856的博客
06-25 5628
ERROR: failed to solve: process "/bin/sh -c yum -y install vim net-tools wget" did not complete successfully: exit code: 1。解决办法
apollo编译出错./apollo.sh build 报错如下ERROR: Analysis of target ‘//modules/v2x/v2x_proxy/os_interface:os_i
wangjl2416的博客
08-01 2394
ERROR: Analysis of target '//modules/v2x/v2x_proxy/os_interface:os_interface_test_cpplint' failed; build aborted: java.io.IOException: Error downloading [https://dl.google.com/go/go1.12.5.linux-amd64.tar.gz] to /apollo/.cache/bazel/540135163923dd7d5820f3ee
linking with `x86_64-w64-mingw32-gcc` failed: exit code: 1报错解决办法
Cfoxer的博客
05-29 1401
网上的解决办法大多都是下载MinGW,然后配置环境变量(设置clion工具链,我用的clion)先弄vs依赖,(我也不知道具体要下哪些,就把c++那一块的全给下了)但是我都没用,最终我的解决办法是按照官方方法下载了。再默认1安装rust就可以了。
Dockerfile 在Ubuntu20.04构建镜像，ERROR: failed to solve: process “...“ did not complete successfully..
weixin_54878462的博客
07-08 3221
2. 运行docker build即可（博主自己构建了一个循环build的脚本文件，其实大差不差）重复build了好几次，都是报这个错误，考虑镜像源问题，估计是apt-get这个命令的问题。最后结果如下：镜像构建成功！
error: command '/usr/bin/gcc' failed with exit code 1 问题解决
test7788990的博客
01-27 9188
linux环境， python3.7.问题描述： 安装rally， pip3 install -r requirements.txt 时提示如下： 说明openssl 已安装。解决：1. pip3 install --upgrade pip ， 结果输出如下 ...
(14:11:39) INFO: 2 processes: 2 internal. (14:11:39) FAILED: Build did NOT complete successfully (14:11:39) FAILED: Build did NOT complete successfully [buildtool] 2025-06-14 22:11:39 ERROR Encounter ErrCode.BazelErr [buildtool] 2025-06-14 22:11:39 ERROR hint: Compiling and install failed! [buildtool] 2025-06-14 22:11:39 ERROR solution: Please checkout the build file by following bazel error hints 出现错误，这个怎么解决
06-16
- **依赖问题**：检查`no such package`或`Failed to fetch`提示 - **权限问题**：注意`Permission denied`相关输出 --- ### 3. **常见修复方案** #### ▶ 案例1：C++工具链配置错误 若出现`xcrun: error`或`clang...
bazel build --verbose_failures //your:target 2>&1 | tee build.log WARNING: The following rc files are no longer being read, please transfer their contents or import their path into one of the standard rc files: /apollo_workspace/tools/bazel.rc (14:14:44) INFO: Current date is 2025-06-14 (14:14:44) Loading: (14:14:44) Loading: 0 packages loaded (14:14:44) ERROR: Skipping '//your:target': no such package 'your': BUILD file not found in any of the following directories. Add a BUILD file to a directory to mark it as a package. - /apollo_workspace/your (14:14:44) WARNING: Target pattern parsing failed. (14:14:44) ERROR: no such package 'your': BUILD file not found in any of the following directories. Add a BUILD file to a directory to mark it as a package. - /apollo_workspace/your (14:14:44) INFO: Elapsed time: 0.188s (14:14:44) INFO: 0 processes. (14:14:44) FAILED: Build did NOT complete successfully (0 packages loaded) (14:14:44) FAILED: Build did NOT complete successfully (0 packages loaded)
06-15
当 Bazel 报告 `BUILD file not found` 错误时，通常表示构建系统无法定位或识别您的构建配置。以下是系统化的解决步骤，结合 Bazel 的特性（如引用[1]提到的增量构建一致性保证）和常见解决方案： --- ### 1. **...
ERROR: Skipping 'modules/perception/env/…': no such target '//modules/perception/env:…': target '…' not declared in package 'modules/perception/env' defined by /apollo/modules/perception/env/BUILD (03:04:27) WARNING: Target pattern parsing failed. (03:04:27) ERROR: no such target '//modules/perception/env:…': target '…' not declared in package 'modules/perception/env' defined by /apollo/modules/perception/env/BUILD (03:04:27) INFO: Elapsed time: 0.295s (03:04:27) INFO: 0 processes. (03:04:27) FAILED: Build did NOT complete successfully (0 packages loaded)但是编译报错了
最新发布
08-05
ERROR: Skipping 'modules/perception/env/…': no such target '//modules/perception/env:…': target '…' not declared in package 'modules/perception/env' defined by /apollo/modules/perception/env/BUILD ...
FAILED: Build did NOT complete successfully (5 packages loaded, 6 targets configured) currently loading: @bazel_platform//toolchains/python3 ... (2 packages) Fetching repository @remotejdk11_linux_toolchain_config_repo; starting Fetching repository @local_config_sh; starting Fetching repository @local_jdk; starting Fetching repository @remotejdk11_macos_toolchain_config_repo; starting Fetching repository @remotejdk18_linux_aarch64_toolchain_config_repo; starting Fetching repository @remotejdk18_macos_aarch64_toolchain_config_repo; starting Fetching repository @remotejdk18_linux_toolchain_config_repo; starting Fetching repository @remotejdk18_win_toolchain_config_repo; starting ... (23 fetches) 现在又报这些错误
03-28
好的，现在用户遇到了另一个Bazel构建错误，显示“Build did NOT complete successfully”，并且有很多包的加载和仓库获取的信息。我需要先分析这些错误信息，找出可能的原因，并给出解决方案。 首先，用户之前的...
root@localhost:~/5.15-13# tools/bazel run //common:kernel_aarch64_dist --config=fast INFO: Analyzed target //common:kernel_aarch64_dist (0 packages loaded, 0 targets configured). INFO: Found 1 target... ERROR: /root/5.15-13/common/BUILD.bazel:52:22: Building kernel kernel_aarch64 failed: (Exit 2): bash failed: error executing command (from target //common:kernel_aarch64) /bin/bash -c ... (remaining 1 argument skipped) /root/5.15-13/common/kernel/sys.c:3009:31: error: incompatible pointer types passing 'struct perf_event *' to parameter of type 'struct perf_event **'; take the address with & [-Werror,-Wincompatible-pointer-types] unregister_wide_hw_breakpoint(bp); ^~ & /root/5.15-13/common/include/linux/hw_breakpoint.h:76:73: note: passing argument to parameter 'cpu_events' here extern void unregister_wide_hw_breakpoint(struct perf_event * __percpu *cpu_events); ^ /root/5.15-13/common/kernel/sys.c:3039:4: error: incompatible pointer types assigning to 'struct perf_event *' from 'struct perf_event **'; dereference with * [-Werror,-Wincompatible-pointer-types] bp = register_wide_hw_breakpoint(&attr, hit_handler, NULL); ^ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ * /root/5.15-13/common/kernel/sys.c:3049:9: error: implicit declaration of function 'perf_event_set_target' [-Werror,-Wimplicit-function-declaration] perf_event_set_target(event, tsk); // 关联到目标进程 ^ 3 errors generated. make[2]: *** [/root/5.15-13/common/scripts/Makefile.build:287: kernel/sys.o] Error 1 make[1]: *** [/root/5.15-13/common/Makefile:1953: kernel] Error 2 make: *** [Makefile:244: __sub-make] Error 2 Target //common:kernel_aarch64_dist failed to build Use --verbose_failures to see the command lines of failed build steps. ERROR: /root/5.15-13/common/BUILD.bazel:52:22 Middleman _middlemen/common_Skernel_Uaarch64_Udist-runfiles failed: (Exit 2): bash failed: error executing command (from target //common:kernel_aarch64) /bin/bash -c ... (remaining 1 argument skipped) INFO: Elapsed time: 45.356s, Critical Path: 44.43s INFO: 4 processes: 4 internal. FAILED: Build did NOT complete successfully FAILED: Build did NOT complete successfully root@localhost:~/5.15-13# 继续仔细修复 完整发给我代码
07-20
pr_err("register_wide_hw_breakpoint failed: %d\n", ret); return ret; } return 0; } static void __exit sample_exit(void) { unregister_wide_hw_breakpoint(sample_hbp); } module_init(sample_init);...
command ‘gcc‘ failed with exit status 1
Li_yan的博客
10-11 712
报错： command 'gcc' failed with exit status 1 解决方法
Tensorflow 编译
ayj12345的博客
03-13 544
Tensorflow 编译c++调用所需动态库（1） 版本选择 linux https://tensorflow.google.cn/install/source 版本 Python 版本 编译器 构建工具 tensorflow-1.12.0 2.7、3.3-3.6 GCC 4.8 Bazel 0.15.0 tensorflow-1.11.0 2.7、3.3-3.6 GCC 4...
g++中的常用编译参数（持续更新-编译常见错误）
快乐小半半的博客
10-10 1421
centos中g++的常用编译优化参数。
error: command ‘/usr/bin/gcc‘ failed with exit code 1
m0_52071515的博客
04-24 1857
仔细看一下报错的信息，在我的报错信息中显示pcdet/ops/iou3d_nms/src/iou3d_cpu.cpp，然后打开了文件仔细看了一下代码，发现下面的注释信息未被正常注释，注释掉即可解决问题。
关于Python安装模块出现error: command 'gcc' failed with exit status 1错误的解决方法
SAGGITARXM
07-17 9562
当使用pip install ###时，有时会出现如标题上的问题，我遇到的问题如下： _posixsubprocess.c:3:20: fatal error: Python.h: No such file or directory #include "Python.h" ^ compilation terminated. ...
Python报错：error: command ‘/usr/bin/gcc‘ failed with exit code 1
热门推荐
苏寅的博客
07-01 4万+
前言 平时我们在Linux服务器上使用pip安装一些Python依赖包的时候偶尔会遇到如下所示的报错： ... #include "Python.h" ^~~~~~~~~~ compilation terminated. error: command '/usr/bin/gcc' failed with exit code 1 ... 常见的如安装uWSGI和mysqlclient都会出现类似报错，那么遇到这种情况该怎么办呢？ 解决方案 对于yum(CentOS, RHEL…) yu
error: command 'gcc' failed with exit status 1
weixin_30794491的博客
01-10 494
MacOS下想安装MySQL-Python，执行语句： sudo pip install MySQL-Python 遇到了如下错误信息： /Users/kaitlyn/anaconda3/envs/env2.7/lib/gcc/x86_64-apple-darwin11.4.2/4.8.5/include-fixed/limits.h:168:61: fatal error:...
评论 4
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值