Re: [Lilypond-auto] Issue 3656 in lilypond: Problems building Lilypond 2.17.95 with libc++ for use with llvm

[lilypond]

Comment #18 on issue 3656 by address@hidden: Problems building Lilypond  
2.17.95 with libc++ for use with llvm
http://code.google.com/p/lilypond/issues/detail?id=3656

Regarding comment #16: "Probably it is best to use the scope operator to  
specify LilyPond's to_string() until the standard version has been out in  
libraries enough to have the implementations debugged."

I agree up to "until", everything after that sounds like either a job for  
autoconf or leaning towards the absurd.  But at any rate, we have to push  
out 2.18 in a reasonable time frame, and creating a whole autoconf  
framework or whatever else is not really feasible.  A patch doing the ::  
thing was floated on the list already and is referenced above.  So I'll  
incorporate that.

There is also the class/struct mismatch thing, but that's just a warning,  
and as far as I know, it's perfectly standard-compliant.  It might make  
sense as a warning remover to recode the affected
struct ... {
into
class ... { public:
to get rid of the complaints, but it's not a high priority for me.

--
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings