Hello,

I've been attempting to compile Klee against llvm-gcc-4.2-2.8-i686-linux and
llvm-2.8 but have encountered the following error. I've checked the versions
of both llvm and llvm-gcc and ensured that my path is clean of any other
llvm-gcc references.

Thanks,
Rubern

make[1]: Entering directory `/home/plunked/klee/runtime'
make[2]: Entering directory `/home/plunked/klee/runtime/Intrinsic'
make[2]: *** No rule to make target
`/home/plunked/llvm-2.8/Release+Asserts/bin/opt', needed by
`/home/plunked/klee/runtime/Intrinsic/Release+Asserts/klee_div_zero_check.bc'.
 Stop.
make[2]: *** Waiting for unfinished jobs....
make[2]: Leaving directory `/home/plunked/klee/runtime/Intrinsic'
make[1]: *** [Intrinsic/.makeall] Error 2
make[1]: *** Waiting for unfinished jobs....
make[2]: Entering directory `/home/plunked/klee/runtime/klee-libc'
make[2]: *** No rule to make target
`/home/plunked/llvm-2.8/Release+Asserts/bin/opt', needed by
`/home/plunked/klee/runtime/klee-libc/Release+Asserts/__cxa_atexit.bc'.
 Stop.
make[2]: *** Waiting for unfinished jobs....
make[2]: Leaving directory `/home/plunked/klee/runtime/klee-libc'
make[1]: *** [klee-libc/.makeall] Error 2
make[2]: Entering directory `/home/plunked/klee/runtime/Runtest'
llvm[2]: Compiling intrinsics.c for Release build (PIC)
intrinsics.c: In function ?klee_choose?:
intrinsics.c:105: warning: format ?%ld? expects type ?long int?, but
argument 3 has type ?uintptr_t?
intrinsics.c:105: warning: format ?%ld? expects type ?long int?, but
argument 4 has type ?uintptr_t?
llvm[2]: Linking Release Shared Library libkleeRuntest.so
llvm[2]: Building Release Archive Library libkleeRuntest.a
make[2]: Leaving directory `/home/plunked/klee/runtime/Runtest'
make[1]: Leaving directory `/home/plunked/klee/runtime'
make: *** [all] Error 1

-- 
I enjoy the massacre of ads. This sentence will slaughter ads without a
messy bloodbath.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
http://keeda.Stanford.EDU/pipermail/klee-dev/attachments/20110408/91797d9f/attachment.html
 

Reply via email to