Re: GUB and librestrict

2016-08-09 Thread littlesincanada
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

Re: GUB and librestrict

2016-08-09 Thread Masamichi Hosoda
> 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 instead of errors. Anyway, I've crea

Re: GUB and librestrict

2016-08-08 Thread littlesincanada
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

Re: GUB and librestrict

2016-08-08 Thread Ralph Little
Hi Excellent! I will give it a try tonight! Many thanks Ralph On Mon, 8/8/16, Masamichi Hosoda wrote: Subject: Re: GUB and librestrict To: w...@gnu.org Cc: m...@philholmes.net, littlesincan...@yahoo.co.uk, lilypond-devel@gnu.org Received: Monday

Re: GUB and librestrict

2016-08-08 Thread Werner LEMBERG
>> Irrespective of that, can someone please fix the `restrict' problem? >> It should be a trivial renaming issue. > > 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, som

Re: GUB and librestrict

2016-08-08 Thread Masamichi Hosoda
>> 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. > > Irrespective of that, can someone please fix the `restrict' problem? > It should be a trivial renaming issue. I

Re: GUB and librestrict

2016-08-08 Thread David Kastrup
littlesincanada writes: > 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<

Re: GUB and librestrict

2016-08-07 Thread littlesincanada
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

Re: GUB and librestrict

2016-08-07 Thread littlesincanada
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

Re: GUB and librestrict

2016-08-07 Thread Werner LEMBERG
> 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. Irrespective of that, can someone please fix the `restrict' problem? It should be a trivial renaming issue. Wern

Re: GUB and librestrict

2016-08-07 Thread Phil Holmes
ust 07, 2016 2:46 AM Subject: GUB and librestrict 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.

GUB and librestrict

2016-08-06 Thread littlesincanada
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