Re: Compiling lilypond

[David Kastrup]

[For the record: compiling LilyPond with Clang++ currently fails]

Mojca Miklavec <address@hidden> writes:

> Hi,
>
> It seems that this is also a problem on the latest OS X, not just on
> my ancient box. We'll probably drop an email on the bug mailing list.

Here is an example you can report to the Clang++ mailing list.  This
overloading resolution seems to be what essentially fails with the
current LilyPond source.

class A {
public:
  template <void (A::*mf)()>
  void zip () { }
  void fun () { }
};

class B : public A
{
public:
  using A::zip; // Fails to involve A::zip in overloading resolution
  template <void (B::*mf)()>
  void zip () { }
} bex;


void x ()
{
  bex.zip <&B::fun> ();
}

Unfortunately, I don't see much of a way to circumvent this one in the
current code base without completely throwing large reorganizations and
simplifications away.

Sorry, you'll need to use GCC for now.

-- 
David Kastrup