Discussion:
compile error with klee
(too old to reply)
Michael Eßer
2014-06-24 17:41:10 UTC
Permalink
<mailto:klee-dev-AQ/***@public.gmane.org>When i compile klee I get the following
error message:
make[2]: *** Keine Regel vorhanden, um das Target
»/home/michael/Downloads/klee/runtime/Intrinsic/Release+Asserts/klee_div_zero_check.ll«,
benötigt von
»/home/michael/Downloads/klee/runtime/Intrinsic/Release+Asserts/klee_div_zero_check.bc«,
zu erstellen. Schluss.


I can't see any llvm version conflicts because I set all seperate in the
../configure call:
./configure --with-llvmsrc=../llvm-2.9
--with-llvmobj=../llvm-2.9.build --with-stp=../stp-build
--with-llvmcc=../llvm-gcc-4.2-2.9-i686-linux/bin/llvm-gcc
--with-llvmcxx=../llvm-gcc-4.2-2.9-i686-linux/bin/llvm-c++
--enable-posix-runtime

Here's the ./configure output:
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking target system type... i686-pc-linux-gnu
checking type of operating system we're going to host on...
checking llvm source dir... /home/michael/Downloads/llvm-2.9
checking llvm obj dir... /home/michael/Downloads/llvm-2.9.build
checking llvm package version... 2.9
checking llvm version major... 2
checking llvm version minor... 9
checking llvm is release version... 1
checking llvm build mode... Release
checking LLVM Bitcode compiler... Using user supplied LLVM bitcode
compilers.
Using C llvm compiler : ../llvm-gcc-4.2-2.9-i686-linux/bin/llvm-gcc
Using C++ llvm compiler : ../llvm-gcc-4.2-2.9-i686-linux/bin/llvm-c++
checking C LLVM Bitcode compiler works... Success
checking CXX LLVM Bitcode compiler works... Success
checking uclibc... no
checking POSIX runtime... yes
checking runtime configuration... Release+Asserts
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 how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking sys/acl.h usability... no
checking sys/acl.h presence... no
checking for sys/acl.h... no
checking for cap_get_proc in -lcap... yes
checking sys/capability.h usability... yes
checking sys/capability.h presence... yes
checking for sys/capability.h... yes
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking how to run the C++ preprocessor... g++ -E
checking selinux/selinux.h usability... no
checking selinux/selinux.h presence... no
checking for selinux/selinux.h... no
checking for library containing mallinfo... none required
checking stp/c_interface.h usability... yes
checking stp/c_interface.h presence... yes
checking for stp/c_interface.h... yes
checking for vc_setInterfaceFlags in -lstp... yes
Using old STP
configure: creating ./config.status
config.status: creating Makefile.config
config.status: creating docs/doxygen.cfg
config.status: creating include/klee/Config/config.h
config.status: include/klee/Config/config.h is unchanged
config.status: executing setup commands
config.status: executing Makefile commands
config.status: executing Makefile.common commands
config.status: executing lib/Makefile commands
config.status: executing runtime/Makefile commands
config.status: executing test/Makefile commands
config.status: executing test/Makefile.tests commands
config.status: executing tools/Makefile commands
config.status: executing unittests/Makefile commands
Michael Esser
2014-06-25 12:26:42 UTC
Permalink
Hi,

there was the wron path to llvm-gcc.

Thanks
Post by Michael Eßer
make[2]: *** Keine Regel vorhanden, um das Target
»/home/michael/Downloads/klee/runtime/Intrinsic/Release+Asserts/klee_div_zero_check.ll«,
benötigt von
»/home/michael/Downloads/klee/runtime/Intrinsic/Release+Asserts/klee_div_zero_check.bc«,
zu erstellen. Schluss.
I can't see any llvm version conflicts because I set all seperate in the
./configure --with-llvmsrc=../llvm-2.9 --with-llvmobj=../llvm-2.9.build
--with-stp=../stp-build
--with-llvmcc=../llvm-gcc-4.2-2.9-i686-linux/bin/llvm-gcc
--with-llvmcxx=../llvm-gcc-4.2-2.9-i686-linux/bin/llvm-c++
--enable-posix-runtime
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking target system type... i686-pc-linux-gnu
checking type of operating system we're going to host on...
checking llvm source dir... /home/michael/Downloads/llvm-2.9
checking llvm obj dir... /home/michael/Downloads/llvm-2.9.build
checking llvm package version... 2.9
checking llvm version major... 2
checking llvm version minor... 9
checking llvm is release version... 1
checking llvm build mode... Release
checking LLVM Bitcode compiler... Using user supplied LLVM bitcode
compilers.
Using C llvm compiler : ../llvm-gcc-4.2-2.9-i686-linux/bin/llvm-gcc
Using C++ llvm compiler : ../llvm-gcc-4.2-2.9-i686-linux/bin/llvm-c++
checking C LLVM Bitcode compiler works... Success
checking CXX LLVM Bitcode compiler works... Success
checking uclibc... no
checking POSIX runtime... yes
checking runtime configuration... Release+Asserts
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 how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking sys/acl.h usability... no
checking sys/acl.h presence... no
checking for sys/acl.h... no
checking for cap_get_proc in -lcap... yes
checking sys/capability.h usability... yes
checking sys/capability.h presence... yes
checking for sys/capability.h... yes
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking how to run the C++ preprocessor... g++ -E
checking selinux/selinux.h usability... no
checking selinux/selinux.h presence... no
checking for selinux/selinux.h... no
checking for library containing mallinfo... none required
checking stp/c_interface.h usability... yes
checking stp/c_interface.h presence... yes
checking for stp/c_interface.h... yes
checking for vc_setInterfaceFlags in -lstp... yes
Using old STP
configure: creating ./config.status
config.status: creating Makefile.config
config.status: creating docs/doxygen.cfg
config.status: creating include/klee/Config/config.h
config.status: include/klee/Config/config.h is unchanged
config.status: executing setup commands
config.status: executing Makefile commands
config.status: executing Makefile.common commands
config.status: executing lib/Makefile commands
config.status: executing runtime/Makefile commands
config.status: executing test/Makefile commands
config.status: executing test/Makefile.tests commands
config.status: executing tools/Makefile commands
config.status: executing unittests/Makefile commands
Loading...