Hi James!
On Sun, Apr 06, 2014 at 05:49:06PM +0100, James wrote:
> Thomas,
>
> On 06/04/14 15:19, Thomas Klausner wrote:
> >A recent git commit introduced a call to to_string. To make lilypond
> >compile with clang again, please commit the attached diff (fixed like
> >
A recent git commit introduced a call to to_string. To make lilypond
compile with clang again, please commit the attached diff (fixed like
other instances of the same issue).
Thanks,
Thomas
--- lily/misc.cc.orig 2014-04-06 12:44:15.0 +
+++ lily/misc.cc
@@ -31,7 +31,7 @@ int
intlog2
Hi!
I saw in the bug report that some version of these changes is now
going to get merged. Thank you for that!
The bug report also mentions that the clang version is slower than the
gcc version on some files. Does someone have an example file and
timings from their machine?
Thanks,
Thomas
On Wed, Nov 13, 2013 at 09:20:40AM +0100, David Kastrup wrote:
> Thomas Klausner writes:
>
> > Hi James!
> >
> > On Sat, Nov 09, 2013 at 09:39:34PM +0100, Joerg Sonnenberger wrote:
> >> On Sat, Nov 09, 2013 at 12:20:36PM +, James wrote:
> >> >
Hi James!
On Sat, Nov 09, 2013 at 09:39:34PM +0100, Joerg Sonnenberger wrote:
> On Sat, Nov 09, 2013 at 12:20:36PM +, James wrote:
> > These patches don't apply cleanly to current master.
> >
> > If you can git format them, then I can shepherd them through our
> > patch review/test process fo
On Fri, Nov 08, 2013 at 12:01:04PM +0100, David Kastrup wrote:
> So you better find someone who actually cares about that
> compiler/platform/library to get to work on it.
That's why I sent these mails -- I had hoped to find someone here.
I'll let you know if I come up with any patches.
Thomas
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:
>
>
Hi!
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:
In file included from file-path.cc:21:
In file included from ./include/file-path.hh:23:
In file included f
Hi!
GNU make 4.0 is out.
It stops, reporting an error, when trying to build lilypond-2.17.28:
"recipes commence before first target"
It looks to me like a misplaced endif. The attached patch fixes it.
Btw, what are the plans for a 2.18 release? :)
Thomas
$NetBSD$
--- stepmake/stepmake/po-tar
> Can you also report which of the preexisting files in lily/out/ gets
> overwritten by the problematic build, and which not?
The header file is not recreated, but the cc file is:
-rw-r--r-- 1 pbulk builder 258460 Sep 2 07:14
work/lilypond-2.17.25/lily/out/parser.cc
-rw-r--r-- 1 pbulk buil
I've followed the thread and can confirm that
rm lily/out/parser.*
before building lilypond fixes the problem for me.
Thomas
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Hi David!
I see you replied to my build issue in lilypond-2.17.24 that I should
try a clean build.
I've done that. I built versions 2.17.23, 2.17.24, and 2.17.25 from
scratch in a sandbox, in different directories, and I still see this
issue, in 2.17.24 and 2.17.25, but not in 2.17.23.
Also, I'v
On Wed, Aug 14, 2013 at 09:35:46PM +0200, David Kastrup wrote:
> Marek Klein writes:
>
> > Hello David,
> > do we need a tracker issue for this?
> >
> > Marek
> >
> > 2013/8/5 David Kastrup
> >
> >> Thomas Klausner writes:
> &
Hi!
The latest stable and development branches of lilypond do not compile with
the recently released bison-3.0.
The following patch fixes this (sorry, whitespace may be off):
--- lily/parser.yy.orig 2013-01-04 13:41:57.0 +
+++ lily/parser.yy
@@ -100,7 +100,7 @@ or
-%pure_parser
14 matches
Mail list logo
