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

[lilypond]

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

From:   David Kastrup
Subject:        Re: lilypond-2.17.28 doesn't build with libc++
Date:   Fri, 08 Nov 2013 12:35:56 +0100
User-agent:     Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux)

Thomas Klausner <address@hidden> writes:

> On Fri, Nov 08, 2013 at 11:15:29AM +0100, Thomas Klausner wrote:
> > I've tried building lilypond-2.17.28 with libc++, the new standard c++
> > library for use with llvm (http://libcxx.llvm.org/).

> > I have a build failure I don't really know how to fix, it is:

> I just saw that 2.17.95 is out.
> It still has the same error.

Sure.  Why should't it?

> I also saw
> In file included from interval-set.cc:20:
> In file included from ./include/interval-set.hh:23:
> In file included from ./include/std-vector.hh:74:
> /usr/include/c++/vector:1371:12: error: calling a private constructor of
> class 'std::__1::__wrap_iter<Interval_t<double> *>'
>      return iterator(__p);
>             ^

Looks like the same.

> warn.cc:114:29: error: use of undeclared identifier 'expected_warnings';  
> did
> you mean 'expect_warning'?
>        for (vsize i = 0; i < expected_warnings.size (); i++)
>                              ^~~~~~~~~~~~~~~~~
>                              expect_warning
> warn.cc:102:6: note: 'expect_warning' declared here

and so on and so on.

It does not make a lot of sense to report all these one by one and hope
that magically this will get stuff fixed.

It's pretty clear that someone has to actually _work_ on getting this
stuff through and classify which problems are due to the C++ library,
which are due to bad usage in LilyPond, and supply fixes to _both_.

So you better find someone who actually cares about that
compiler/platform/library to get to work on it.

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