Hi,
OK, not many comments but I guess since there is no code, there's
nothing to comment on :)
I will try to get my prototype together and integrated with Lilypond
over the next couple of weeks and check it into my branch.
It's going to be pretty rough but at least functional.
Cheers,
Ralph
Hi,
On 11/08/16 21:18, David Kastrup wrote:
littlesincanada writes:
On the face of it, a rebase is the obvious solution, but I'm told that
it's a cardinal sin to rebase commits that have already been pushed.
So forget about that cardinal sin and just rebase. You'll find
Hi Devs,
It's a long time since I pushed any Lilypond dev work to my dev branch
dev/rlittle. About 9 years to be precise. :o
OK, time that situation changed.
The only commit on that branch is a first pass at a Braille output
option base. Things have moved on and I'm working on it some more, bu
Hi,
On 09/08/16 04:53, Masamichi Hosoda wrote:
The path in this line looks a bit wrong:
cc1: error:
/home/ralph/gub/target/tools/root/usr/lib/libffi-3.2.1/include: No
such file or directory [-Werror=missing-include-dirs]
Is nobody else having these issues?
In my GUB environment, it is warnings
Hi,
On 08/08/16 04:23, Masamichi Hosoda wrote:
I've created a pull request.
https://github.com/gperciva/gub/pull/27
It fixes the librestrict C99 problem.
And, it fixes tools::guile texi compilation problem.
Also, some libraries update is contained.
I've succeed full `make lilypond' in my GUB e
Hi,
However, I get a further failure in the build which I'm not sure how
to deal with:
Further to the further, I'm wondering if the following is actually what
is causing the error and the other error might be a problem in the error
recovery:
--8<--8<--8<--8<--8<--8
Hi,
On 07/08/16 03:17, Phil Holmes wrote:
You should get more debugging information in the terminal output - it
normally has something like "Tail of .log". Have a good look in
xxx.log and see what the error is.
OK, I fiddled with it a bit and I managed to get further. Not really
sure w
Hi,
I'm trying to build Lilypond using GUB.
I'm hitting on a problem in librestrict.
In restrict.c, in the initialize() function, a new c99 keyword
"restrict" is being used as a variable.
If I rename it, then the source compiles.
However, I get a further failure in the build which I'm not sure
