执行./configure报checking for g++... no错误

简介:

今天在某实验环境下编译安装软件时,执行./configure 报错(./configure是源代码安装的第一步,主要的作用是对即将安装的软件进行配置,检查当前的环境是否满足要安装软件的依赖关系),错误提示如下:

checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for g++... no
checking for c++... no
checking for gpp... no
checking for aCC... no
checking for CC... no
checking for cxx... no
checking for cc++... no
checking for cl.exe... no
checking for FCC... no
checking for KCC... no
checking for RCC... no
checking for xlC_r... no
checking for xlC... no
checking whether the C++ compiler works... no

 

原因是缺少C++编译器,yum install gcc gcc-c++即可(ubuntu系统下是apt-get install gcc g++)


本文转自 kuSorZ 51CTO博客,原文链接:http://blog.51cto.com/kusorz/1730404

相关文章
|
应用服务中间件
./configure *: No such file or directory
今天在CentOS下安装Nginx时,遇到了类似以下的问题: ./configure auto/unix: No such file or directory ./configure auto/options: No such file or directory 之前在另一台服务器上安装的时候也没有遇到此问题, 安装过程参考:CentOS6.5下Nginx1.7.4安装记录 于是网上搜索解决方案,但是搜索了很久也没有找到解决方案, 当我使用“mkdir auto/unix”之后,还是提示类似的错误,但目录名又变了。
3064 0
configure: error: libacl not found
configure: error: libacl not found
61 0
./autogen.sh: 3: gtkdocize: not found
./autogen.sh: 3: gtkdocize: not found
77 0
configure: error: cups-config not found
configure: error: cups-config not found
74 0
解决办法:configure: error: C compiler cannot create executables错误
解决办法:configure: error: C compiler cannot create executables错误
429 0
|
应用服务中间件 Linux nginx
./configure: error: C compiler cc is not found
./configure: error: C compiler cc is not found
621 0
|
Ubuntu Shell
脚本执行常见错误:build.sh: caller: not found
从Ubuntu 6.10开始,默认使用dash(theDebian Almquist Shell)而不是bash(the GNUBourne-Again Shell)但Login Shell还是bash. 原因是dash更快、更高效,而且它符合POSIX规范。Ubuntu在启动的时候会运行很多shell脚本,使用dash可以加快启动速度。
157 0

热门文章

最新文章