Discussion:
klee-uclibc built with clang-3.3 problem, thx!
(too old to reply)
peterlee
2014-08-08 17:19:25 UTC
Permalink
Dear All

Right now I am using clang/llvm-3.3 to compile the klee-uclibc in the
32-bits environment.

I grasped the klee-uclibc with the following command:

git clone --depth 1 --branch klee_0_9_29
https://github.com/klee/klee-uclibc.git

Then I used the following command to configure the klee-uclibc:

./configure --make-llvm-lib --with-llvm-config=/path/to/llvm-config

but I always met the following problems:

INFO:Disabling assertions
INFO:Configuring for Debug build
INFO:Configuring for LLVM bitcode archive
INFO:Using llvm-config
at.../home/gli/peng/klover-32/vendor/llvm-3.3/build32
Traceback (most recent call last):
File "./configure", line 622, in <module>
main(sys.argv[1:])
File "./configure", line 122, in main
handleLLVMConfig(pargs, cc)
File "./configure", line 364, in handleLLVMConfig
(retCode, output) = runTool([llvmConfigTool, '--bindir'])
File "./configure", line 220, in runTool
output = subprocess.check_output(cmd, stderr=subprocess.STDOUT)
File
"/home/gli/peng/Software/python-inst/lib/python2.7/subprocess.py", line
566, in check_output
process = Popen(stdout=PIPE, *popenargs, **kwargs)
File
"/home/gli/peng/Software/python-inst/lib/python2.7/subprocess.py", line
710, in __init__
errread, errwrite)
File
"/home/gli/peng/Software/python-inst/lib/python2.7/subprocess.py", line
1327, in _execute_child
raise child_exception
OSError: [Errno 13] Permission denied

Any help is highly appreciated!

Regards
Peng
Daniel Liew
2014-08-08 21:09:00 UTC
Permalink
Post by peterlee
./configure --make-llvm-lib --with-llvm-config=/path/to/llvm-config
You are replacing ``/path/to/llvm-config`` with the actual path to
llvm-config right?

You don't need to specify this argument if llvm-config is in your path.
Post by peterlee
"/home/gli/peng/Software/python-inst/lib/python2.7/subprocess.py", line
1327, in _execute_child
raise child_exception
OSError: [Errno 13] Permission denied
The configure script can't execute llvm-config. You need to fix this.
If you pass ``--log-level debug`` you may get more clues.

Loading...