Status: Accepted
Owner: ----
Labels: Type-Maintainability Frog
New issue 2011 by [email protected]: configure doesn't like clang++
http://code.google.com/p/lilypond/issues/detail?id=2011
llvm / clang++ is an awesome new compiler that has much better error
checking, and occasionally produces faster code then g++. In my
artifastring physical string modeling library, I get a 10% speed-up just
from passing CXX="clang++" to configure -- seriously. No code changes, no
build system changes; just *poof* 10% faster.
lilypond's configure doesn't like that, because we check for GCC >= 3.4,
whereas llvm is at version 2.9. It would be nice if we did some kind of
intelligent checking of this, so that llvm is fine.
../configure CXX="clang++"
you can manually avoid this problem by modifying configure.in on lines 94
and 97. (GCC and GXX)
I'm mainly interested in clang++ for the error checking. We *know* that we
have odd memory problems in lilypond, and there's a lot of positive buzz on
the internets about clang's improved error checking. Seems like a useful
tool to bash against our code base.
_______________________________________________
bug-lilypond mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/bug-lilypond
