Autotools的“配置”脚本始终会立即消耗掉我所有的4GB RAM，并使我的计算机挂起

Question

每当我通过运行configure命令运行GNU-Autotools的./configure脚本时。它在5秒钟内很快很快消耗了我所有的RAM（4GB），然后将计算机挂起。我使用Linux系统，并使用不同的GNU源程序包测试了此问题，结果是相同的。您可以在下面看到运行configure的示例：

当过程到达“正在检查BSD或MS兼容的名称列表（nm）...”时，我通过CTRL + C中断了该过程。

我的配置日志：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中断了抢救我的计算机的过程。

Answer 1

首先，我重新安装了binutils以解决nm的问题，但是没有任何改变，然后我删除了binutils及其相关性，再次安装了它，现在一切正常。

我没有发现nm发生了什么，但我只是发现这是配置过程中的问题。

我希望这个答案也能帮助其他人。