[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: lilypond-2.17.28 doesn't build with libc++

From: David Kastrup
Subject: Re: lilypond-2.17.28 doesn't build with libc++
Date: Wed, 13 Nov 2013 10:09:20 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux)

Thomas Klausner <address@hidden> writes:

> On Wed, Nov 13, 2013 at 09:20:40AM +0100, David Kastrup wrote:
>> For a rarely used platform like clang++, the net result of this fix
>> would likely be that we get to hear something like "oh, by the way,
>> the last three versions did not compile using clang++ so I used GCC
>> instead" occasionally.  Or not hear it at all.
> Well, I'm currently regularly compiling lilypond with clang, and then
> there's this rarely-used operating system called 'Mac OS X' that has
> clang as its default compiler (and libc++ as its default C++ library
> since Mavericks), so there might be a few more people who can report
> issues

Most MacOSX users are happy using the precompiled binaries.  And those
are crosscompiled using GCC.  And even feedback from those using the
binaries is rather thin, so basically we are mostly on a "let's hope
this works" basis.  For example, there is
<URL:http://code.google.com/p/lilypond/issues/detail?id=3622> and we
really have little enough clue how to figure out what went wrong or
still goes wrong under which circumstances.

To get back to the topic: if we could get this strange ::to_string
requirement quashed or at least get a good idea why we don't see the
same problem under GCC but do under clang++, that would help finding a
solution that is more likely to stay fixed.

David Kastrup

reply via email to

[Prev in Thread] Current Thread [Next in Thread]