Le mercredi 22 août 2012 à 18:43 +0100, Graham Percival a écrit :
> Presumably the script was tested with bash, but was being run with
> sh or dash?  or something like that?
I tested "make dist" succesfully on my system, but without being sure if
sh on my distro would behave as bash or not...  Spaces in commannd
outputs ùight also be a cause of this breakage... I'm reworking lines 43
and 54 of GNUmakefile.in to get rid of bashisms and quoting command
outputs, and will submit an issue ASAP after having checked "make dist".

John


> 
> - Graham
> 
> 
> git
> --git-dir=/main/src/gub/target/linux-x86/src/lilypond-git.sv.gnu.org--lilypond.git-release-unstable/.git
> show HEAD | head -100 > out/RELEASE-COMMIT
> make[5]: Leaving directory
> `/main/src/gub/target/linux-x86/build/lilypond-git.sv.gnu.org--lilypond.git-release-unstable'
> cd
> /main/src/gub/target/linux-x86/src/lilypond-git.sv.gnu.org--lilypond.git-release-unstable
> && git ls-files
> >/main/src/gub/target/linux-x86/build/lilypond-git.sv.gnu.org--lilypond.git-release-unstable/.gitfilelist
> /bin/sh: Syntax error: word unexpected (expecting "then")
> make[4]: *** [dist] Error 2
> make[4]: Leaving directory
> `/main/src/gub/target/linux-x86/build/lilypond-git.sv.gnu.org--lilypond.git-release-unstable'
> Traceback (most recent call last):
>   File "test-lily/dist-check.py", line 137, in <module>
>     main ()
>   File "test-lily/dist-check.py", line 129, in main
>     system ('cd %(builddir)s/ && make DOCUMENTATION=yes dist' %
> locals ())
>   File "test-lily/dist-check.py", line 56, in system
>     raise Exception ('failed')
> Exception: failed
> make[3]: *** [unlocked-dist-check] Error 1
> make[3]: Leaving directory `/main/src/gub'
> 
> 
> 
> 
> _______________________________________________
> 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

Reply via email to