Re: GUB failing

[David Kastrup]

"Phil Holmes" <email@philholmes.net> writes:

> Not sure it's working.  It ran happily for just over 15 minutes and
> seems to have stalled for the last hour.  It's not consuming CPU but
> hasn't returned. The log has:
>
> **** unlocked-dist-check rule
> make[3]: Entering directory `/home/gub/NewGub/gub'
> PATH=/home/gub/NewGub/gub/target/tools/root/usr/bin:/home/gub/NewGub/gub/target/tools/root/usr/bin:/home/gub/NewGub/gub/target/tools/root/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
> \
> python2 test-lily/dist-check.py\
> --branch=release/unstable \
> --url=git://git.sv.gnu.org/lilypond.git \
> --repository=downloads/lilypond
>   
> /home/gub/NewGub/gub/target/linux-x86/build/lilypond-git.sv.gnu.org--lilypond.git-release-unstable
> make[4]: Entering directory
> `/home/gub/NewGub/gub/target/linux-x86/build/lilypond-git.sv.gnu.org--lilypond.git-release-unstable'
> Making out/RELEASE-COMMIT
> make[5]: Entering directory
> `/home/gub/NewGub/gub/target/linux-x86/build/lilypond-git.sv.gnu.org--lilypond.git-release-unstable/python'
> make[6]: Entering directory
> `/home/gub/NewGub/gub/target/linux-x86/build/lilypond-git.sv.gnu.org--lilypond.git-release-unstable/python/auxiliar'
>
> Then about 200 lines of Entering... Leaving directories, then:
>
> make[5]: Leaving directory
> `/home/gub/NewGub/gub/target/linux-x86/build/lilypond-git.sv.gnu.org--lilypond.git-release-unstable'
> tar: invalid argument 'order' for '--sort'
> Valid arguments are:
> - 'none'
> - 'name'
> - 'inode'
> make[4]: Leaving directory
> `/home/gub/NewGub/gub/target/linux-x86/build/lilypond-git.sv.gnu.org--lilypond.git-release-unstable'
>
> And that's where it stops doing anything.
>
> Anyone any ideas?

Sounds like tar (or some other program?) got nonsensical options and is
now waiting for input from the terminal instead of some program or file.
You can try to see what happens if you type Ctrl-D (End of file).  If I
guess right, something more should happen.  The worst that can happen
(but not really if the terminal is locked up without prompt) is that
your terminal window closes.

-- 
David Kastrup