Hi, in the Klee getting started you suggest that llvm-gcc must be found in the PATH, so I assume that all compilation is done using llvm-gcc but not the distribution's gcc? Or what's the sense of mixing distribution gcc (which cannot produce llvm output) with llvm? Or is my reasoning wrong?
in any case here the versions: DISTRIBUTION: gcc -v Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib64/gcc/x86_64-suse-linux/4.5/lto-wrapper Target: x86_64-suse-linux Configured with: ../configure --prefix=/usr --infodir=/usr/share/info --mandir=/usr/share/man --libdir=/usr/lib64 --libexecdir=/usr/lib64 --enable-languages=c,c++,objc,fortran,obj-c++,java,ada --enable-checking=release --with-gxx-include-dir=/usr/include/c++/4.5 --enable-ssp --disable-libssp --disable-plugin --with-bugurl=http://bugs.opensuse.org/ --with-pkgversion='SUSE Linux' --disable-libgcj --disable-libmudflap --with-slibdir=/lib64 --with-system-zlib --enable-__cxa_atexit --enable-libstdcxx-allocator=new --disable-libstdcxx-pch --enable-version-specific-runtime-libs --program-suffix=-4.5 --enable-linux-futex --without-system-libunwind --enable-gold --with-plugin-ld=/usr/bin/gold --with-arch-32=i586 --with-tune=generic --build=x86_64-suse-linux Thread model: posix gcc version 4.5.0 20100604 [gcc-4_5-branch revision 160292] (SUSE Linux) downloaded llvm-gcc: llvm-gcc -v Using built-in specs. Target: x86_64-unknown-linux-gnu Configured with: ../configure --prefix=/home/nlewycky/llvm-2.7//pre2/release/llvm-gcc4.2-2.7-x86_64-linux --disable-multilib --program-prefix=llvm- --enable-llvm=/home/nlewycky/llvm-2.7//pre2/release/llvm-2.7 --enable-languages=c,c++,fortran Thread model: posix gcc version 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2.7) On Tue, 2011-04-26 at 09:28 -0400, David Lightstone wrote: > The reason for the inquiry relates to the version of GCC provided with > the distribution. > > I had a most difficult time building with GCC 4.5.1 but was able to > build using GCC 4.4.5 > > > > I eventually concluded the GCC 4.5.1 is not compatible. > > > > Check the version of GCC used to perform the build > > > > Dave Lightstone > > > > > > From: David Lightstone [mailto:david.lightstone at prodigy.net] > Sent: Thursday, March 31, 2011 5:17 PM > To: 'arrowdodger' > Subject: RE: [klee-dev] QA guidance / advice needed > > > > > I believe I have isolated the problem to GCC 4.5.1 > > There has to be some sort of inconsistency between either the > libraries (used to build the pre-built llvm-gcc and the libraries used > with GCC 4.5.1) or expected runtime environment > > > > > > > > The means by which this was accomplished is 2 tests > > Test 1 > > Build GCC 4.5.1 (the version of GCC provided with Fedora 14) on > Fedora 14-32bit. Use it to build llvm and then KLEE > > The result is - make check fails > > > > Test 2 > > Build GCC 4.4.5 (the version of GCC provided with Fedora 13) on Fedora > 14-32bit, use it to build llvm and then KLEE > > The result is - make check succeeds > > > > Dave Lightstone > > > > > > From: arrowdodger [mailto:6yearold at gmail.com] > Sent: Thursday, March 31, 2011 12:07 PM > To: David Lightstone > Subject: Re: [klee-dev] QA guidance / advice needed > > > > > On Thu, Mar 31, 2011 at 7:42 PM, David Lightstone > <david.lightstone at prodigy.net> wrote: > > I do not particularly like building in the source directory. > > Sometimes things get overwritten (poorly written construction > scripts) during the ./configure process. > > (I think but am not certain the KLEE scripts exhibits this > behavior) > > When that happens you need to have enough sense to delete and > reinstall the source. Generally I do not have enough sense to > do that. > > > > Yes, i too. That's why i use CMake to build LLVM. Unfortunately, you > still need to use autotools build if you want KLEE. > But llvm's Makefiles were initially designed to build in-source, so it > should be OK. > > > Failure of make check provided at end > > > > > > I've looked on this. This is very strange. Sorry, but have no idea how > to fix this. > By the way, have looked for LLVM and KLEE packages in your Fedora RPM > repository? > >
