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

[lilypond]

Updates:
        Labels: Fixed_2_19_0

Comment #31 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

Well, I'm not sure it's our job to warn people about the code generation of  
llvm, in particular if you say you've had the same problem with other  
software.

But if anybody wants to make a patch for the documentation, that should be  
fine.  At any rate, need to get this flushed from the queue in time for  
2.17.96, so pushing to staging (keeping on countdown for stable/2.18) as

commit 2c633c806d4f1c760bec4a1da90e0e0011102d7a
Author: David Kastrup <address@hidden>
Date:   Mon Nov 18 20:59:15 2013 +0100

    Issue 3656/2: disambiguate our own ::to_string from std::to_string

commit 2bd665b7b90b74a4e0e838b1827da12ad646e289
Author: David Kastrup <address@hidden>
Date:   Tue Nov 12 17:56:31 2013 +0100

    Issue 3656: Problems building Lilypond 2.17.95 with libc++ for use with  
llvm

    std-vector.hh did not include config.hh but relied on it


--
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