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


https://bugs.freedesktop.org/show_bug.cgi?id=71043

--- Comment #10 from Tor Lillqvist <tml@iki.fi> ---
I, and several other people, compile LibreOffice using Clang all the time, both
on Linux (where Clang so far is not mainstream, I guess) and on OS X (for OS X
itself and cross-compiling for iOS) (where Clang *is* mainstream, no gcc
available any more at all). This has been done for over a year at least. So it 
isn't as if it would be anything new to compile LibrOffice using Clang.

The configure.ac has logic to decide whether to use the -fno-enforce-eh-specs
option or not, and so far it has worked. So either your version of Clang is in
some way then odd and the configure.ac tests break down, or you are telling it
to use Clang in some wrong way. What does your autogen.input look like? For me,
to use Clang (on Linux), I simply add CC=clang and CXX=clang++ lines to
autogen.input.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

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.