Re: GUB and librestrict

[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 instead of errors.

Anyway, I've created a patch that fixes it and updated the pull request.
https://github.com/gperciva/gub/pull/27


Patch works. Great!
But...when we get to harfbuzz.

--8<--8<--8<--8<--8<--8<--8<--8<--8<--8<--8<-
/bin/bash ../libtool  --tag=CXX   --mode=compile x86_64-linux-g++ 
-DHAVE_CONFIG_H -I. 
-I/home/ralph/gub/target/linux-64/src/harfbuzz-1.2.7/src -I.. 
-I/usr/include-g -O2 -fno-rtti -fno-exceptions -Wcast-align 
-fvisibility-inlines-hidden  -MT libharfbuzz_icu_la-hb-icu.lo -MD -MP 
-MF .deps/libharfbuzz_icu_la-hb-icu.Tpo -c -o 
libharfbuzz_icu_la-hb-icu.lo `test -f 'hb-icu.cc' || echo 
'/home/ralph/gub/target/linux-64/src/harfbuzz-1.2.7/src/'`hb-icu.cc
libtool: compile:  x86_64-linux-g++ -DHAVE_CONFIG_H -I. 
-I/home/ralph/gub/target/linux-64/src/harfbuzz-1.2.7/src -I.. 
-I/usr/include -g -O2 -fno-rtti -fno-exceptions -Wcast-align 
-fvisibility-inlines-hidden -MT libharfbuzz_icu_la-hb-icu.lo -MD -MP -MF 
.deps/libharfbuzz_icu_la-hb-icu.Tpo -c 
/home/ralph/gub/target/linux-64/src/harfbuzz-1.2.7/src/hb-icu.cc -fPIC 
-DPIC -o .libs/libharfbuzz_icu_la-hb-icu.o
librestrict:error:/home/ralph/gub/target/linux-64/root/usr/cross/libexec/gcc/x86_64-linux/4.9.2/cc1plus: 
tried to open () file /usr/include/stdc-predef.h

librestrict:allowed:
  /home/ralph/gub/target/linux-64
  /tmp
  /dev/null
  /dev/urandom
  /proc/self
:0:0: internal compiler error: Aborted
librestrict:error:/home/ralph/gub/target/linux-64/root/usr/cross/libexec/gcc/x86_64-linux/4.9.2/cc1plus: 
tried to open () file 
/home/ralph/gub/target/tools/root/usr/lib/librestrict.so

librestrict:allowed:
  /home/ralph/gub/target/linux-64
  /tmp
  /dev/null
  /dev/urandom
  /proc/self
x86_64-linux-g++: internal compiler error: Aborted (program cc1plus)
librestrict:error:/home/ralph/gub/target/linux-64/root/usr/cross/bin/x86_64-linux-g++: 
tried to open () file 
/home/ralph/gub/target/tools/root/usr/lib/librestrict.so

librestrict:allowed:
  /home/ralph/gub/target/linux-64
  /tmp
  /dev/null
  /dev/urandom
  /proc/self
../libtool: line 990:  8585 Aborted x86_64-linux-g++ 
-DHAVE_CONFIG_H -I. 
-I/home/ralph/gub/target/linux-64/src/harfbuzz-1.2.7/src -I.. 
-I/usr/include -g -O2 -fno-rtti -fno-exceptions -Wcast-align 
-fvisibility-inlines-

...
--8<--8<--8<--8<--8<--8<--8<--8<--8<--8<--8<-

I have to admit that I'm getting a bit demoralised.
I report this issue, but I'm going to abandon GUB and return to just 
compiling git head with repo build-deps for now.

I can't build the doc but that's not a priority for me at the moment.

Regards,
Ralph




___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: GUB and librestrict

[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 created a patch that fixes it and updated the pull request.
https://github.com/gperciva/gub/pull/27

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: GUB and librestrict

[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 environment.



I applied your patch and that gets me much further.
Now a problem in glib:

---8<---8<---8<---8<---8<---8<---8<
MD -MP -MF .deps/libgobject_2_0_la-gparam.Tpo -c 
/home/ralph/gub/target/tools/src/glib-2.44.1/gobject/gparam.c  -fPIC 
-DPIC -o .libs/libgobject_2_0_la-gparam.o
cc1: error: 
/home/ralph/gub/target/tools/root/usr/lib/libffi-3.2.1/include: No such 
file or directory [-Werror=missing-include-dirs]
cc1: error: 
/home/ralph/gub/target/tools/root/usr/lib/libffi-3.2.1/include: No such 
file or directory [-Werror=missing-include-dirs]
cc1: error: 
/home/ralph/gub/target/tools/root/usr/lib/libffi-3.2.1/include: No such 
file or directory [-Werror=missing-include-dirs]

cc1: some warnings being treated as errors
make[4]: *** [libgobject_2_0_la-gatomicarray.lo] Error 1
make[4]: *** Waiting for unfinished jobs
cc1: some warnings being treated as errors
make[4]: *** [libgobject_2_0_la-gclosure.lo] Error 1
cc1: some warnings being treated as errors
make[4]: *** [libgobject_2_0_la-genums.lo] Error 1
cc1: some warnings being treated as errors
cc1: some warnings being treated as errors
cc1: some warnings being treated as errors
make[4]: *** [libgobject_2_0_la-gmarshal.lo] Error 1
make[4]: *** [libgobject_2_0_la-gbinding.lo] Error 1
make[4]: *** [libgobject_2_0_la-gboxed.lo] Error 1
cc1: some warnings being treated as errors
make[4]: *** [libgobject_2_0_la-gparam.lo] Error 1
cc1: some warnings being treated as errors
make[4]: *** [libgobject_2_0_la-gobject.lo] Error 1
make[4]: Leaving directory 
`/home/ralph/gub/target/tools/build/glib-2.44.1/gobject'

make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory 
`/home/ralph/gub/target/tools/build/glib-2.44.1/gobject'

make[2]: *** [all] Error 2
make[2]: Leaving directory 
`/home/ralph/gub/target/tools/build/glib-2.44.1/gobject'

make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/ralph/gub/target/tools/build/glib-2.44.1'
make: *** [all] Error 2
Command barfed: cd /home/ralph/gub/target/tools/build/glib-2.44.1 && 
make -j8

Traceback (most recent call last):
  File "bin/gub", line 233, in exceptional_build
build (settings, options, files)
  File "bin/gub", line 229, in build
b.build_source_packages (names)
  File "bin/../gub/buildrunner.py", line 334, in build_source_packages
self.spec_build (spec_name)
  File "bin/../gub/buildrunner.py", line 262, in spec_build
deferred_runner.execute_deferred_commands ()
  File "bin/../gub/runner.py", line 167, in execute_deferred_commands
cmd.execute (self.logger)
  File "bin/../gub/commands.py", line 75, in execute
ignore_errors=self.ignore_errors)
  File "bin/../gub/loggedos.py", line 93, in system
raise misc.SystemFailed (m)
SystemFailed: Command barfed: cd 
/home/ralph/gub/target/tools/build/glib-2.44.1 && make -j8

---8<---8<---8<---8<---8<---8<---8<

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?

Cheers,
Ralph

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: GUB and librestrict

[Ralph Little]

Hi
Excellent! I will give it a try tonight!

Many thanks
Ralph


On Mon, 8/8/16, Masamichi Hosoda <truer...@trueroad.jp> wrote:

 Subject: Re: GUB and librestrict
 To: w...@gnu.org
 Cc: m...@philholmes.net, littlesincan...@yahoo.co.uk, lilypond-devel@gnu.org
 Received: Monday, August 8, 2016, 12:23 PM
 
 >> 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'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 environment.
 

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: GUB and librestrict

[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, some libraries update is contained.

Thanks a lot for your quick patch!


Werner

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: GUB and librestrict

[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'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 environment.

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: GUB and librestrict

[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<--8<--8<--8<--8<--8<--8<--8<--8<---
> /home/ralph/gub/target/tools/src/guile-1.8.7/doc/ref/gh.texi:1000:
> must be after `@deftypefun' to use `@deftypefunx'
> /home/ralph/gub/target/tools/src/guile-1.8.7/doc/ref/fdl.texi:411:
> raising the section level of @appendixsubsec which is too low
> /home/ralph/gub/target/tools/src/guile-1.8.7/doc/ref/api-utility.texi:566:
> warning: node `C Hooks' is next for `Hook Reference' in menu but not
> in sectioning
> /home/ralph/gub/target/tools/src/guile-1.8.7/doc/ref/api-utility.texi:674:
> warning: node `Hook Reference' is prev for `C Hooks' in menu but not
> in sectioning
> /home/ralph/gub/target/tools/src/guile-1.8.7/doc/ref/api-options.texi:510:
> warning: node next `Printing options' in menu `Debugger options' and
> in sectioning `Evaluator options' differ
> /home/ralph/gub/target/tools/src/guile-1.8.7/doc/ref/api-options.texi:533:
> warning: node prev `Evaluator options' in menu `Debugger options' and
> in sectioning `Printing options' differ
> /home/ralph/gub/target/tools/src/guile-1.8.7/doc/ref/api-options.texi:544:
> warning: node next `Evaluator trap options' in menu `Examples of
> option use' and in sectioning `Debugger options' differ
> /home/ralph/gub/target/tools/src/guile-1.8.7/doc/ref/api-options.texi:625:
> warning: node next `Debugger options' in menu `Evaluator options' and
> in sectioning `Examples of option use' differ
> /home/ralph/gub/target/tools/src/guile-1.8.7/doc/ref/api-options.texi:625:
> warning: node prev `Debugger options' in menu `Printing options' and
> in sectioning `Evaluator trap options' differ
> /home/ralph/gub/target/tools/src/guile-1.8.7/doc/ref/api-options.texi:681:
> warning: node prev `Examples of option use' in menu `Evaluator trap
> options' and in sectioning `Debugger options' differ
> make[2]: ***
> [/home/ralph/gub/target/tools/src/guile-1.8.7/doc/ref/guile.info]
> Error 1
> --8<--8<--8<--8<--8<--8<--8<--8<--8<---

Most of those would appear to be warnings.  What really strikes me is
that we are using Guile 1.8.7 here: the "newest" 1.8 version is 1.8.8
and there seems little point in not using that.  It may be unlikely to
fix any Texinfo problem (the above appear to be warnings and not fatal
though, possibly excepting the first) but when patching up things,
starting with anything but the latest operative version seems wasteful.

-- 
David Kastrup

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: GUB and librestrict

[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<--8<--8<--8<---
/home/ralph/gub/target/tools/src/guile-1.8.7/doc/ref/gh.texi:1000: must 
be after `@deftypefun' to use `@deftypefunx'
/home/ralph/gub/target/tools/src/guile-1.8.7/doc/ref/fdl.texi:411: 
raising the section level of @appendixsubsec which is too low
/home/ralph/gub/target/tools/src/guile-1.8.7/doc/ref/api-utility.texi:566: 
warning: node `C Hooks' is next for `Hook Reference' in menu but not in 
sectioning
/home/ralph/gub/target/tools/src/guile-1.8.7/doc/ref/api-utility.texi:674: 
warning: node `Hook Reference' is prev for `C Hooks' in menu but not in 
sectioning
/home/ralph/gub/target/tools/src/guile-1.8.7/doc/ref/api-options.texi:510: 
warning: node next `Printing options' in menu `Debugger options' and in 
sectioning `Evaluator options' differ
/home/ralph/gub/target/tools/src/guile-1.8.7/doc/ref/api-options.texi:533: 
warning: node prev `Evaluator options' in menu `Debugger options' and in 
sectioning `Printing options' differ
/home/ralph/gub/target/tools/src/guile-1.8.7/doc/ref/api-options.texi:544: 
warning: node next `Evaluator trap options' in menu `Examples of option 
use' and in sectioning `Debugger options' differ
/home/ralph/gub/target/tools/src/guile-1.8.7/doc/ref/api-options.texi:625: 
warning: node next `Debugger options' in menu `Evaluator options' and in 
sectioning `Examples of option use' differ
/home/ralph/gub/target/tools/src/guile-1.8.7/doc/ref/api-options.texi:625: 
warning: node prev `Debugger options' in menu `Printing options' and in 
sectioning `Evaluator trap options' differ
/home/ralph/gub/target/tools/src/guile-1.8.7/doc/ref/api-options.texi:681: 
warning: node prev `Examples of option use' in menu `Evaluator trap 
options' and in sectioning `Debugger options' differ
make[2]: *** 
[/home/ralph/gub/target/tools/src/guile-1.8.7/doc/ref/guile.info] Error 1

--8<--8<--8<--8<--8<--8<--8<--8<--8<---

Cheers,
Ralph


___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: GUB and librestrict

[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 what happened.
When I have got through it, I will do another bootstrap start to chase 
it down.


However, now I have an issue in the guile build.
From the bottom of the guile build log:

---8<---8<---8<---8<---8<---8<---8<---8<---8<---8<---8<---
...
  rc=$?; \
  CDPATH="${ZSH_VERSION+.}:" && cd 
/home/ralph/gub/target/tools/src/guile-1.8.7/doc/ref && \
  $restore $backupdir/* `echo 
".//home/ralph/gub/target/tools/src/guile-1.8.7/doc/ref/guile.info" | 
sed 's|[^/]*$||'`; \

fi; \
rm -rf $backupdir; exit $rc
/home/ralph/gub/target/tools/src/guile-1.8.7/doc/ref/gh.texi:1000: must 
be after `@deftypefun' to use `@deftypefunx'
/home/ralph/gub/target/tools/src/guile-1.8.7/doc/ref/fdl.texi:411: 
raising the section level of @appendixsubsec which is too low
/home/ralph/gub/target/tools/src/guile-1.8.7/doc/ref/api-utility.texi:566: 
warning: node `C Hooks' is next for `Hook Reference' in menu but not in 
sectioning
/home/ralph/gub/target/tools/src/guile-1.8.7/doc/ref/api-utility.texi:674: 
warning: node `Hook Reference' is prev for `C Hooks' in menu but not in 
sectioning
/home/ralph/gub/target/tools/src/guile-1.8.7/doc/ref/api-options.texi:510: 
warning: node next `Printing options' in menu `Debugger options' and in 
sectioning `Evaluator options' differ
/home/ralph/gub/target/tools/src/guile-1.8.7/doc/ref/api-options.texi:533: 
warning: node prev `Evaluator options' in menu `Debugger options' and in 
sectioning `Printing options' differ
/home/ralph/gub/target/tools/src/guile-1.8.7/doc/ref/api-options.texi:544: 
warning: node next `Evaluator trap options' in menu `Examples of option 
use' and in sectioning `Debugger options' differ
/home/ralph/gub/target/tools/src/guile-1.8.7/doc/ref/api-options.texi:625: 
warning: node next `Debugger options' in menu `Evaluator options' and in 
sectioning `Examples of option use' differ
/home/ralph/gub/target/tools/src/guile-1.8.7/doc/ref/api-options.texi:625: 
warning: node prev `Debugger options' in menu `Printing options' and in 
sectioning `Evaluator trap options' differ
/home/ralph/gub/target/tools/src/guile-1.8.7/doc/ref/api-options.texi:681: 
warning: node prev `Examples of option use' in menu `Evaluator trap 
options' and in sectioning `Debugger options' differ
make[2]: *** 
[/home/ralph/gub/target/tools/src/guile-1.8.7/doc/ref/guile.info] Error 1
make[2]: Leaving directory 
`/home/ralph/gub/target/tools/build/guile-1.8.7/doc/ref'

make[1]: *** [install-recursive] Error 1
make[1]: Leaving directory 
`/home/ralph/gub/target/tools/build/guile-1.8.7/doc'

make: *** [install-recursive] Error 1
Command barfed: cd /home/ralph/gub/target/tools/build/guile-1.8.7 && 
make DESTDIR=/home/ralph/gub/target/tools/install/guile-1.8.7-root install

Traceback (most recent call last):
  File "bin/gub", line 233, in exceptional_build
build (settings, options, files)
  File "bin/gub", line 229, in build
b.build_source_packages (names)
  File "bin/../gub/buildrunner.py", line 334, in build_source_packages
self.spec_build (spec_name)
  File "bin/../gub/buildrunner.py", line 262, in spec_build
deferred_runner.execute_deferred_commands ()
  File "bin/../gub/runner.py", line 167, in execute_deferred_commands
cmd.execute (self.logger)
  File "bin/../gub/commands.py", line 75, in execute
ignore_errors=self.ignore_errors)
  File "bin/../gub/loggedos.py", line 93, in system
raise misc.SystemFailed (m)
SystemFailed: Command barfed: cd 
/home/ralph/gub/target/tools/build/guile-1.8.7 && make 
DESTDIR=/home/ralph/gub/target/tools/install/guile-1.8.7-root install

---8<---8<---8<---8<---8<---8<---8<---8<---8<---8<---8<---

The following line looks a bit suspicious:

$restore $backupdir/* `echo 
".//home/ralph/gub/target/tools/src/guile-1.8.7/doc/ref/guile.info" | 
sed 's|[^/]*$||'`; \


..and would seem to be the problem.
Why would the path start with .//?

Cheers,
Ralph

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: GUB and librestrict

[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.


Werner

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: GUB and librestrict

[Phil Holmes]

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.


--
Phil Holmes


- Original Message - 
From: "littlesincanada" <littlesincan...@yahoo.co.uk>

To: <lilypond-devel@gnu.org>
Sent: Sunday, August 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.

However, I get a further failure in the build which I'm not sure how to 
deal with:


---8<---8<---8<---8<---8<---8<---8<-

Running dump_file
  ('install', 
'/home/ralph/gub/target/tools/status/librestrict-1.9.a-1.9.a', 'w')

  {'permissions': 420}
 *** Stage: package (librestrict, tools)
invoking false
Command barfed: false
Traceback (most recent call last):
  File "bin/gub", line 233, in exceptional_build
build (settings, options, files)
  File "bin/gub", line 229, in build
b.build_source_packages (names)
  File "bin/../gub/buildrunner.py", line 334, in build_source_packages
self.spec_build (spec_name)
  File "bin/../gub/buildrunner.py", line 262, in spec_build
deferred_runner.execute_deferred_commands ()
  File "bin/../gub/runner.py", line 167, in execute_deferred_commands
cmd.execute (self.logger)
  File "bin/../gub/commands.py", line 75, in execute
ignore_errors=self.ignore_errors)
  File "bin/../gub/loggedos.py", line 93, in system
raise misc.SystemFailed (m)
SystemFailed: Command barfed: false
---8<---8<---8<---8<---8<---8<---8<---

Any ideas how to proceed?

I'm building on Linux Mint 18, x64.

Cheers,
Ralph

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel




___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

GUB and librestrict

[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 how to 
deal with:


---8<---8<---8<---8<---8<---8<---8<-

Running dump_file
  ('install', 
'/home/ralph/gub/target/tools/status/librestrict-1.9.a-1.9.a', 'w')

  {'permissions': 420}
 *** Stage: package (librestrict, tools)
invoking false
Command barfed: false
Traceback (most recent call last):
  File "bin/gub", line 233, in exceptional_build
build (settings, options, files)
  File "bin/gub", line 229, in build
b.build_source_packages (names)
  File "bin/../gub/buildrunner.py", line 334, in build_source_packages
self.spec_build (spec_name)
  File "bin/../gub/buildrunner.py", line 262, in spec_build
deferred_runner.execute_deferred_commands ()
  File "bin/../gub/runner.py", line 167, in execute_deferred_commands
cmd.execute (self.logger)
  File "bin/../gub/commands.py", line 75, in execute
ignore_errors=self.ignore_errors)
  File "bin/../gub/loggedos.py", line 93, in system
raise misc.SystemFailed (m)
SystemFailed: Command barfed: false
---8<---8<---8<---8<---8<---8<---8<---

Any ideas how to proceed?

I'm building on Linux Mint 18, x64.

Cheers,
Ralph

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel