Comment #1 on issue 2011 by [email protected]: configure doesn't like clang++
http://code.google.com/p/lilypond/issues/detail?id=2011
I think the primary test to do here is checking that guile's stack-scanning
conservative garbage collector (and its source code) get along with
clang++. I should also be surprised if the flower tests throwing g++ 4.6.1
for a loop will be system independent enough to get along with clang++.
Actually, the whole yaffut.hh/Boost inheritage seems totally crazy and
likely unmaintainable to me. Perhaps we should file an issue for replacing
it with something doing the intended job rather than something much more
complex and unfathomable that is supposed to also cover our needs by
accident.
So it would be a good opportunity to throw that out, anyway.
Throwing guile out, in contrast, seems more challenging. So it really is
necessary to check its compatibility with clang++, or we have a non-starter.
_______________________________________________
bug-lilypond mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/bug-lilypond
