Re: GUB calling 'false'

[Phil Holmes]

----- Original Message ----- 
From: <address@hidden>
To: "lilypond-devel Development" <address@hidden>
Sent: Wednesday, January 04, 2012 12:04 PM
Subject: GUB calling 'false'


> Hey all,
>
> I'm getting adeptish at reading GUB barf, but what puzzles me is that the 
> command GUB called was 'false' (see the end of the copy and paste from the 
> logfile).  Thoughts?
>
> Cheers,
> MS
>
> MapLocate[/home/mikesol/gub/target/linux-x86/install/lilypond-doc-2.15.23-root] 
> no files matching pattern: lib*.la
> invoking rm -f 
> /home/mikesol/gub/target/linux-x86/install/lilypond-doc-2.15.23-root/usr/info/dir 
> /home/mikesol/gub/target/linux-x86/install/lilypond-doc-2.15.23-root/usr/info/dir.old 
> /home/mikesol/gub/target/linux-x86/install/lilypond-doc-2.15.23-root/usr/share/info/dir 
> /home/mikesol/gub/target/linux-x86/install/lilypond-doc-2.15.23-root/usr/share/info/dir.old 
> /home/mikesol/gub/target/linux-x86/install/lilypond-doc-2.15.23-root/usr/cross/info/dir 
> /home/mikesol/gub/target/linux-x86/install/lilypond-doc-2.15.23-root/usr/cross/info/dir.old 
> /home/mikesol/gub/target/linux-x86/install/lilypond-doc-2.15.23-root/usr/cross/share/info/dir 
> /home/mikesol/gub/target/linux-x86/install/lilypond-doc-2.15.23-root/usr/cross/share/info/dir.old
> invoking LD_PRELOAD= cp -f sourcefiles/dir 
> /home/mikesol/gub/target/linux-x86/install/lilypond-doc-2.15.23-root/share/info/dir
> invoking cd 
> /home/mikesol/gub/target/linux-x86/install/lilypond-doc-2.15.23-root/share/info 
> && 
> LILYPOND_EXTERNAL_BINARY=/home/mikesol/gub/target/linux-x86/root/usr/bin/lilypond 
> PATH=/home/mikesol/gub/target/tools/root/usr/bin:/home/mikesol/gub/target/linux-x86/root/usr/bin:$PATH 
> MALLOC_CHECK_=2 
> LD_LIBRARY_PATH=/home/mikesol/gub/target/tools/root/usr/lib:/home/mikesol/gub/target/linux-x86/root/usr/lib:${LD_LIBRARY_PATH-/foe} 
> GS_FONTPATH=/home/mikesol/gub/target/linux-x86/root/usr/share/ghostscript/8.70/fonts:/home/mikesol/gub/target/linux-x86/root/usr/share/gs/fonts 
> GS_LIB=/home/mikesol/gub/target/linux-x86/root/usr/share/ghostscript/8.70/Resource/Init:/home/mikesol/gub/target/linux-x86/root/usr/share/ghostscript/8.70/Resource 
> install-info --info-dir=. lilypond-notation.info
> install-info: warning: no info dir entry in `lilypond-notation.info'
> invoking LD_PRELOAD= tar -C 
> /home/mikesol/gub/target/linux-x86/install/lilypond-doc-2.15.23-root -cjf 
> /home/mikesol/gub/uploads/lilypond-2.15.23-2.documentation.tar.bz2 .
> invoking LD_PRELOAD= tar --exclude '*.signature' -C 
> /home/mikesol/gub/target/linux-x86/build/lilypond-git.sv.gnu.org--lilypond.git-release-unstable/out-www/online-root 
>  -cjf /home/mikesol/gub/uploads/lilypond-2.15.23-2.webdoc.tar.bz2 .
> Running dump_file
>  ('install', 
> '/home/mikesol/gub/target/linux-x86/status/lilypond-doc-2.15.23-f3686ac8951d6627146d5224dc4660598ea8abe5', 
> 'w')
>  {'permissions': 420}
> *** Stage: package (lilypond-doc, linux-x86)
> 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
>
>
> _______________________________________________
> lilypond-devel mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/lilypond-devel

Can't help the specific, but I'm assuming this uses make?  If so, you can 
get (often lots of) extra information with the -d flag - i.e. make -d 
target.  Might give you extra info on what it's doing when it fails.  Oh - 
and redirect the output to a logfile with make -d target &> logfile.txt so 
you can check more precisely what's going on.

--
Phil Holmes