Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

[Bug] Error when build

未关闭
  • 哪里不对？
#84 0 条评论 4 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
1/5
预计耗时
1 小时以内
新手友好度
55/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
停滞
技术栈
cmake, cpp
领域
build-system

调研方向

从 main_portable.cc:216 开始，将 absl::MutexLock 调用与构建错误中显示的构造函数签名进行比较。在 macOS 上运行 cmake --build build/out --config Release；当 bindiff 目标在没有 MutexLock 错误的情况下成功编译时即表示完成。

由索引模型根据 Issue 内容生成。

描述

Describe the bug
I got error when build
tiendoan@M3-Pro bindiff % cmake --build build/out --config Release
[0/2] Re-checking globbed directories...
[571/578] Building CXX object CMakeFiles/bindiff.dir/main_portable.cc.o
FAILED: [code=1] CMakeFiles/bindiff.dir/main_portable.cc.o
/usr/bin/c++ -I/Users/tiendoan/bindiff/build/out/_deps/absl-src -I/Users/tiendoan/bindiff/build/binexport -I/Users/tiendoan/bindiff/build/binexport/stubs -I/Users/tiendoan/bindiff/build/out/_deps/binexport-build/gen_include -I/Users/tiendoan/bindiff/build/out/_deps/binexport-build/src_include -I/Users/tiendoan/bindiff/build/binexport/boost_parts -I/Users/tiendoan/bindiff/build/out/_deps/protobuf-src/src -I/Users/tiendoan/bindiff/build/out/_deps/protobuf-src/third_party/utf8_range -I/Users/tiendoan/bindiff/build/out/src_include -I/Users/tiendoan/bindiff/build/out/gen_include -I/Users/tiendoan/bindiff -O3 -DNDEBUG -std=c++17 -flto=thin -arch arm64 -fPIE -Wno-nullability-completeness -Wno-invalid-noreturn -Wno-deprecated -gfull -MD -MT CMakeFiles/bindiff.dir/main_portable.cc.o -MF CMakeFiles/bindiff.dir/main_portable.cc.o.d -o CMakeFiles/bindiff.dir/main_portable.cc.o -c /Users/tiendoan/bindiff/main_portable.cc
/Users/tiendoan/bindiff/main_portable.cc:216:23: error: no matching constructor for initialization of 'absl::MutexLock'
absl::MutexLock lock(g_queue_mutex);
^ ~~~~~~~~~~~~~
/Users/tiendoan/bindiff/build/out/_deps/absl-src/absl/synchronization/mutex.h:590:12: note: candidate constructor not viable: no known conversion from 'absl::Mutex' to 'Mutex ' for 1st argument; take the address of the argument with &
explicit MutexLock(Mutex absl_nonnull mu) ABSL_EXCLUSIVE_LOCK_FUNCTION(mu)
^
/Users/tiendoan/bindiff/build/out/_deps/absl-src/absl/synchronization/mutex.h:604:3: note: candidate constructor not viable: no known conversion from 'absl::Mutex' to 'const MutexLock' for 1st argument
MutexLock(const MutexLock&) = delete; // NOLINT(runtime/mutex)
^
/Users/tiendoan/bindiff/build/out/_deps/absl-src/absl/synchronization/mutex.h:605:3: note: candidate constructor not viable: no known conversion from 'absl::Mutex' to 'MutexLock' for 1st argument
MutexLock(MutexLock&&) = delete; // NOLINT(runtime/mutex)
^
/Users/tiendoan/bindiff/build/out/_deps/absl-src/absl/synchronization/mutex.h:598:12: note: candidate constructor not viable: requires 2 arguments, but 1 was provided
explicit MutexLock(Mutex* absl_nonnull mu, const Condition& cond)
^
1 error generated.
[573/578] Building C object CMakeFiles/sqlite.dir/_deps/sqlite-src/sqlite3.c.o
ninja: build stopped: subcommand failed.

Environment (please complete the following information):

  • OS and version: MacOS
  • Disassembler and version: SDK IDA 9.1

Additional context
I saw commit b3ba8f81d1296585b710512c3cc2e9697e2c1298 remove & in absl::MutexLock lock. I just add & back and can build

主要语言
Java
星标
3.2k
派生
244
30 天内没有已合并 PR

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

google/bindiff 的其他 Issue

查看 google/bindiff 的全部 Issue

相似的 Issue

更多 Java Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。