[LLVMdev] Building LLVM 2.5 on CENTOS 5.3

[Christian Sayer]

Hello Sarah,
just to give you a hint of something that might happen:
I am in the same situation on suse linux with gcc 4.1 as the system's compiler,
so I built 4.3 as an alternative from sources. Everything went well for
quite a long time, but eventually my program would crash at runtime
on something as simple as passing a std::string by value or reference.
It turned out that I had to use LD_LIBRARY_PATH to make it load
libstdc++.so of the 4.3 installation. The nasty thing is that this seems to
cause problems very rarely.
Just in case you notice that your application runs fine in the virtual machine
but not anymore once rolled out...

Regards,
Christian

 --
  Christian SAYER


> -----Original Message-----
> From: llvmdev-bounces at cs.uiuc.edu
> [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Sarah Thompson
> Sent: Wednesday, April 29, 2009 7:43 AM
> To: LLVM Developers Mailing List
> Subject: Re: [LLVMdev] Building LLVM 2.5 on CENTOS 5.3
>
> Just to give closure here, I eventually gave up, built an Ubuntu 9
> VMWare image which uses gcc 4.3.2 by default, installed Eclipse
> Ganymede and various other tools, then built LLVM 2.5 and my own code.
> It all ran fine. There is clearly something broken in the CentOS gcc43
> package. Definitely one to avoid.
>
> [s]
>
> On Apr 28, 2009, at 5:40 PM, Sarah Thompson wrote:
>
> > (My script does both of those -- the debug build worked (I
> think), but
> > the release build fails)
> >
> > [s]
> >
> > On Apr 28, 2009, at 5:19 PM, Bill Wendling wrote:
> >
> >> We build debug by default. You will have to add
> ENABLE_OPTIMIZED=1 on
> >> the "make" command line or --enable-optimized during configuration.
> >>
> >> -bw
> >>
> >> On Tue, Apr 28, 2009 at 5:12 PM, Sarah Thompson
> <sarah at findatlantis.com
> >>> wrote:
> >>> Hmm... looks like my LLVM build script only built debug
> versions of
> >>> the tools, not release versions. I'm investigating, I
> didn't change
> >>> anything that should have caused that.
> >>>
> >>> [s]
> >>>
> >>> On Apr 28, 2009, at 4:56 PM, Bill Wendling wrote:
> >>>
> >>>> On Tue, Apr 28, 2009 at 4:43 PM, Sarah Thompson
> <sarah at findatlantis.com
> >>>>> wrote:
> >>>>> 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.
> >>>>>
> >>>> That's odd. It's the "/bin/" in there that make is complaining
> >>>> about.
> >>>> I'm not sure why a different compiler would cause it to change
> >>>> behavior. Does adding "VERBOSE=1" to the "make" command shed any
> >>>> light
> >>>> on what's going wrong here?
> >>>>
> >>>> -bw
> >>>>

--

CONFIDENTIAL NOTICE: The contents of this message, including any attachments, are confidential and are intended solely for the use of the person or entity to whom the message was addressed. If you are not the intended recipient of this message, please be advised that any dissemination, distribution, or use of the contents of this message is strictly prohibited. If you received this message in error, please notify the sender. Please also permanently delete all copies of the original message and any attached documentation. Thank you.