go build/install/run/clean/...等

最新推荐文章于 2020-09-14 13:03:14 发布
原创 最新推荐文章于 2020-09-14 13:03:14 发布 · 335 阅读 · 0 ·
CC 4.0 BY-SA版权
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。

本文提供了 Go 语言命令教程的详细介绍，涵盖了从基础到高级的各种命令使用方法，适合初学者和有一定经验的开发者进行学习。
Go 学习笔记（37）— 标准命令行工具（go build 跨平台编译、交叉编译、go clean、go run、go fmt、go install、go get、go vet）
wohu1104的专栏
05-24 9593
1. 标准命令简述 Go 本身包含来大量用于处理 Go 程序的命令和工具。 命令 作用 build 用于编译指定的代码包或 Go 语言源码文件。命令源码文件会被编译成可执行文件，并存放到命令执行的目录或指定目录下。而库源码文件被编译后，则不会在非临时目录中留下任何文件。 clean 用于清除因执行其他 go 命令而遗留下来的临时目录和文件。 doc 用于显示打印 Go 语言代码包以及程序实体的文档。 env 用于打印 Go 语言相关的环境信息。 fix 用于修正指定代码的
Go命令基础之go install
实践求真知
11-22 2237
一 简介 1、用于编译并安装代码包或源码文件。 2、安装代码包会在当前工作区的pkg/下生成归档文件。 3、安装命令源码文件会在当前工作区的bin目录或$GOBIN目录下生成可执行文件。 4、执行该命令且不追加任何参数时，它会试图把当前目录作为代码包并安装。 5、执行该命令且以代码包的导入路径作为参数时，该代码包及其依赖会被安装。 6、执行该命令且以命令源码文件及其库源码文件作为参数时
go语言之go run/build/install/get
xiezhongtian的专栏
08-11 1372
go run go build go install
go语言普通的常用命令（略）
weixin_44001521的博客
09-14 592
1、go doc 和dodoc 快速显示指定软件包的帮助文档 godoc -http=:6060 -index -play -http=：PORT 指定监听的地址，默认6060 -index 支持关键词索引 -play 在浏览器里对go语言进行测试 2、go build 编译软件包 -x 打印执行过程的详细信息，辅助测试 -gcflags 指定编译器参数 -ldflags 指定链接器参数，通过-X 动态指定包变量值 3、go clean 清理项目，删除编译生成的二进制文件和临时文件 -i 删除go ins
go run go build go install 命令解释
热门推荐
学无止境
11-28 2万+
go run：go run 编译并直接运行程序，它会产生一个临时文件（但不会生成 .exe 文件），直接在命令行输出程序执行结果，方便用户调试。 go build：go build 用于测试编译包，主要检查是否会有编译错误，如果是一个可执行文件的源码（即是 main 包），就会直接生成一个可执行文件。 go install：go install 的作用有两步：第一步是编译导入的包文件，所有导入
IDEA Maven Web项目的install和run
窗边冷月光
04-17 2648
首先，进入 Run -> Edit Configurations -> Add New Configuration 添加两个Maven，分别取名为instal、run install Paramsters： Working directory：项目的路径,如果是多模块项目，那就是最外层的项目路径。 Command line：clean install Runne...
go run build/ci.go install ./cmd/geth go: errors parsing go.mod: /usr/local/go-ethereum-master/go.mod:3: invalid go version '1.24.0': must match format 1.23 /usr/local/go-ethereum-master/go.mod:151: unknown block type: tool make: *** [geth] 错误 1
10-03
对于执行 `go run build/ci.go install ./cmd/geth` 命令时出现 `errors parsing go.mod`、`invalid go version`、`unknown block type: tool` 错误以及最终 `make: *** [geth] 错误 1`，可以参考以下思路来解决： ...
在linux可以使用“make geth”，那在window下输入什么命令可以达到相应目的，以下是Makefile文件中的内容：“# This Makefile is meant to be used by people that do not usually work # with Go source code. If you know what GOPATH is then you probably # don't need to bother with make. .PHONY: geth all test lint fmt clean devtools help GOBIN = ./build/bin GO ?= latest GORUN = go run #? geth: Build geth. geth: $(GORUN) build/ci.go install ./cmd/geth @echo "Done building." @echo "Run \"$(GOBIN)/geth\" to launch geth." #? all: Build all packages and executables. all: $(GORUN) build/ci.go install #? test: Run the tests. test: all $(GORUN) build/ci.go test #? lint: Run certain pre-selected linters. lint: ## Run linters. $(GORUN) build/ci.go lint #? fmt: Ensure consistent code formatting. fmt: gofmt -s -w $(shell find . -name "*.go") #? clean: Clean go cache, built executables, and the auto generated folder. clean: go clean -cache rm -fr build/_workspace/pkg/ $(GOBIN)/* # The devtools target installs tools required for 'go generate'. # You need to put $GOBIN (or $GOPATH/bin) in your PATH to use 'go generate'. #? devtools: Install recommended developer tools. devtools: env GOBIN= go install golang.org/x/tools/cmd/stringer@latest env GOBIN= go install github.com/fjl/gencodec@latest env GOBIN= go install google.golang.org/protobuf/cmd/protoc-gen-go@latest env GOBIN= go install ./cmd/abigen @type "solc" 2> /dev/null || echo 'Please install solc' @type "protoc" 2> /dev/null || echo 'Please install protoc' #? help: Get more info on make commands. help: Makefile @echo '' @echo 'Usage:' @echo ' make [target]' @echo '' @echo 'Targets:' @sed -n 's/^#?//p' $< | column -t -s ':' | sort | sed -e 's/^/ /'”
03-16
看一下Makefile里的geth目标，对应的命令是“go run build/ci.go install ./cmd/geth”。所以实际上，在Linux下执行“make geth”其实就是运行这个go命令。那么在Windows下，只要能够运行同样的go命令，应该就可以...
a 0:00:00 Installing build dependencies ... error error: subprocess-exited-with-error × pip subprocess to install build dependencies did not run successfully. │ exit code: 1 ╰─> [229 lines of output] WARNING: Skip installing pip, this will break the python-pip package (termux). Looking in indexes: https://pypi.tuna.tsinghua.edu.cn/simple Ignoring numpy: markers 'python_version == "3.6" and platform_machine != "aarch64" and platform_machine != "arm64"' don't match your environment Ignoring numpy: markers 'python_version == "3.7" and platform_machine != "aarch64" and platform_machine != "arm64"' don't match your environment Ignoring numpy: markers 'python_version == "3.8" and platform_machine != "aarch64" and platform_machine != "arm64"' don't match your environment Ignoring numpy: markers 'python_version < "3.9" and sys_platform == "linux" and platform_machine == "aarch64"' don't match your environment Ignoring numpy: markers 'python_version < "3.9" and sys_platform == "darwin" and platform_machine == "arm64"' don't match your environment Ignoring setuptools: markers 'python_version < "3.12"' don't match your environment Collecting numpy>=2.0.0 Downloading https://pypi.tuna.tsinghua.edu.cn/packages/2e/19/d7c972dfe90a353dbd3efbbe1d14a5951de80c99c9dc1b93cd998d51dc0f/numpy-2.3.1.tar.gz (20.4 MB) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 20.4/20.4 MB 8.5 MB/s eta 0:00:00 Installing build dependencies: started Installing build dependencies: finished with status 'done' Getting requirements to build wheel: started Getting requirements to build wheel: finished with status 'done' Installing backend dependencies: started Installing backend dependencies: still running... Installing backend dependencies: finished with status 'error' error: subprocess-exited-with-error × pip subprocess to install backend dependencies did not run successfully. │ exit code: 1 ╰─> [196 lines of output] Looking in indexes: https://pypi.tuna.tsinghua.edu.cn/simple Collecting ninja>=1.8.2 Downloading https://pypi.tuna.tsinghua.edu.cn/packages/95/d4/6b0324541018561c5e73e617bd16f20a4fc17d1179bb3b3520b6ca8beb7b/ninja-1.11.1.4.tar.gz (201 kB) Installing build dependencies: started Installing build dependencies: finished with status 'done' Getting requirements to build wheel: started Getting requirements to build wheel: finished with status 'done' Installing backend dependencies: started Installing backend dependencies: finished with status 'done' Preparing metadata (pyproject.toml): started Preparing metadata (pyproject.toml): finished with status 'done' Collecting patchelf>=0.11.0 Downloading https://pypi.tuna.tsinghua.edu.cn/packages/0d/41/dc3ee5838db2d90be935adb53ae7745135d9c719d070b1989b246f983c7f/patchelf-0.17.2.2.tar.gz (149 kB) Installing build dependencies: started Installing build dependencies: finished with status 'done' Getting requirements to build wheel: started Getting requirements to build wheel: finished with status 'done' Installing backend dependencies: started Installing backend dependencies: finished with status 'done' Preparing metadata (pyproject.toml): started Preparing metadata (pyproject.toml): finished with status 'done' Building wheels for collected packages: ninja, patchelf Building wheel for ninja (pyproject.toml): started Building wheel for ninja (pyproject.toml): still running... Building wheel for ninja (pyproject.toml): finished with status 'error' error: subprocess-exited-with-error × Building wheel for ninja (pyproject.toml) did not run successfully. │ exit code: 1 ╰─> [120 lines of output] /data/data/com.termux/files/usr/tmp/pip-build-env-4j78z2m7/normal/lib/python3.12/site-packages/setuptools_scm/git.py:310: UserWarning: git archive did not support describe output warnings.warn("git archive did not support describe output") /data/data/com.termux/files/usr/tmp/pip-build-env-4j78z2m7/normal/lib/python3.12/site-packages/setuptools_scm/git.py:328: UserWarning: unprocessed git archival found (no export subst applied) warnings.warn("unprocessed git archival found (no export subst applied)") *** scikit-build-core 0.11.5 using CMake 3.31.6 (wheel) *** Configuring CMake... loading initial cache file build/py3-none-linux_aarch64/CMakeInit.txt -- The C compiler identification is Clang 20.1.7 -- The CXX compiler identification is Clang 20.1.7 -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working C compiler: /data/data/com.termux/files/usr/bin/aarch64-linux-android-clang - skipped -- Detecting C compile features -- Detecting C compile features - done -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Check for working CXX compiler: /data/data/com.termux/files/usr/bin/aarch64-linux-android-clang++ - skipped -- Detecting CXX compile features -- Detecting CXX compile features - done -- ************************************ -- Ninja Python Distribution -- -- RUN_NINJA_TEST : OFF -- ************************************ -- IPO / LTO not supported: <Change Dir: '/data/data/com.termux/files/usr/tmp/pip-install-nuu7do6s/ninja_7200d3032e2b456abb23067d29afe294/build/py3-none-linux_aarch64/_deps/ninja-build/CMakeFiles/_CMakeLTOTest-CXX/bin' Run Build Command(s): /data/data/com.termux/files/usr/bin/cmake -E env VERBOSE=1 /data/data/com.termux/files/usr/bin/make -f Makefile /data/data/com.termux/files/usr/bin/cmake -S/data/data/com.termux/files/usr/tmp/pip-install-nuu7do6s/ninja_7200d3032e2b456abb23067d29afe294/build/py3-none-linux_aarch64/_deps/ninja-build/CMakeFiles/_CMakeLTOTest-CXX/src -B/data/data/com.termux/files/usr/tmp/pip-install-nuu7do6s/ninja_7200d3032e2b456abb23067d29afe294/build/py3-none-linux_aarch64/_deps/ninja-build/CMakeFiles/_CMakeLTOTest-CXX/bin --check-build-system CMakeFiles/Makefile.cmake 0 /data/data/com.termux/files/usr/bin/cmake -E cmake_progress_start /data/data/com.termux/files/usr/tmp/pip-install-nuu7do6s/ninja_7200d3032e2b456abb23067d29afe294/build/py3-none-linux_aarch64/_deps/ninja-build/CMakeFiles/_CMakeLTOTest-CXX/bin/CMakeFiles /data/data/com.termux/files/usr/tmp/pip-install-nuu7do6s/ninja_7200d3032e2b456abb23067d29afe294/build/py3-none-linux_aarch64/_deps/ninja-build/CMakeFiles/_CMakeLTOTest-CXX/bin//CMakeFiles/progress.marks /data/data/com.termux/files/usr/bin/make -f CMakeFiles/Makefile2 all make[1]: Entering directory '/data/data/com.termux/files/usr/tmp/pip-install-nuu7do6s/ninja_7200d3032e2b456abb23067d29afe294/build/py3-none-linux_aarch64/_deps/ninja-build/CMakeFiles/_CMakeLTOTest-CXX/bin' /data/data/com.termux/files/usr/bin/make -f CMakeFiles/foo.dir/build.make CMakeFiles/foo.dir/depend make[2]: Entering directory '/data/data/com.termux/files/usr/tmp/pip-install-nuu7do6s/ninja_7200d3032e2b456abb23067d29afe294/build/py3-none-linux_aarch64/_deps/ninja-build/CMakeFiles/_CMakeLTOTest-CXX/bin' cd /data/data/com.termux/files/usr/tmp/pip-install-nuu7do6s/ninja_7200d3032e2b456abb23067d29afe294/build/py3-none-linux_aarch64/_deps/ninja-build/CMakeFiles/_CMakeLTOTest-CXX/bin && /data/data/com.termux/files/usr/bin/cmake -E cmake_depends "Unix Makefiles" /data/data/com.termux/files/usr/tmp/pip-install-nuu7do6s/ninja_7200d3032e2b456abb23067d29afe294/build/py3-none-linux_aarch64/_deps/ninja-build/CMakeFiles/_CMakeLTOTest-CXX/src /data/data/com.termux/files/usr/tmp/pip-install-nuu7do6s/ninja_7200d3032e2b456abb23067d29afe294/build/py3-none-linux_aarch64/_deps/ninja-build/CMakeFiles/_CMakeLTOTest-CXX/src /data/data/com.termux/files/usr/tmp/pip-install-nuu7do6s/ninja_7200d3032e2b456abb23067d29afe294/build/py3-none-linux_aarch64/_deps/ninja-build/CMakeFiles/_CMakeLTOTest-CXX/bin /data/data/com.termux/files/usr/tmp/pip-install-nuu7do6s/ninja_7200d3032e2b456abb23067d29afe294/build/py3-none-linux_aarch64/_deps/ninja-build/CMakeFiles/_CMakeLTOTest-CXX/bin /data/data/com.termux/files/usr/tmp/pip-install-nuu7do6s/ninja_7200d3032e2b456abb23067d29afe294/build/py3-none-linux_aarch64/_deps/ninja-build/CMakeFiles/_CMakeLTOTest-CXX/bin/CMakeFiles/foo.dir/DependInfo.cmake make[2]: Leaving directory '/data/data/com.termux/files/usr/tmp/pip-install-nuu7do6s/ninja_7200d3032e2b456abb23067d29afe294/build/py3-none-linux_aarch64/_deps/ninja-build/CMakeFiles/_CMakeLTOTest-CXX/bin' /data/data/com.termux/files/usr/bin/make -f CMakeFiles/foo.dir/build.make CMakeFiles/foo.dir/build make[2]: Entering directory '/data/data/com.termux/files/usr/tmp/pip-install-nuu7do6s/ninja_7200d3032e2b456abb23067d29afe294/build/py3-none-linux_aarch64/_deps/ninja-build/CMakeFiles/_CMakeLTOTest-CXX/bin' [ 25%] Building CXX object CMakeFiles/foo.dir/foo.cpp.o /data/data/com.termux/files/usr/bin/aarch64-linux-android-clang++ -O2 -g -DNDEBUG -flto=thin -MD -MT CMakeFiles/foo.dir/foo.cpp.o -MF CMakeFiles/foo.dir/foo.cpp.o.d -o CMakeFiles/foo.dir/foo.cpp.o -c /data/data/com.termux/files/usr/tmp/pip-install-nuu7do6s/ninja_7200d3032e2b456abb23067d29afe294/build/py3-none-linux_aarch64/_deps/ninja-build/CMakeFiles/_CMakeLTOTest-CXX/src/foo.cpp [ 50%] Linking CXX static library libfoo.a /data/data/com.termux/files/usr/bin/cmake -P CMakeFiles/foo.dir/cmake_clean_target.cmake /data/data/com.termux/files/usr/bin/cmake -E cmake_link_script CMakeFiles/foo.dir/link.txt --verbose=1 "/data/data/com.termux/files/usr/bin/llvm-ar" qc libfoo.a CMakeFiles/foo.dir/foo.cpp.o "/data/data/com.termux/files/usr/bin/llvm-ranlib" libfoo.a make[2]: Leaving directory '/data/data/com.termux/files/usr/tmp/pip-install-nuu7do6s/ninja_7200d3032e2b456abb23067d29afe294/build/py3-none-linux_aarch64/_deps/ninja-build/CMakeFiles/_CMakeLTOTest-CXX/bin' [ 50%] Built target foo /data/data/com.termux/files/usr/bin/make -f CMakeFiles/boo.dir/build.make CMakeFiles/boo.dir/depend make[2]: Entering directory '/data/data/com.termux/files/usr/tmp/pip-install-nuu7do6s/ninja_7200d3032e2b456abb23067d29afe294/build/py3-none-linux_aarch64/_deps/ninja-build/CMakeFiles/_CMakeLTOTest-CXX/bin' cd /data/data/com.termux/files/usr/tmp/pip-install-nuu7do6s/ninja_7200d3032e2b456abb23067d29afe294/build/py3-none-linux_aarch64/_deps/ninja-build/CMakeFiles/_CMakeLTOTest-CXX/bin && /data/data/com.termux/files/usr/bin/cmake -E cmake_depends "Unix Makefiles" /data/data/com.termux/files/usr/tmp/pip-install-nuu7do6s/ninja_7200d3032e2b456abb23067d29afe294/build/py3-none-linux_aarch64/_deps/ninja-build/CMakeFiles/_CMakeLTOTest-CXX/src /data/data/com.termux/files/usr/tmp/pip-install-nuu7do6s/ninja_7200d3032e2b456abb23067d29afe294/build/py3-none-linux_aarch64/_deps/ninja-build/CMakeFiles/_CMakeLTOTest-CXX/src /data/data/com.termux/files/usr/tmp/pip-install-nuu7do6s/ninja_7200d3032e2b456abb23067d29afe294/build/py3-none-linux_aarch64/_deps/ninja-build/CMakeFiles/_CMakeLTOTest-CXX/bin /data/data/com.termux/files/usr/tmp/pip-install-nuu7do6s/ninja_7200d3032e2b456abb23067d29afe294/build/py3-none-linux_aarch64/_deps/ninja-build/CMakeFiles/_CMakeLTOTest-CXX/bin /data/data/com.termux/files/usr/tmp/pip-install-nuu7do6s/ninja_7200d3032e2b456abb23067d29afe294/build/py3-none-linux_aarch64/_deps/ninja-build/CMakeFiles/_CMakeLTOTest-CXX/bin/CMakeFiles/boo.dir/DependInfo.cmake make[2]: Leaving directory '/data/data/com.termux/files/usr/tmp/pip-install-nuu7do6s/ninja_7200d3032e2b456abb23067d29afe294/build/py3-none-linux_aarch64/_deps/ninja-build/CMakeFiles/_CMakeLTOTest-CXX/bin' /data/data/com.termux/files/usr/bin/make -f CMakeFiles/boo.dir/build.make CMakeFiles/boo.dir/build make[2]: Entering directory '/data/data/com.termux/files/usr/tmp/pip-install-nuu7do6s/ninja_7200d3032e2b456abb23067d29afe294/build/py3-none-linux_aarch64/_deps/ninja-build/CMakeFiles/_CMakeLTOTest-CXX/bin' [ 75%] Building CXX object CMakeFiles/boo.dir/main.cpp.o /data/data/com.termux/files/usr/bin/aarch64-linux-android-clang++ -O2 -g -DNDEBUG -flto=thin -MD -MT CMakeFiles/boo.dir/main.cpp.o -MF CMakeFiles/boo.dir/main.cpp.o.d -o CMakeFiles/boo.dir/main.cpp.o -c /data/data/com.termux/files/usr/tmp/pip-install-nuu7do6s/ninja_7200d3032e2b456abb23067d29afe294/build/py3-none-linux_aarch64/_deps/ninja-build/CMakeFiles/_CMakeLTOTest-CXX/src/main.cpp [100%] Linking CXX executable boo /data/data/com.termux/files/usr/bin/cmake -E cmake_link_script CMakeFiles/boo.dir/link.txt --verbose=1 aarch64-linux-android-clang++: error: invalid linker name in argument '-fuse-ld=gold' aarch64-linux-android-clang++: error: invalid linker name in argument '-fuse-ld=gold' /data/data/com.termux/files/usr/bin/aarch64-linux-android-clang++ -O2 -g -DNDEBUG -flto=thin -fuse-ld=gold CMakeFiles/boo.dir/main.cpp.o -o boo libfoo.a make[2]: *** [CMakeFiles/boo.dir/build.make:104: boo] Error 1 make[2]: Leaving directory '/data/data/com.termux/files/usr/tmp/pip-install-nuu7do6s/ninja_7200d3032e2b456abb23067d29afe294/build/py3-none-linux_aarch64/_deps/ninja-build/CMakeFiles/_CMakeLTOTest-CXX/bin' make[1]: *** [CMakeFiles/Makefile2:125: CMakeFiles/boo.dir/all] Error 2 make[1]: Leaving directory '/data/data/com.termux/files/usr/tmp/pip-install-nuu7do6s/ninja_7200d3032e2b456abb23067d29afe294/build/py3-none-linux_aarch64/_deps/ninja-build/CMakeFiles/_CMakeLTOTest-CXX/bin' make: *** [Makefile:94: all] Error 2 > -- Performing Test flag_no_deprecated -- Performing Test flag_no_deprecated - Success -- Performing Test flag_color_diag -- Performing Test flag_color_diag - Success CMake Warning at ninja-upstream/CMakeLists.txt:49 (message): re2c was not found; changes to src/*.in.cc will not affect your build. -- Looking for fork -- Looking for fork - found -- Looking for pipe -- Looking for pipe - found -- Configuring done (9.0s) -- Generating done (0.1s) -- Build files have been written to: /data/data/com.termux/files/usr/tmp/pip-install-nuu7do6s/ninja_7200d3032e2b456abb23067d29afe294/build/py3-none-linux_aarch64 *** Building project with Unix Makefiles... [ 1%] Building CXX object _deps/ninja-build/CMakeFiles/libninja-re2c.dir/src/depfile_parser.cc.o [ 2%] Building CXX object _deps/ninja-build/CMakeFiles/libninja-re2c.dir/src/lexer.cc.o [ 2%] Built target libninja-re2c [ 4%] Building CXX object _deps/ninja-build/CMakeFiles/libninja.dir/src/build_log.cc.o [ 5%] Building CXX object _deps/ninja-build/CMakeFiles/libninja.dir/src/build.cc.o [ 7%] Building CXX object _deps/ninja-build/CMakeFiles/libninja.dir/src/clean.cc.o [ 8%] Building CXX object _deps/ninja-build/CMakeFiles/libninja.dir/src/clparser.cc.o [ 10%] Building CXX object _deps/ninja-build/CMakeFiles/libninja.dir/src/dyndep.cc.o [ 11%] Building CXX object _deps/ninja-build/CMakeFiles/libninja.dir/src/dyndep_parser.cc.o [ 13%] Building CXX object _deps/ninja-build/CMakeFiles/libninja.dir/src/debug_flags.cc.o [ 14%] Building CXX object _deps/ninja-build/CMakeFiles/libninja.dir/src/deps_log.cc.o [ 16%] Building CXX object _deps/ninja-build/CMakeFiles/libninja.dir/src/disk_interface.cc.o [ 17%] Building CXX object _deps/ninja-build/CMakeFiles/libninja.dir/src/edit_distance.cc.o [ 19%] Building CXX object _deps/ninja-build/CMakeFiles/libninja.dir/src/eval_env.cc.o [ 20%] Building CXX object _deps/ninja-build/CMakeFiles/libninja.dir/src/graph.cc.o [ 22%] Building CXX object _deps/ninja-build/CMakeFiles/libninja.dir/src/graphviz.cc.o [ 23%] Building CXX object _deps/ninja-build/CMakeFiles/libninja.dir/src/json.cc.o [ 25%] Building CXX object _deps/ninja-build/CMakeFiles/libninja.dir/src/line_printer.cc.o [ 26%] Building CXX object _deps/ninja-build/CMakeFiles/libninja.dir/src/manifest_parser.cc.o [ 28%] Building CXX object _deps/ninja-build/CMakeFiles/libninja.dir/src/metrics.cc.o [ 29%] Building CXX object _deps/ninja-build/CMakeFiles/libninja.dir/src/missing_deps.cc.o [ 31%] Building CXX object _deps/ninja-build/CMakeFiles/libninja.dir/src/parser.cc.o [ 32%] Building CXX object _deps/ninja-build/CMakeFiles/libninja.dir/src/state.cc.o [ 34%] Building CXX object _deps/ninja-build/CMakeFiles/libninja.dir/src/status.cc.o [ 35%] Building CXX object _deps/ninja-build/CMakeFiles/libninja.dir/src/string_piece_util.cc.o [ 37%] Building CXX object _deps/ninja-build/CMakeFiles/libninja.dir/src/tokenpool-gnu-make.cc.o [ 38%] Building CXX object _deps/ninja-build/CMakeFiles/libninja.dir/src/util.cc.o [ 40%] Building CXX object _deps/ninja-build/CMakeFiles/libninja.dir/src/version.cc.o [ 41%] Building CXX object _deps/ninja-build/CMakeFiles/libninja.dir/src/subprocess-posix.cc.o /data/data/com.termux/files/usr/tmp/pip-install-nuu7do6s/ninja_7200d3032e2b456abb23067d29afe294/ninja-upstream/src/subprocess-posix.cc:26:10: fatal error: 'spawn.h' file not found 26 | #include <spawn.h> | ^~~~~~~~~ 1 error generated. make[2]: *** [_deps/ninja-build/CMakeFiles/libninja.dir/build.make:429: _deps/ninja-build/CMakeFiles/libninja.dir/src/subprocess-posix.cc.o] Error 1 make[1]: *** [CMakeFiles/Makefile2:193: _deps/ninja-build/CMakeFiles/libninja.dir/all] Error 2 make: *** [Makefile:136: all] Error 2 *** CMake build failed [end of output] note: This error originates from a subprocess, and is likely not a problem with pip. ERROR: Failed building wheel for ninja Building wheel for patchelf (pyproject.toml): started Building wheel for patchelf (pyproject.toml): finished with status 'error' error: subprocess-exited-with-error × Building wheel for patchelf (pyproject.toml) did not run successfully. │ exit code: 1 ╰─> [29 lines of output] *** scikit-build-core 0.11.5 using CMake 3.31.6 (wheel) *** Configuring CMake... loading initial cache file build/py3-none-linux_aarch64/CMakeInit.txt -- The C compiler identification is Clang 20.1.7 -- The CXX compiler identification is Clang 20.1.7 -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working C compiler: /data/data/com.termux/files/usr/bin/aarch64-linux-android-clang - skipped -- Detecting C compile features -- Detecting C compile features - done -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Check for working CXX compiler: /data/data/com.termux/files/usr/bin/aarch64-linux-android-clang++ - skipped -- Detecting CXX compile features -- Detecting CXX compile features - done -- Configuring done (2.6s) -- Generating done (0.0s) -- Build files have been written to: /data/data/com.termux/files/usr/tmp/pip-install-nuu7do6s/patchelf_96e1be08ef43472d93a934bd092c3537/build/py3-none-linux_aarch64 *** Building project with Unix Makefiles... [ 12%] Creating directories for 'build_patchelf' [ 25%] No download step for 'build_patchelf' [ 37%] No update step for 'build_patchelf' [ 50%] Performing patch step for 'build_patchelf' ./bootstrap.sh: 2: autoreconf: not found make[2]: *** [CMakeFiles/build_patchelf.dir/build.make:114: build_patchelf-prefix/src/build_patchelf-stamp/build_patchelf-patch] Error 127 make[1]: *** [CMakeFiles/Makefile2:87: CMakeFiles/build_patchelf.dir/all] Error 2 make: *** [Makefile:136: all] Error 2 *** CMake build failed [end of output] note: This error originates from a subprocess, and is likely not a problem with pip. ERROR: Failed building wheel for patchelf Failed to build ninja patchelf ERROR: Failed to build installable wheels for some pyproject.toml based projects (ninja, patchelf) [end of output] note: This error originates from a subprocess, and is likely not a problem with pip. error: subprocess-exited-with-error × pip subprocess to install backend dependencies did not run successfully. │ exit code: 1 ╰─> See above for output. note: This error originates from a subprocess, and is likely not a problem with pip. [end of output] note: This error originates from a subprocess, and is likely not a problem with pip. error: subprocess-exited-with-error × pip subprocess to install build dependencies did not run successfully. │ exit code: 1 ╰─> See above for output. note: This error originates from a subprocess, and is likely not a problem with pip. ~ $
07-01
安装numpy，可以尝试使用--no-build-isolation以避免使用独立的构建环境，这样可以使用Termux已经安装的依赖pipinstall numpy--no-build-isolation#如果上述方法失败，可以尝试设置以下环境变量来禁用某些特性或指定...
npm ERR! vue-backend@1.2.0 build: `node build/build.js && node build/themeExtract.js`
最新发布
10-15
这个错误发生在运行`npm run build`时，具体是执行两个脚本：`node build/build.js`和`node build/themeExtract.js`。错误可能由多种原因引起，比如： 1. 构建脚本中的JavaScript代码存在语法错误或逻辑错误。 2. ...
flutter中build.gradle仓库的配置(解决外网下载速度过慢失败的问题)
08-19
Flutter中Build.gradle仓库配置解决外网下载...同时，这篇文章也提供了一些有用的建议，例如多执行几次 Flutter run指令，或者先执行Flutter clean来清理之前build的文件。希望这篇文章能够对Flutter开发者有所帮助。
Maven工程 install和run包配置
weixin_30507481的博客
12-25 222
1、New一个Environment变量： Name：global.config.path Value：D:\490993\config; 转载于:https://www.cnblogs.com/hongming-blogs/p/8107945.html...
android--------AndroidStudio 关闭 Install Run
weixin_33862041的博客
03-09 264
2019独角兽企业重金招聘Python工程师标准>>> ...
AndroidStudio 如何关闭 Install Run
Android程序员
12-25 5322
1.打开settings 2.搜索run 3.将右边复选框取消 如图： 4.右下脚 点击 Apply 5.右下脚 点击 Ok
idea 中项目右键没有maven的run与clean与install命令选项选项
weixin_42078933的博客
04-12 8257
idea 中项目右键没有run命令选项，没有maven的clean与install选项 此项目是maven项目，试过创建一个新的maven项目也是如此。 idea 中项目右键没有run命令选项，没有maven的clean与install选项 如下图： 但是在右边有，如下图： 然后鼠标右键还是一样如下图： ...
go build和go install的区别
kwame211的博客
01-30 7165
go build 通过go build加上要编译的Go源文件名，我们即可得到一个可执行文件，默认情况下这个文件的名字为源文件名字去掉.go后缀。 $ go build hello.go $ lshello hello.go 当然我们也 可以通过-o选项来指定其他名字： $ go build -o mygo hello.go $ lsmygo hello.go 如果我们在go-ex
Android Studio禁用 install run
scuzoutao的博客
10-10 2614
最近在尝试在项目中接入腾讯的热修复方案-Tinker 在github上面把给出的官方sample clone下来之后想运行在虚拟机上，报错了，如下： Tinker does not support instant run mode, please trigger build by assembleDebug or disable instant run in 'File-&gt;Settings....
go run build/ci.go install ./cmd/geth go: errors parsing go.mod: /root/go/go-ethereum/go.mod:3: invalid go version '1.22.0': must match format 1.23 报错原因
03-16
### Go 项目中 `go.mod` 文件的 Go 版本设置不正确导致错误的原因 当在 Go 项目中遇到 `'invalid go version'` 的错误时，通常是因为 `go.mod` 文件中的 Go 版本声明与当前使用的 Go 工具链版本不符。具体来说： - 如果 `go.mod` 中指定了一个不存在或者未被支持的 Go 版本号，则会出现此错误[^1]。 - 此外，如果本地环境下的 Go 编译器版本低于或高于 `go.mod` 所需的版本范围，也可能触发该问题。 #### 解决方案 以下是几种常见的处理方式来解决此类问题： 1. **确认并更新到匹配的 Go SDK** - 查看当前系统的 Go 版本是否满足需求： ```bash go version ``` - 若发现实际运行环境中所安装的 Go 版本不符合预期，可以卸载旧版再重新部署对应的新版SDK。例如按照提示信息调整至特定版本如 `go1.17.2`[^4]: ```bash cd $GOROOT && cd .. && sudo rm -rf go wget https://dl.google.com/go/go1.17.2.linux-amd64.tar.gz tar -C /usr/local -xzf go1.17.2.linux-amd64.tar.gz ``` 2. **修正 `go.mod` 文件内的版本定义** - 修改项目的根目录下 `go.mod` 文件的第一行内容为合适的Go语言标准库发行编号。比如改为最新稳定发布的标签形式： ```text module your-module-name go 1.18 ``` - 使用命令刷新模块缓存以及同步依赖关系树结构： ```bash go clean -modcache go mod tidy ``` 3. **配置代理加速网络请求过程** 对于国内开发者而言，访问官方仓库可能较慢甚至失败，因此建议切换成更高效的镜像站点作为替代品之一[^5]： ```bash go env -w GO111MODULE=on go env -w GOPROXY=https://mirrors.aliyun.com/goproxy/,direct ``` 以上操作完成后再次尝试执行相关指令即可验证修复效果如何。 --- ### 示例代码片段展示如何检查和修改 Go 环境变量 下面提供一段脚本来帮助自动化部分流程: ```bash #!/bin/bash CURRENT_GO_VERSION=$(go version | cut -d ' ' -f3) if [[ "$CURRENT_GO_VERSION" != *"go1.18"* ]]; then echo "Your current Go version is ${CURRENT_GO_VERSION}. Please update to Go 1.18." else sed -i '' 's/^go .*/go 1.18/' ./go.mod go clean -modcache go mod tidy fi ``` 上述脚本首先获取现有的 Go 版本并与目标值对比；如果不一致就提醒升级必要性，反之则直接编辑 `go.mod` 并清理重置模块状态。 ---
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
红包 添加红包
表情包 插入表情
表情包 代码片
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值