|
From: | Phil Holmes |
Subject: | Re: Master fails to compile |
Date: | Fri, 22 May 2015 17:07:41 +0100 |
To: "Phil Holmes" <address@hidden> Cc: <address@hidden> Sent: Friday, May 22, 2015 4:57 PM Subject: Re: Master fails to compile
"Phil Holmes" <address@hidden> writes:----- Original Message ----- From: "David Kastrup" <address@hidden>To: "Phil Holmes" <address@hidden> Cc: <address@hidden> Sent: Friday, May 22, 2015 4:37 PM Subject: Re: Master fails to compile"Phil Holmes" <address@hidden> writes:Does it help if you move the LY_DECLARE_SMOB_PROC lines in lily/include/listener.hh which currently are right above the corresponding function definitions to below the corresponding function definitions?Not 100% certain what change was needed. Below is a patch showing what I tried and compilation still failed.That was what I meant, yes. I just tried compiling with Clang++ and this worked out fine as well (modulo 5 gazillion warnings elsewhere, good grief). So I suspect that we are within the C++ standards here. What g++ version are you using? -- David Kastrup4.4.3. It's the version that came with lilydev 1.1I'm surprised it did not blow up around your ears earlier. That sounds about as old as we had in GUB before we were forced to upgrade in consequence of some template usage patterns last fall. What's the current version of Lilydev? -- David Kastrup
Looks like it's 3.0: IIRC James created it and so would be best placed to say what the gcc version is. I'm quite happy to upgrade my gcc providing it's not impossible to work out how to do it. Don't really want to trash my current development environment to upgrade to a later lilydev.
--Phil Holmes
[Prev in Thread] | Current Thread | [Next in Thread] |