linux 编译gcc 12.2.0时未找到uint64_t或int64_t

guz6ccqo  于 2023-11-17  发布在  Linux
关注(0)|答案(1)|浏览(513)

我是一个初学者与Linux,我更新GCC,但我有一个错误的编译。
我用途:

../configure --prefix=/usr --disable-multilib --with-system-zlib --enable-default-pie --enable-default-ssp --enable-languages=c,c++,fortran,go,objc,obj-c++

字符串
当我运行make时,它给出以下错误:

Configuring stage 1 in ./gcc
configure: creating cache ./config.cache
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking target system type... x86_64-pc-linux-gnu
checking LIBRARY_PATH variable... ok
checking GCC_EXEC_PREFIX variable... ok
checking whether to place generated files in the source directory... no
checking whether a default linker was specified... no
checking whether a default dsymutil was specified... no
checking whether a default assembler was specified... no
checking for x86_64-pc-linux-gnu-gcc... gcc -std=gnu99
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc -std=gnu99 accepts -g... yes
checking for gcc -std=gnu99 option to accept ISO C89... none needed
checking whether we are using the GNU C++ compiler... no
checking whether g++ -std=c++11 accepts -g... no
checking for x86_64-pc-linux-gnu-gnatbind... no
checking for x86_64-pc-linux-gnu-gnatmake... no
checking whether compiler driver understands Ada... no
checking for x86_64-pc-linux-gnu-gdc... no
checking whether the D compiler works... no
checking how to run the C++ preprocessor... /lib/cpp
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... no
checking for sys/types.h... no
checking for sys/stat.h... no
checking for stdlib.h... no
checking for string.h... no
checking for memory.h... no
checking for strings.h... no
checking for inttypes.h... no
checking for stdint.h... no
checking for unistd.h... no
checking minix/config.h usability... no
checking minix/config.h presence... no
checking for minix/config.h... no
checking whether it is safe to define __EXTENSIONS__... no
checking how to run the C preprocessor... gcc -std=gnu99 -E
checking for inline... no
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... unknown
checking for _LARGE_FILES value needed for large files... unknown
checking size of ino_t... 0
checking size of dev_t... 0
checking size of void *... 0
checking size of short... 0
checking size of int... 0
checking size of long... 0
checking for long long... no
checking for int8_t... no
checking for int16_t... no
checking for int32_t... no
checking for int64_t... no
checking for unsigned long long int... no
checking for long long int... no
checking for intmax_t... no
checking for intptr_t... no
checking for uint8_t... no
checking for uint16_t... no
checking for uint32_t... no
checking for uint64_t... no
checking for uintmax_t... no
checking for uintptr_t... no
configure: error: uint64_t or int64_t not found
make[2]: *** [Makefile:4663: configure-stage1-gcc] Error 1
make[2]: Leaving directory '/usr/local/src/gcc-12.2.0/build'
make[1]: *** [Makefile:27037: stage1-bubble] Error 2
make[1]: Leaving directory '/usr/local/src/gcc-12.2.0/build'
make: *** [Makefile:1072: all] Error 2

如果有人对此有想法,我会接受的

联系我们

u4vypkhs

u4vypkhs1#

检查在尝试构建期间生成的log.log文件(可能是/gcc/js. log)。其中一个会告诉你到底哪里出错了,这并不一定是找不到uint64_t。例如,GCC 11和更高版本要求引导编译器支持C++ 11,uint64_t的测试是第一个在引导编译器的命令行中添加-std=c++11的测试。如果你的编译系统上的本地编译器是一个比4.8.3更老的GCC,你会得到uint64_t错误。

相关问题