gcc:error trying to exec 'cc1obj':execvp:No such file or directory

最新推荐文章于 2024-05-23 13:33:04 发布
最新推荐文章于 2024-05-23 13:33:04 发布
阅读量4.2k 收藏 5
点赞数 4
CC 4.0 BY-SA版权
分类专栏： 学习之路上的各种小错误 文章标签： ubuntu gcc object-c 编译
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.youkuaiyun.com/HelloWorld20151118/article/details/51164509
本文记录了在Ubuntu12上搭建Objective-C环境的过程，包括遇到的问题及解决方法。文章详细介绍了如何解决编译时出现的'cc1obj'错误，并提供了安装gobjc的具体步骤。

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

前几日刚刚在Ubuntu12上搭建好object-c环境，但是命途多舛呀!花费了很久时间才搭建好的环境

但是却跑不了一个简单的helloworld，心累！

编译时报了如下错误：

gcc:error trying to exec 'cc1obj':execvp:No such file or directory!

原因：这个可能是你的gcc尚不支持cc1obj

解决方法：必须要安装gobjc

使用命令：sudo apt-get install gobjc即可

gcc: error trying to exec ‘cc1‘: execvp: No such file or directory解决方法
cjstang的博客
07-17 1万+
解决gcc: error trying to exec 'cc1': execvp: No such file or directory，无法执行的问题
tcc88xx/android配置linux内核（make tcc88xx_defconfig）时gcc:error trying to exec 'cc1':execvp:No such file or directory
ezhong0812的专栏
04-23 5222
网上搜了好多，有的说版本不一样、有的说权限不够，要chmod、试了下不行搜到一个帖子说路径不对，PATH过去就行了， 这个行了在出现错误的时候 文件/etc/bash.bashrc下export JAVA_HOME=/home/jdk1.6.0_24export ANDROID_JAVA_HOME=$JAVA_HOMEexport PATH=$JAVA_HOME/bin:$PATH文件/etc/profile下export PATH=/home/arm-2008q3/bin:$PATH在终端下 gcc -v
编译错误 gcc: error trying to exec ‘cc1plus‘: execvp: no such file or directory 解决，gcc、g++ 指定版本安装及切换
coco的专栏
05-23 1939
编译C++代码时出现 gcc: error trying to exec ‘cc1plus’: execvp: no such file or directory的错误，导致问题的原因可能是因为没有安装 g++，或是已安装的 gcc 和 g++ 版本号不一致不兼容导致。再用 gcc -v 和 g++ -v 分别检查 gcc 和 g++ 的版本号, 看版本号是否一致，若不一致，请安装同一个版本的gcc和g++。
gcc: error trying to exec ‘cc1‘: execvp: No such file or directory
一起学习 | Study Together
04-04 3384
安装gcc之后出现了执行.c文件时出现错误 gcc: error trying to exec 'cc1': execvp: No such file or directory 添加环境变量之后即可 whereis cc1 找到cc1在哪里 /usr/libexec/gcc/x86_64-redhat-linux/4.8.2/cc1 我的centos7中cc1的位置 如果找不到 用 locate cc1 找出后，复制 /usr/libexec/gcc/x86_64-redhat-linux/4.8.
gcc: error trying to exec ‘cc1plus’: execvp: 没有那个文件或目录
01-07
cc1 和 gcc 什么关系？ GCC的编译有多个阶段，每个阶段都使用不同的内部命令。特别是C，首先使用cpp进行预处理，然后编译为汇编，汇编为机器语言，然后链接在一起。 cc1是​​内部命令，用于获取预处理的C语言文件并将其转换为程序集。它是编译C的实际部分。对于C ++，有cc1plus和其他用于不同语言的内部命令。 第一，你没有安装g++ 第二，你的gcc的版本和g++版本不相符合 源码安装gcc: https://blog.youkuaiyun.com/ydyang1126/article/details/76822261 centos下g++安装包名字叫做：gcc-c++ # yum -y i
报错：gcc: error trying to exec ‘cc1plus‘: execvp: 没有那个文件或目录
sazass的博客
04-24 4244
原因可能是gcc 与g++版本不匹配 查询版本： gcc --version g++ --version 若确定版本不匹配，则开始下载对应版本的g++： sudo apt install g++-8 若电脑存有多个版本的g++版本： 可以分配优先级： sudo update-alternatives --install /usr/bin/g++ g++ /usr/bin/g++-4.8 50 sudo update-alternatives --install /usr/bin/g++ g++ /
linux离线下安装redis
weixin_43231352的博客
03-27 8159
linux下安装redis 1 reids下载 各版本下载地址:http://download.redis.io/releases/ 2 检查gcc :Redis为c语言编写，因此安装需要配置c语言编译环境gcc，查看linux是否安装了该编译环境，可以直接输入命令查看如下图所示 输入命令: gcc 如果显示:-bash: gcc: command not found # 表示没有该环境 ...
linux安装python依赖：[root@VM-16-5-centos noon]# pip3.6 install sqlalchemy WARNING: Running pip install with root privileges is generally not a good idea. Try `pip3.6 install --user` instead. Collecting sqlalchemy Downloading http://mirrors.tencentyun.com/pypi/packages/5e/50/f63ff7811a8d3367a2c7fae6095f08da20e64e09762e4da1bf05706aefb1/SQLAlchemy-1.4.54-cp36-cp36m-manylinux1_x86_64.manylinux2010_x86_64.manylinux_2_12_x86_64.manylinux_2_5_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl (1.6MB) 100% |████████████████████████████████| 1.6MB 1.8MB/s Collecting greenlet!=0.4.17; python_version >= "3" and (platform_machine == "aarch64" or (platform_machine == "ppc64le" or (platform_machine == "x86_64" or (platform_machine == "amd64" or (platform_machine == "AMD64" or (platform_machine == "win32" or platform_machine == "WIN32")))))) (from sqlalchemy) Downloading http://mirrors.tencentyun.com/pypi/packages/1e/1e/632e55a04d732c8184201238d911207682b119c35cecbb9a573a6c566731/greenlet-2.0.2.tar.gz (164kB) 100% |████████████████████████████████| 174kB 920kB/s Collecting importlib-metadata; python_version < "3.8" (from sqlalchemy) Downloading http://mirrors.tencentyun.com/pypi/packages/a0/a1/b153a0a4caf7a7e3f15c2cd56c7702e2cf3d89b1b359d1f1c5e59d68f4ce/importlib_metadata-4.8.3-py3-none-any.whl Collecting zipp>=0.5 (from importlib-metadata; python_version < "3.8"->sqlalchemy) Downloading http://mirrors.tencentyun.com/pypi/packages/bd/df/d4a4974a3e3957fd1c1fa3082366d7fff6e428ddb55f074bf64876f8e8ad/zipp-3.6.0-py3-none-any.whl Requirement already satisfied: typing-extensions>=3.6.4; python_version < "3.8" in /usr/local/lib/python3.6/site-packages (from importlib-metadata; python_version < "3.8"->sqlalchemy) Installing collected packages: greenlet, zipp, importlib-metadata, sqlalchemy Running setup.py install for greenlet ... error Complete output from command /usr/bin/python3 -u -c "import setuptools, tokenize;__file__='/tmp/pip-build-xwpa9djj/greenlet/setup.py';f=getattr(tokenize, 'open', open)(__file__);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, __file__, 'exec'))" install --record /tmp/pip-5rl6bxpe-record/install-record.txt --single-version-externally-managed --compile: running install running build running build_py creating build creating build/lib.linux-x86_64-3.6 creating build/lib.linux-x86_64-3.6/greenlet copying src/greenlet/__init__.py -> build/lib.linux-x86_64-3.6/greenlet creating build/lib.linux-x86_64-3.6/greenlet/platform copying src/greenlet/platform/__init__.py -> build/lib.linux-x86_64-3.6/greenlet/platform creating build/lib.linux-x86_64-3.6/greenlet/tests copying src/greenlet/tests/test_generator.py -> build/lib.linux-x86_64-3.6/greenlet/tests copying src/greenlet/tests/test_stack_saved.py -> build/lib.linux-x86_64-3.6/greenlet/tests copying src/greenlet/tests/test_contextvars.py -> build/lib.linux-x86_64-3.6/greenlet/tests copying src/greenlet/tests/test_greenlet.py -> build/lib.linux-x86_64-3.6/greenlet/tests copying src/greenlet/tests/test_cpp.py -> build/lib.linux-x86_64-3.6/greenlet/tests copying src/greenlet/tests/test_gc.py -> build/lib.linux-x86_64-3.6/greenlet/tests copying src/greenlet/tests/test_extension_interface.py -> build/lib.linux-x86_64-3.6/greenlet/tests copying src/greenlet/tests/test_version.py -> build/lib.linux-x86_64-3.6/greenlet/tests copying src/greenlet/tests/test_throw.py -> build/lib.linux-x86_64-3.6/greenlet/tests copying src/greenlet/tests/test_greenlet_trash.py -> build/lib.linux-x86_64-3.6/greenlet/tests copying src/greenlet/tests/test_weakref.py -> build/lib.linux-x86_64-3.6/greenlet/tests copying src/greenlet/tests/test_tracing.py -> build/lib.linux-x86_64-3.6/greenlet/tests copying src/greenlet/tests/__init__.py -> build/lib.linux-x86_64-3.6/greenlet/tests copying src/greenlet/tests/leakcheck.py -> build/lib.linux-x86_64-3.6/greenlet/tests copying src/greenlet/tests/test_generator_nested.py -> build/lib.linux-x86_64-3.6/greenlet/tests copying src/greenlet/tests/test_leaks.py -> build/lib.linux-x86_64-3.6/greenlet/tests running egg_info writing src/greenlet.egg-info/PKG-INFO writing dependency_links to src/greenlet.egg-info/dependency_links.txt writing requirements to src/greenlet.egg-info/requires.txt writing top-level names to src/greenlet.egg-info/top_level.txt reading manifest file 'src/greenlet.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' warning: no previously-included files found matching 'benchmarks/*.json' no previously-included directories found matching 'docs/_build' warning: no files found matching '*.py' under directory 'appveyor' warning: no previously-included files matching '*.pyc' found anywhere in distribution warning: no previously-included files matching '*.pyd' found anywhere in distribution warning: no previously-included files matching '*.so' found anywhere in distribution warning: no previously-included files matching '.coverage' found anywhere in distribution writing manifest file 'src/greenlet.egg-info/SOURCES.txt' copying src/greenlet/greenlet.cpp -> build/lib.linux-x86_64-3.6/greenlet copying src/greenlet/greenlet.h -> build/lib.linux-x86_64-3.6/greenlet copying src/greenlet/greenlet_allocator.hpp -> build/lib.linux-x86_64-3.6/greenlet copying src/greenlet/greenlet_compiler_compat.hpp -> build/lib.linux-x86_64-3.6/greenlet copying src/greenlet/greenlet_cpython_compat.hpp -> build/lib.linux-x86_64-3.6/greenlet copying src/greenlet/greenlet_exceptions.hpp -> build/lib.linux-x86_64-3.6/greenlet copying src/greenlet/greenlet_greenlet.hpp -> build/lib.linux-x86_64-3.6/greenlet copying src/greenlet/greenlet_internal.hpp -> build/lib.linux-x86_64-3.6/greenlet copying src/greenlet/greenlet_refs.hpp -> build/lib.linux-x86_64-3.6/greenlet copying src/greenlet/greenlet_slp_switch.hpp -> build/lib.linux-x86_64-3.6/greenlet copying src/greenlet/greenlet_thread_state.hpp -> build/lib.linux-x86_64-3.6/greenlet copying src/greenlet/greenlet_thread_state_dict_cleanup.hpp -> build/lib.linux-x86_64-3.6/greenlet copying src/greenlet/greenlet_thread_support.hpp -> build/lib.linux-x86_64-3.6/greenlet copying src/greenlet/slp_platformselect.h -> build/lib.linux-x86_64-3.6/greenlet copying src/greenlet/platform/setup_switch_x64_masm.cmd -> build/lib.linux-x86_64-3.6/greenlet/platform copying src/greenlet/platform/switch_aarch64_gcc.h -> build/lib.linux-x86_64-3.6/greenlet/platform copying src/greenlet/platform/switch_alpha_unix.h -> build/lib.linux-x86_64-3.6/greenlet/platform copying src/greenlet/platform/switch_amd64_unix.h -> build/lib.linux-x86_64-3.6/greenlet/platform copying src/greenlet/platform/switch_arm32_gcc.h -> build/lib.linux-x86_64-3.6/greenlet/platform copying src/greenlet/platform/switch_arm32_ios.h -> build/lib.linux-x86_64-3.6/greenlet/platform copying src/greenlet/platform/switch_arm64_masm.asm -> build/lib.linux-x86_64-3.6/greenlet/platform copying src/greenlet/platform/switch_arm64_masm.obj -> build/lib.linux-x86_64-3.6/greenlet/platform copying src/greenlet/platform/switch_arm64_msvc.h -> build/lib.linux-x86_64-3.6/greenlet/platform copying src/greenlet/platform/switch_csky_gcc.h -> build/lib.linux-x86_64-3.6/greenlet/platform copying src/greenlet/platform/switch_m68k_gcc.h -> build/lib.linux-x86_64-3.6/greenlet/platform copying src/greenlet/platform/switch_mips_unix.h -> build/lib.linux-x86_64-3.6/greenlet/platform copying src/greenlet/platform/switch_ppc64_aix.h -> build/lib.linux-x86_64-3.6/greenlet/platform copying src/greenlet/platform/switch_ppc64_linux.h -> build/lib.linux-x86_64-3.6/greenlet/platform copying src/greenlet/platform/switch_ppc_aix.h -> build/lib.linux-x86_64-3.6/greenlet/platform copying src/greenlet/platform/switch_ppc_linux.h -> build/lib.linux-x86_64-3.6/greenlet/platform copying src/greenlet/platform/switch_ppc_macosx.h -> build/lib.linux-x86_64-3.6/greenlet/platform copying src/greenlet/platform/switch_ppc_unix.h -> build/lib.linux-x86_64-3.6/greenlet/platform copying src/greenlet/platform/switch_riscv_unix.h -> build/lib.linux-x86_64-3.6/greenlet/platform copying src/greenlet/platform/switch_s390_unix.h -> build/lib.linux-x86_64-3.6/greenlet/platform copying src/greenlet/platform/switch_sparc_sun_gcc.h -> build/lib.linux-x86_64-3.6/greenlet/platform copying src/greenlet/platform/switch_x32_unix.h -> build/lib.linux-x86_64-3.6/greenlet/platform copying src/greenlet/platform/switch_x64_masm.asm -> build/lib.linux-x86_64-3.6/greenlet/platform copying src/greenlet/platform/switch_x64_masm.obj -> build/lib.linux-x86_64-3.6/greenlet/platform copying src/greenlet/platform/switch_x64_msvc.h -> build/lib.linux-x86_64-3.6/greenlet/platform copying src/greenlet/platform/switch_x86_msvc.h -> build/lib.linux-x86_64-3.6/greenlet/platform copying src/greenlet/platform/switch_x86_unix.h -> build/lib.linux-x86_64-3.6/greenlet/platform copying src/greenlet/tests/_test_extension.c -> build/lib.linux-x86_64-3.6/greenlet/tests copying src/greenlet/tests/_test_extension_cpp.cpp -> build/lib.linux-x86_64-3.6/greenlet/tests running build_ext building 'greenlet._greenlet' extension creating build/temp.linux-x86_64-3.6 creating build/temp.linux-x86_64-3.6/src creating build/temp.linux-x86_64-3.6/src/greenlet gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fwrapv -fPIC -I/usr/include/python3.6m -c src/greenlet/greenlet.cpp -o build/temp.linux-x86_64-3.6/src/greenlet/greenlet.o gcc: error trying to exec 'cc1plus': execvp: 没有那个文件或目录 error: command 'gcc' failed with exit status 1 ---------------------------------------- Command "/usr/bin/python3 -u -c "import setuptools, tokenize;__file__='/tmp/pip-build-xwpa9djj/greenlet/setup.py';f=getattr(tokenize, 'open', open)(__file__);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, __file__, 'exec'))" install --record /tmp/pip-5rl6bxpe-record/install-record.txt --single-version-externally-managed --compile" failed with error code 1 in /tmp/pip-build-xwpa9djj/greenlet/ [root@VM-16-5-centos noon]# python3.6 getSalerInfo3.py Traceback (most recent call last): File "getSalerInfo3.py", line 13, in <module> from sqlalchemy import exc, create_engine, text ModuleNotFoundError: No module named 'sqlalchemy' [root@VM-16-5-centos noon]#报错
06-19
若出现`cc1plus: fatal error: Python.h: No such file or directory`： ```bash sudo yum install python36-devel # 确认已安装 export CFLAGS="-I/usr/include/python3.6m" # 手动指定头文件路径 ``` #### 3. ...
linux centos7 安装gc,CentOS 7.0 系统安装gcc/g++ 7.3
weixin_39675679的博客
05-16 1231
最近因为项目需要，需要使用 C++ 17 的一些特性，CentOS 自带的 gcc/g++ 版本是 4.8，如果没有安装，可以通过 yum 命令安装，安装命令如下：# 安装gccyum install gcc#安装 g++yum install gcc-c++由于 gcc/g++ 4.8 完全支持 C++ 11，支持部分 C++ 14，不支持 C++ 17，而完全支持 C++ 17 的是 g++ ...
Ubuntu11.10（32位）编译android常见错误（30种）
08-22 1288
开始正式编译，在源码目录下make即可。 make 我完全不知道跑了个啥，只知道超级卡。完成后产生的out文件夹有3.9G。 镜像生成在out/target/product/generic下：android源码编译后得到system.img,ramdisk.img,userdata.img映像文件。其中， ramdisk.img是emulator的文件系统，system.img包括了主要的包
error trying to exec 'cc1': execvp: No such file or directory
weixin_40700617的博客
08-08 1万+
出现这种情况一般是没有将交叉编译工具链的路径添加到环境变量中 解决办法：打开/etc/profile文件 将交叉编译工具链的路径添加进去，保存退出 然后执行 source /etc/profile 注意一定要是bin目录，如下图我的交叉编译工具链是在bin目录的下一级目录，如果不是写bin目录的话问题是不会解决的 ...
编译出错提示 error trying to exec 'cc1': execvp: No such file or directory
热门推荐
IamGooday的专栏
09-06 2万+
在我的Ubuntu系统中，编译程序出现此提示。 网上说法一大堆，或者编译器坏了，或者与其他软件冲突之类。似乎都不符合我的情况。于是自查， 查询后获知其实我的编译器已经有了这个cc1， /usr/local/arm/4.4.1/libexec/gcc/arm-none
arm-eabi-gcc: error trying to exec 'cc1': execvp: No such file or directory 问题的解决
myZero1986的专栏
04-23 4861
今天在做ubuntu10.04环境下ndk测试时，老是出现如下问题： root@zero-desktop:~/ndk/android-ndk-r4b/samples/hello-jni/jni# ndk-build  Gdbserver      : [arm-eabi-4.4.0] /root/ndk/android-ndk-r4b/samples/hello-jni/libs/armeab
error trying to exec 'cc1' 错误修复
Run for the future!
12-11 3292
error trying to exec cc1错误查找错误提示：error trying to exec cc1: execvp: No such file or directory解答：1）所使用的GCC是不是合适的；2）查看自己的PATH路径是否加入了一些存在冲突的路径；
离线安装gcc----解决error trying to exec ‘cc1’: execvp: 没有该文件或目录的错误
影帝
05-21 5556
centos中安装gcc后编译程序出现提示：gcc: error trying to exec 'cc1': execvp: 没有该文件或目录的错误 以前在ubuntu或者mint中都是执行sudo apt-get install build-essential来解决，现在找到一种手动安装的方法。 还需要安装如下几个安装包： 【1】rpm包下载地址：http://www.rpmfind.net/linux/RPM/index.html 【2】解压centos镜像得到packages，里面包含系统.
gcc: error trying to exec 'cc1plus': execvp: 没有那个文件或目录 error: command 'gcc' failed with exit status
zoe的博客
08-08 2415
根据网上查找的答案，安装了相关的依赖包，问题还是存在： 网上答案： yum install gcc libffi-devel python-devel openssl-devel 因为要安装的pyltp，底层的语言是C++,所以还需要安装一个依赖包： yum install gcc-c++  ...
gcc: error trying to exec 'cc1': execvp: No such file or directory
最新发布
08-08
我们遇到了gcc编译错误：gcc: error trying to exec 'cc1': execvp: No such file or directory 这个错误通常表示gcc在尝试调用其内部组件cc1（负责C语言编译的组件）时找不到该文件。 可能的原因和解决方案如下：...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值