[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Lilypond-auto] Issue 3656 in lilypond: Problems building Lilypond 2
From: |
lilypond |
Subject: |
Re: [Lilypond-auto] Issue 3656 in lilypond: Problems building Lilypond 2.17.28 with libc++ for use with llvm |
Date: |
Tue, 12 Nov 2013 15:34:51 +0000 |
Comment #4 on issue 3656 by address@hidden: Problems building Lilypond
2.17.28 with libc++ for use with llvm
http://code.google.com/p/lilypond/issues/detail?id=3656
David Kastrup wrote:
From: David Kastrup
Subject: Re: lilypond-2.17.28 doesn't build with libc++
Date: Sat, 09 Nov 2013 13:41:38 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux)
Joerg Sonnenberger <address@hidden> writes:
It isn't. It's a bug in Lilypond I had fixed in pkgsrc for the old
version, but Thomas was missing the various changed for 2.17.28.
Essentially, lots of files are not including config.h and therefore
don't have the HAVE_STD_VECTOR_DATA define set.
You mean config.hh and HAVE_STL_DATA_METHOD here.
Attached is a patchset to fix this.
That seems quite non-sensical. If std-vector.hh needs to include
config.hh to work, then one should include it in std-vector.hh and not
manually try to include it in every file including std-vector.hh.
some inconsistencies in the forward type defines
Why would those be problematic? I find the change ugly.
In my youth, struct and class keywords were exactly equivalent, the sole
difference being the starting accessibility (public for struct, private
for class) in the member declarations.
Has this changed?
--
David Kastrup
--
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
- [Lilypond-auto] Issue 3656 in lilypond: Problems building Lilypond 2.17.28 with libc++ for use with llvm, lilypond, 2013/11/12
- Re: [Lilypond-auto] Issue 3656 in lilypond: Problems building Lilypond 2.17.28 with libc++ for use with llvm, lilypond, 2013/11/12
- Re: [Lilypond-auto] Issue 3656 in lilypond: Problems building Lilypond 2.17.28 with libc++ for use with llvm, lilypond, 2013/11/12
- Re: [Lilypond-auto] Issue 3656 in lilypond: Problems building Lilypond 2.17.28 with libc++ for use with llvm, lilypond, 2013/11/12
- Re: [Lilypond-auto] Issue 3656 in lilypond: Problems building Lilypond 2.17.28 with libc++ for use with llvm,
lilypond <=
- Re: [Lilypond-auto] Issue 3656 in lilypond: Problems building Lilypond 2.17.28 with libc++ for use with llvm, lilypond, 2013/11/12
- Re: [Lilypond-auto] Issue 3656 in lilypond: Problems building Lilypond 2.17.28 with libc++ for use with llvm, lilypond, 2013/11/12