[llvm-commits] [lld] r152269 - in /lld/trunk: ./ include/lld/Core/ include/lld/Platform/ lib/ lib/Core/ lib/Passes/ test/ tools/lld-core/

Nick Kledzik kledzik at apple.com
Fri Mar 9 09:33:06 PST 2012


I ran into this when first adding -std=c++11.  The cmake tool likes to run /usr/bin/c++ to test if options are supported.  If your /usr/bin/c++ is not clang, then it thinks you cannot use the option.  

Hopefully, there is some way to point cmake to which compiler to use.

-Nick

On Mar 9, 2012, at 9:09 AM, Evandro Menezes wrote:
> Ben,
> 
> cmake 2.8 doesn't seem to have liked it:
> 
> CMake Warning at tools/lld/CMakeLists.txt:74 (message):
>  -std=c++0x not supported.
> 
> I'll keep on investigating things on my side.
> 
> Thanks,
> 
> -- 
> Evandro Menezes          Austin, TX          emenezes at codeaurora.org
> Qualcomm Innovation Center, Inc is a member of the Code Aurora Forum
> 
> 
> On 03/08/12 18:31, Benjamin Kramer wrote:
>> 
>> On 09.03.2012, at 01:11, Chris Lattner wrote:
>> 
>>> 
>>> On Mar 8, 2012, at 3:02 PM, Evandro Menezes wrote:
>>> 
>>>> GCC 4.4.5 with "-std=c++0x", since its default is "-std=c++98":
>>>> 
>>>> tools/lld/lib/Core/Resolver.cpp:264: warning: 'auto' will change meaning
>>>> in C++0x; please remove it
>>>> 
>>>> I'm not always at liberty to use whichever compiler I want, but what IT
>>>> lets me.
>>> 
>>> Ok, build clang first, then use it to build lld.
>> 
>> GCC 4.4's c++11 support isn't great, but it supports auto and a few other things with -std=c++0x.
>> 
>> I changed the build system to use -std=c++0x instead of -std=c++11 in r152355, for compatibility with gcc<  4.7.
>> 
>> - Ben
>> 
>>> 
>>> -Chris
>>> _______________________________________________
>>> llvm-commits mailing list
>>> llvm-commits at cs.uiuc.edu
>>> http://lists.cs.uiuc.edu/mailman/listinfo/llvm-commits
>> 




More information about the llvm-commits mailing list