[klee-dev] Arch linux: Cannot build Klee , stuck with "Unable to link with libstp"

[Daniel Liew]

Current upsteam KLEE has the following order of precedence in the
configure script for detecting the bitcode compiler.

1.  Clang inside your LLVM build directory
2.  llvm-gcc in your PATH environment
3.  clang in your PATH environment

If llvm-gcc is in your PATH and you didn't build clang inside your
llvm build directory then llvm-gcc should be picked up. If it really
isn't working for some bizarre reason you can force the bitcode
compiler by doing

$ ./configure --with-llvmcc=/path/to/llvm-gcc
--with-llvmcxx=/path/to/llvm-g++ <other configure options>

> The LLVM2.9 bin path is in my PATH.  But it *does not* have clang++ or clang  as shown below.  The original klee repo configure script apparently does not check (and use?) clang*  that's why I didn't get such errors before.

I don't know what you mean by "original klee repo".

> prime Wed Feb 12:08:35:58 (4270)
> ~/Src/Devel/KLEE/llvm-gcc4.2-2.9-x86_64-linux/bin
> $ ls
> llvm-c++*       x86_64-unknown-linux-gnu-cpp-4.2.1*
> llvm-cpp*       x86_64-unknown-linux-gnu-gcc-4.2.1*
> llvm-g++*       x86_64-unknown-linux-gnu-llvm-c++*
> llvm-gcc*       x86_64-unknown-linux-gnu-llvm-cpp*
> llvm-gccbug*    x86_64-unknown-linux-gnu-llvm-g++*
> llvm-gcov*      x86_64-unknown-linux-gnu-llvm-gcc*
> llvm-gfortran*  x86_64-unknown-linux-gnu-llvm-gfortran*

This does not actually prove that llvm-gcc is your path...you should
do something like

$ which llvm-gcc
/home/dsl11/dev/klee/llvm-gcc4.2-2.9-x86_64-linux/bin/llvm-gcc

to check. The fact that KLEE's configure script picked up clang as the
bitcode compiler would indicate (unless there's a bug in the configure
script) that llvm-gcc is not in your PATH when you ran configure.


Thanks,
Dan.