On 2014-09-09 19:50, [email protected] wrote:
Il 09/09/2014 05:44, Robert Xu ha scritto:
* Yes, we have switched to LLVM/Clang as our default compiler for
2015.0. You don't have to use it; simply set CC=gcc and CXX=g++ in
your spec file.
This would be awesome, but can you tell me what is the point in
switching
between 2 bad compilers at the build time?
And just what is supposed to be bad about them?
Clang is too young and unstable, full of bugs,
Name a few.
Even when we were using a pre-release snapshot of clang 3.5, we ran into
only 1 thing that actually turned out to be a compiler bug (and that's
fixed in the 3.5 release). Doesn't sound very unstable or full of bugs
especially if we consider the number of "Internal Compiler Errors" we
typically get after a major gcc update.
There's a couple of projects that rely on gcc extensions (sometimes even
on particular gcc bugs) causing build failures with any other compiler -
but that's typically easy to fix, and if not, export CC=gcc export
CXX=g++ is perfectly fine.
the gcc4.9 that we
have in cooker
is worse then vanilla ,
How so? I'm using mostly clang these days, but I'm probably still one of
the heaviest gcc 4.9-2014.08 users here (esp. because that's the
compiler we use to build Android with at work) and haven't run into any
serious issues with it.
ttyl
bero
_______________________________________________
OM-Cooker mailing list
[email protected]
http://ml.openmandriva.org/listinfo.cgi/om-cooker-openmandriva.org
