Date: prev next · Thread: first prev next last
2012 Archives by date, by thread · List index


On Tuesday 07 of August 2012, John Smith wrote:
On Tue, Aug 7, 2012 at 8:57 AM, Stephan Bergmann <sbergman@redhat.com> 
wrote:
So I am not sure why your LO build tries to use --std=gnu++0x at all.


Stephan

It's not clang/clang++ that is executed here: it's the
ccc-analyzer/c++-analyzer. It sits in front of the compiler you use,
which is still GCC in this case. After ccc-analyzer/c++-analyzer is
done with the analysis, it passes all parameters and arguments to the
actual compiler (GCC), which then proceeds to compile the code as
usual. Im guessing your fix is trying to detect which compiler is
used, and thats still (as it is intended) GCC, but doesnt notice the
analyzer sitting in front of it (again, as intended) . Since none of
the llvm/clang parts support the __float128 type, the error is still
produced by ccc-analyzer/c++-analyzer.

 It doesn't make much sense to analyze with Clang but compile with GCC. 
Configure detects various features of the compiler and if you actually use 
GCC, certain things will not be set up properly for Clang. Use Clang for 
compiling too.

-- 
 Lubos Lunak
 l.lunak@suse.cz

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.