如何解决KLEE安装错误?与“subprocess.py”相关

时间:2015-06-05 14:13:15

标签: python klee

我正在使用http://klee.github.io/getting-started/

中的以下说明安装KLEE

我来到了第04步:./ configure --make-llvm-lib

但是,当我运行该命令时,会出现以下错误:


    INFO:Disabling assertions
    INFO:Configuring for Debug build
    INFO:Configuring for LLVM bitcode archive
    INFO:Using llvm-config at.../root/exp/llvm-2.9/Release+Asserts/bin/llvm-config
    INFO:Using llvm tool dir.../root/exp/llvm-2.9/Release+Asserts/bin
    INFO:Found "/root/exp/llvm-2.9/Release+Asserts/bin/llvm-objdump".
    INFO:Found "/root/exp/llvm-2.9/Release+Asserts/bin/llvm-link".
    INFO:Found "/root/exp/llvm-2.9/Release+Asserts/bin/llvm-ar".
    INFO:Found "/root/exp/llvm-2.9/Release+Asserts/bin/llvm-nm".
    INFO:Searching for LLVM Bitcode compiler...
    INFO:Found llvm-gcc in PATH.../root/exp/llvm-gcc-4.2-2.9-i686-linux/bin/llvm-gcc
    INFO:Testing LLVM Bitcode compiler.../root/exp/llvm-gcc-4.2-2.9-i686-linux/bin/llvm-gcc
    Traceback (most recent call last):
      File "./configure", line 622, in 
        main(sys.argv[1:])
      File "./configure", line 122, in main
        handleLLVMConfig(pargs, cc)
      File "./configure", line 400, in handleLLVMConfig
        cc = findBitCodeCompiler(llvmToolDir)
      File "./configure", line 482, in findBitCodeCompiler
        if testBitCodeCompiler(llvmgcc, llvmToolDir):
      File "./configure", line 545, in testBitCodeCompiler
        '-o', bitCodeFileName]
      File "./configure", line 220, in runTool
        output = subprocess.check_output(cmd, stderr=subprocess.STDOUT)
      File "/usr/lib/python2.7/subprocess.py", line 568, in check_output
        process = Popen(stdout=PIPE, *popenargs, **kwargs)
      File "/usr/lib/python2.7/subprocess.py", line 711, in __init__
        errread, errwrite)
      File "/usr/lib/python2.7/subprocess.py", line 1308, in _execute_child
        raise child_exception
    OSError: [Errno 2] No such file or directory

看起来缺少一个文件。但是,我不知道任何可能使用的文件,因为我对KLEE不熟悉。

我正在使用Ubuntu 13.04,并已成功执行了前面的步骤。我非常感谢任何建议。谢谢!

1 个答案:

答案 0 :(得分:1)

问题解决了。由于使用的llvm-gcc版本不正确(x86_64而不是i386错误)