每当我通过运行configure
命令运行的GNU自动工具的./configure
脚本。它烧到5秒钟内我所有的RAM(4GB)非常快的,然后立即挂掉我的电脑。我使用的Linux系统,我测试了这个问题,不同的GNU源码包,结果是一样的。你可以看到下面运行configure
的例子:
我打破通过CTRL + C的处理中,在处理到达“检查BSD-或MS-兼容名称列表器(纳米)...”。
我的config.log:http://ashavahishta.persiangig.com/document/Text/config.log
$ ./configure
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 whether make supports nested variables... yes
checking whether UID '1000' is supported by ustar format... yes
checking whether GID '1000' is supported by ustar format... yes
checking how to create a ustar tar archive... gnutar
checking whether to enable maintainer-specific portions of Makefiles... yes
checking whether make supports nested variables... (cached) yes
checking for gcc... gcc 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 accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether gcc understands -c and -o together... yes
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking whether make sets $(MAKE)... (cached) yes
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... no
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for gcc... gcc
checking whether we are using the GNU Objective C compiler... yes
checking whether gcc accepts -g... yes
checking dependency style of gcc... gcc3
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking how to print strings... printf
checking for a sed that does not truncate output... /bin/sed
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for fgrep... /bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)...
所有checking
后,这里的内存成品和我通过CTRL + C破解过程营救我的电脑。
首先,我重新安装了binutils
解决与nm
但没有什么问题没有改变,那么我删除binutils
和它的依赖,我重新安装了它,现在一切都运行完美。
我没有找到发生了什么事约nm
但我发现,是在配置过程中的问题。
我希望这个答案帮助其他人了。