[cfe-dev] [3.5 Release] Release Candidate 1 Sources and Binaries Available

[Ben Pope]

On Wednesday, July 30, 2014 02:07 AM, Larry Evans wrote:
> On 07/29/2014 09:16 AM, Ben Pope wrote:
>>
>> My guess is you're building with g++-4.9, so:
>>
>> CC=gcc-4.8 CXX=g++-4.8 ./configure <stuff>
>>
>> Ben
> Yes:
>
> ~/dwnlds/llvm/3.5rc1 $ which gcc
> /usr/local/bin/gcc
> ~/dwnlds/llvm/3.5rc1 $ gcc --version
> gcc (GCC) 4.9.0
> Copyright (C) 2014 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions.  There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
>
> ~/dwnlds/llvm/3.5rc1 $ /usr/bin/gcc --version
> gcc (Ubuntu 4.8.2-19ubuntu1) 4.8.2
> Copyright (C) 2013 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions.  There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
>
> ~/dwnlds/llvm/3.5rc1 $
>
> So, using the gcc defined in /usr/local/bin, caused some object
> fields to require the GLIBCXX in /usr/local/lib64; however,
> the clang Makefiles only made provision for looking in /usr/lib64?
> And changing the CC to /usr/bin/gcc would then cause the object
> files to require the GLIBCXX in /usr/lib64, and that's what
> the clang Makefiles expect?  Is that how it works?
> Just trying understand what's going on :(
>
> Thank for the help.

Lets try an experiment: with g++-4.9, compile a simple program that uses 
libstdc++.

g++ hello.cpp
./a.out
ldd a.out | grep libstdc++
chrpath -l a.out

ldd your_built_clang | grep libstdc++
chrpath -l your_built_clang

Let me know your findings.

Ben