Hi Martin, I'm starting to look at getting KLEE up to scratch (it's going to be a long process) this week and one of the things on my to do list is uclibc. The old version would not compile on my machine due to changes in my kernel headers.
I see there is now a klee-uclibc repository [1] but I'm not sure what work has and has not been done, there seem to be quite a few branches. Seeing as you seem to have done the most work here could you explain to me (and the rest of the KLEE community -- note I've CC'ed the mailing list) what each branch is for and summarise what work you have done (I don't want to duplicate your efforts). Would you also be able to recommend one or more starting points for uclibc versions? I'd like to get the old uclibc (monolithic) up and running on my machine with llvm-gcc so I can fix some outstanding issues on llvm2.9, then I'd like start experimenting with LLVM3.3 so I can see what needs working on (I'm very keen for us to move to clang... I'm not a fan of llvm-gcc). We also ideally need some sort of strategy for merging with upstream uclibc... I presume the branches with version numbers are official releases... should we branch off those?.. i.e. 0_9_28_klee 0.9.33_klee Thanks, Dan Liew. [1] https://github.com/ccadar/klee-uclibc _______________________________________________ klee-dev mailing list [email protected] https://mailman.ic.ac.uk/mailman/listinfo/klee-dev
