Hi Vijay, You are definitely not alone in thinking installation of KLEE is pain.
I just addressed a major pain point for new (..and old, sometimes I make this mistake) users of KLEE where llvm-gcc was not in the PATH variable at LLVM configure time. This was very confusing and completely unnecessary. The commit [1] is not yet merged (but hopefully will be soon) changes KLEE's configure behaviour so that it will try to detect clang/llvm-gcc when configuring KLEE and completely ignores what was detected at LLVM configure time. The other issues you encountered relate to uclibc. In my opinion uclibc has been broken for a long time and we are only just starting to fix it. There is now a KLEE uclibc repository [2] but work on that isn't quite complete yet. As Cristian mentioned a VM is possible but they do take up a lot of space. One thing that could easy the pain would be to distribute the VM using torrents provided there are enough volunteers... As for building packages, something like the OpenSUSE build service might be what we are after which can allow us to build packages for several distros/architectures for free. I used once a while ago and it seemed pretty good. [1] https://github.com/ccadar/klee/pull/65 [2] https://github.com/ccadar/klee-uclibc/tree/klee_monolithic [3] https://build.opensuse.org/ Thanks, Dan Liew. _______________________________________________ klee-dev mailing list [email protected] https://mailman.ic.ac.uk/mailman/listinfo/klee-dev
