All I am working in a Fedora 14 environment (both 32bit and 64 bit implementations)
On Fedora 13 (both 32bit and 64bit) I was able to build Klee successfully (make check succeeds) using the pre-build llvm gcc compilers; llvm-gcc-4.2-2.7-i686-linux.gz (32 bit environment) or llvm-gcc4.2-2.7-x86_64-linux.tar.bz2 (64 bit environment) On Fedora 14 (both 32bit and 64bit) I was NOT able to build Klee successfully (ie make check failed) using either of the pre-built llvm gcc compilers I was able, however, to build llvm-gcc-4.2 in all environments (32 and 64 bit, Fedora 13 and 14); use them to build the llvm tool chain; and use both the tool chain and the llvm-gcc to build Klee successfully (ie make check succeeds) This being an anomaly which I suspect warrants better characterization (I just don't know what will be useful) That is it leads me to believe that I have ether (1) a build logistics problem. ie what I think I built, and what I actually built are different ( maybe configuration selections for llvm and/or klee wrong; or using marginally compatible host tools; or wrong compilers, host vs pre-built used in the built) (2) llvm-gcc-4.2-2.7-i686-linux.gz (32 bit environment) or llvm-gcc4.2-2.7-x86_64-linux.tar.bz2 (64 bit environment) are not entirely compatible with Fedora 14 I suspect that I will need to characterize things a bit, but really don't how best to approach things. My initial guess is (standard configuration audit) (1) Confirm the configuration and processor target for each of the (LLVM and KLEE) libraries and executablies which were built (2) Characterize host tools used in the build (3) the libraries which were used to prepare a build of both llvm and klee Dave Lightstone
