Hi Folks, I'm having some difficulties getting LLVM to build and work correctly on CENTOS 5.3. This is basically tracked down easily enough to CENTOS using GCC 4.1.x by default, which is known-buggy and known not to work with LLVM -- I was getting the well-known problem with aborts due to a non-empty symbol table. I have installed the gcc43 package via yum (I'm trying to stick to known packages because I need to roll this out at some point), which installs a gcc43 executable. Is there any configure magic available that will make it possible to get the LLVM build system to pick up gcc43 rather than the default gcc? Symlinking it didn't work, because I suspect it was still picking up the old libraries and headers. This is preferable to requiring users to significantly hack their environment. Thanks, Sarah Thompson NASA Ames
On Apr 28, 2009, at 3:45 PMPDT, Sarah Thompson wrote:> Hi Folks, > > I'm having some difficulties getting LLVM to build and work correctly > on CENTOS 5.3. This is basically tracked down easily enough to CENTOS > using GCC 4.1.x by default, which is known-buggy and known not to work > with LLVM -- I was getting the well-known problem with aborts due to a > non-empty symbol table. I have installed the gcc43 package via yum > (I'm trying to stick to known packages because I need to roll this out > at some point), which installs a gcc43 executable. Is there any > configure magic available that will make it possible to get the LLVM > build system to pick up gcc43 rather than the default gcc? Symlinking > it didn't work, because I suspect it was still picking up the old > libraries and headers. This is preferable to requiring users to > significantly hack their environment.I haven't tried it, but comments in 'configure' suggest the CC and CXX environment variables should work.
Am trying that currently... looks OK so far. I'll post results when I've run my regression tests. Thanks! [s] On Apr 28, 2009, at 4:01 PM, Dale Johannesen wrote:> > On Apr 28, 2009, at 3:45 PMPDT, Sarah Thompson wrote: > >> Hi Folks, >> >> I'm having some difficulties getting LLVM to build and work correctly >> on CENTOS 5.3. This is basically tracked down easily enough to CENTOS >> using GCC 4.1.x by default, which is known-buggy and known not to >> work >> with LLVM -- I was getting the well-known problem with aborts due >> to a >> non-empty symbol table. I have installed the gcc43 package via yum >> (I'm trying to stick to known packages because I need to roll this >> out >> at some point), which installs a gcc43 executable. Is there any >> configure magic available that will make it possible to get the LLVM >> build system to pick up gcc43 rather than the default gcc? Symlinking >> it didn't work, because I suspect it was still picking up the old >> libraries and headers. This is preferable to requiring users to >> significantly hack their environment. > > I haven't tried it, but comments in 'configure' suggest the CC and CXX > environment variables should work. > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
OK, that got much further, but I'm now seeing another problem which may (or may not) be related. Building my own code (my model checker), it builds libraries fine, then within tools (I'm using a fairly standard LLVM build environment here), I am seeing the error *** llvm-config doesn't exist - rebuilding it followed by a make: Entering an unknown directory which is complaining about .../tools//bin/llvm-config This didn't happen when I was building with gcc 4.1.x, though of course, my code didn't actually work when compiled with that compiler. [s] On Apr 28, 2009, at 4:01 PM, Dale Johannesen wrote:> > On Apr 28, 2009, at 3:45 PMPDT, Sarah Thompson wrote: > >> Hi Folks, >> >> I'm having some difficulties getting LLVM to build and work correctly >> on CENTOS 5.3. This is basically tracked down easily enough to CENTOS >> using GCC 4.1.x by default, which is known-buggy and known not to >> work >> with LLVM -- I was getting the well-known problem with aborts due >> to a >> non-empty symbol table. I have installed the gcc43 package via yum >> (I'm trying to stick to known packages because I need to roll this >> out >> at some point), which installs a gcc43 executable. Is there any >> configure magic available that will make it possible to get the LLVM >> build system to pick up gcc43 rather than the default gcc? Symlinking >> it didn't work, because I suspect it was still picking up the old >> libraries and headers. This is preferable to requiring users to >> significantly hack their environment. > > I haven't tried it, but comments in 'configure' suggest the CC and CXX > environment variables should work. > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev