Failed make doc for Patchy
I am not at home but Patchy complained just now. -- Forwarded message -- From: pkx1...@gmail.com Date: 14 March 2012 18:34 Subject: Patchy email Merged staging, now at: c6a925ecd742196979038804b02846faad7f2cc9 Success: ./autogen.sh --noconfigure Success: ../configure --disable-optimising Success: nice make clean -j6 CPU_COUNT=6 Success: nice make -j6 CPU_COUNT=6 Success: nice make test -j6 CPU_COUNT=6 *** FAILED BUILD *** nice make doc -j6 CPU_COUNT=6 Previous good commit: d11dbf277719c0179c5520154c925839d969a535 Current broken commit: c6a925ecd742196979038804b02846faad7f2cc9 -- -- James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Failed make doc for Patchy
James pkx1...@gmail.com writes: I am not at home but Patchy complained just now. -- Forwarded message -- From: pkx1...@gmail.com Date: 14 March 2012 18:34 Subject: Patchy email Merged staging, now at: c6a925ecd742196979038804b02846faad7f2cc9 Success: ./autogen.sh --noconfigure Success: ../configure --disable-optimising Success: nice make clean -j6 CPU_COUNT=6 Success: nice make -j6 CPU_COUNT=6 Success: nice make test -j6 CPU_COUNT=6 *** FAILED BUILD *** nice make doc -j6 CPU_COUNT=6 Previous good commit: d11dbf277719c0179c5520154c925839d969a535 Current broken commit: c6a925ecd742196979038804b02846faad7f2cc9 Documentation has not been touched between master and staging. A change by Carl would have triggered more likely in make test than in make doc. That makes changes from me (or a Heisenbug) most likely. My personal suspect would have been commit 65c8ce914c62117fb61a21237f7dcf80ebb0cc6e Author: David Kastrup d...@gnu.org Date: Sun Mar 11 12:16:52 2012 +0100 Make Score an initial Timing alias to allow for context mods But then I am pretty certain that I actually ran make info on that one to make reasonably sure it did not cause offense. I am taking a look right now. If you have relevant log file data, it might speed things up. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Failed make doc for Patchy
On Wed, Mar 14, 2012 at 08:16:17PM +0100, David Kastrup wrote: commit 65c8ce914c62117fb61a21237f7dcf80ebb0cc6e Make Score an initial Timing alias to allow for context mods But then I am pretty certain that I actually ran make info on that one to make reasonably sure it did not cause offense. info will check if you can generate the internals reference, i.e. with scm/documentation-generate.scm. It won't call the lilypond binary to produce any output at all. - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Failed make doc for Patchy
Graham Percival gra...@percival-music.ca writes: On Wed, Mar 14, 2012 at 08:16:17PM +0100, David Kastrup wrote: commit 65c8ce914c62117fb61a21237f7dcf80ebb0cc6e Make Score an initial Timing alias to allow for context mods But then I am pretty certain that I actually ran make info on that one to make reasonably sure it did not cause offense. info will check if you can generate the internals reference, i.e. with scm/documentation-generate.scm. It won't call the lilypond binary to produce any output at all. You are wrong. Try it. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Failed make doc for Patchy
On Wed, Mar 14, 2012 at 07:45:39PM +, Graham Percival wrote: info will check if you can generate the internals reference, i.e. with scm/documentation-generate.scm. It won't call the lilypond binary to produce any output at all. No wait, I'm completely wrong. Sorry, I was thinking of make (and makeinfo), not make info. - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Failed make doc for Patchy
- Original Message - From: David Kastrup d...@gnu.org To: lilypond-devel@gnu.org Sent: Wednesday, March 14, 2012 7:16 PM Subject: Re: Failed make doc for Patchy James pkx1...@gmail.com writes: I am not at home but Patchy complained just now. Shall I run patchy and check the logfiles? -- Phil Holmes ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Failed make doc for Patchy
Phil Holmes m...@philholmes.net writes: - Original Message - From: David Kastrup d...@gnu.org To: lilypond-devel@gnu.org Sent: Wednesday, March 14, 2012 7:16 PM Subject: Re: Failed make doc for Patchy James pkx1...@gmail.com writes: I am not at home but Patchy complained just now. Shall I run patchy and check the logfiles? I am currently running make doc, but it does not look like it is going to finish fast. But I am going to bed now, so when I look next, it might be finished. It is not a build from an empty tree, though, just from make all doc-clean doc. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Failed make doc for Patchy
David Kastrup d...@gnu.org writes: Phil Holmes m...@philholmes.net writes: - Original Message - From: David Kastrup d...@gnu.org To: lilypond-devel@gnu.org Sent: Wednesday, March 14, 2012 7:16 PM Subject: Re: Failed make doc for Patchy James pkx1...@gmail.com writes: I am not at home but Patchy complained just now. Shall I run patchy and check the logfiles? I am currently running make doc, but it does not look like it is going to finish fast. But I am going to bed now, so when I look next, it might be finished. It is not a build from an empty tree, though, just from make all doc-clean doc. It is commit bb726728d07f5d155e061b360101028c4a4618e8 Author: Carl c_soren...@byu.edu Date: Sat Mar 10 11:47:54 2012 -0700 Fix make error in regression tests coming from midi2ly I have been unable to complete make test-baseline because of errors in the files coming from midi2ly.py. I tracked the error to make/midi-rules.make. The change in this patch allows me to successfully complete make test-baseli my computer, running OSX 10.5.8, with GNU Make 3.81. This change results in \\ in the headers getting reduced to just \ and that trips up TeX. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Failed make doc for Patchy
Hello,
On 14 March 2012 20:04, David Kastrup d...@gnu.org wrote:
Phil Holmes m...@philholmes.net writes:
- Original Message -
From: David Kastrup d...@gnu.org
To: lilypond-devel@gnu.org
Sent: Wednesday, March 14, 2012 7:16 PM
Subject: Re: Failed make doc for Patchy
James pkx1...@gmail.com writes:
I am not at home but Patchy complained just now.
Shall I run patchy and check the logfiles?
I've just done it and I get this file that causes the complaints
--snip--
%
% Start cut--pastable-section
%
\paper {
indent = 0\mm
line-width = 160\mm
% offset the left padding, also add 1mm as lilypond creates cropped
% images with a little space on the right
line-width = #(- line-width (* mm 3.00) (* mm 1))
}
\layout {
}
%
% ly snippet:
%
\sourcefilename out-www/voice-2-midi.ly
\sourcefileline 0
% Lily was here -- automatically converted by
/home/james/lilypond-git/scripts/midi2ly.py from out-www/voice-2.midi
\version 2.14.0
\layout {
\context {
\Voice
\remove Note_heads_engraver
\consists Completion_heads_engraver
\remove Rest_engraver
\consists Completion_rest_engraver
}
}
% included from ./out-www/voice-2.header
\header {
texidoc=midi2ly maps two voices nicely on one staff as oiceOne, oiceTwo
options=
}
% end
trackAchannelA = {
% [SEQUENCE_TRACK_NAME] control track
% [TEXT_EVENT] creator:
% [TEXT_EVENT] GNU LilyPond 2.15.34
\time 4/4
\tempo 4 = 60
}
trackA =
\context Voice = voiceA \trackAchannelA
trackBchannelA = {
\set Staff.instrumentName = trackB:voiceA
}
trackBchannelB = {
\set Staff.instrumentName = trackB:voiceB
}
trackBchannelC = \relative c {
\voiceOne
e''4 e e e
| % 2
}
trackBchannelD = \relative c {
\voiceTwo
f' f f f
| % 2
}
trackB =
\context Voice = voiceA \trackBchannelA
\context Voice = voiceB \trackBchannelB
\context Voice = voiceC \trackBchannelC
\context Voice = voiceD \trackBchannelD
\score {
\context Staff=trackB \trackA
\context Staff=trackB \trackB
\layout {}
\midi {}
}
%
% end ly snippet
%
--snip--
--
--
James
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Failed make doc for Patchy
James pkx1...@gmail.com writes: Hello, On 14 March 2012 20:04, David Kastrup d...@gnu.org wrote: Phil Holmes m...@philholmes.net writes: - Original Message - From: David Kastrup d...@gnu.org To: lilypond-devel@gnu.org Sent: Wednesday, March 14, 2012 7:16 PM Subject: Re: Failed make doc for Patchy James pkx1...@gmail.com writes: I am not at home but Patchy complained just now. Shall I run patchy and check the logfiles? I've just done it and I get this file that causes the complaints Yup, echo turns \v into vertical tab. Really daft. bb726728d07f5d155e061b360101028c4a4618e8 will need to get done differently. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Failed make doc for Patchy
David Kastrup d...@gnu.org writes: James pkx1...@gmail.com writes: Hello, On 14 March 2012 20:04, David Kastrup d...@gnu.org wrote: Phil Holmes m...@philholmes.net writes: - Original Message - From: David Kastrup d...@gnu.org To: lilypond-devel@gnu.org Sent: Wednesday, March 14, 2012 7:16 PM Subject: Re: Failed make doc for Patchy James pkx1...@gmail.com writes: I am not at home but Patchy complained just now. Shall I run patchy and check the logfiles? I've just done it and I get this file that causes the complaints Yup, echo turns \v into vertical tab. Really daft. bb726728d07f5d155e061b360101028c4a4618e8 will need to get done differently. I backed it out of staging. Try again. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Failed make doc for Patchy
On 3/14/12 3:12 PM, David Kastrup d...@gnu.org wrote: I backed it out of staging. Try again. Thanks, David. I guess if I figure out another fix, I'll have to try it on lilydev to make sure it works there as well as here. Carl ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Failed make doc for Patchy
Carl Sorensen c_soren...@byu.edu writes: On 3/14/12 3:12 PM, David Kastrup d...@gnu.org wrote: I backed it out of staging. Try again. Thanks, David. I guess if I figure out another fix, I'll have to try it on lilydev to make sure it works there as well as here. Afraid so. bash has no problem with echo '\v', but dash, the default /bin/sh in Ubuntu, cranks out a vertical tab. And the MacOSX /bin/sh is the first shell I heard of that does not grok echo -n. Autoconf offers the following in portable shell programming: `echo' The simple `echo' is probably the most surprising source of portability troubles. It is not possible to use `echo' portably unless both options and escape sequences are omitted. Don't expect any option. Do not use backslashes in the arguments, as there is no consensus on their handling. For `echo '\n' | wc -l', the `sh' of Solaris outputs 2, but Bash and Zsh (in `sh' emulation mode) output 1. The problem is truly `echo': all the shells understand `'\n'' as the string composed of a backslash and an `n'. Within a command substitution, `echo 'string\c'' will mess up the internal state of ksh88 on AIX 6.1 so that it will print the first character `s' only, followed by a newline, and then entirely drop the output of the next echo in a command substitution. Because of these problems, do not pass a string containing arbitrary characters to `echo'. For example, `echo $foo' is safe only if you know that FOO's value cannot contain backslashes and cannot start with `-'. If this may not be true, `printf' is in general safer and easier to use than `echo' and `echo -n'. Thus, scripts where portability is not a major concern should use `printf '%s\n'' whenever `echo' could fail, and similarly use `printf %s' instead of `echo -n'. For portable shell scripts, instead, it is suggested to use a here-document like this: cat EOF $foo EOF Alternatively, M4sh provides `AS_ECHO' and `AS_ECHO_N' macros which choose between various portable implementations: `echo' or `print' where they work, `printf' if it is available, or else other creative tricks in order to work around the above problems. The problem with a here-document is that it requires passing newlines into the shell script, and that is something that Make does not care for. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Failed make doc for Patchy
On Wed, Mar 14, 2012 at 10:27:52PM +0100, David Kastrup wrote: And the MacOSX /bin/sh is the first shell I heard of that does not grok echo -n. ... If this may not be true, `printf' is in general safer and easier to use than `echo' and `echo -n'. This matches the open group specifications. http://pubs.opengroup.org/onlinepubs/009695399/utilities/echo.html ... APPLICATION USAGE It is not possible to use echo portably across all POSIX systems unless both -n (as the first argument) and escape sequences are omitted. The printf utility can be used portably to emulate any of the traditional behaviors of the echo utility as follows (assuming that IFS has its standard value or is unset): The historic System V echo and the requirements on XSI implementations in this volume of IEEE Std 1003.1-2001 are equivalent to: printf %b\n $* The BSD echo is equivalent to: if [ X$1 = X-n ] then shift printf %s $* else printf %s\n $* fi New applications are encouraged to use printf instead of echo. - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Failed make doc for Patchy
Graham Percival gra...@percival-music.ca writes:
On Wed, Mar 14, 2012 at 10:27:52PM +0100, David Kastrup wrote:
And the MacOSX /bin/sh is the first shell I heard of that does not grok
echo -n.
...
If this may not be true, `printf' is in general safer and easier
to use than `echo' and `echo -n'.
This matches the open group specifications.
http://pubs.opengroup.org/onlinepubs/009695399/utilities/echo.html
...
APPLICATION USAGE
It is not possible to use echo portably across all POSIX
systems unless both -n (as the first argument) and escape
sequences are omitted.
Actually:
git grep echo -n
make/midi-rules.make: (echo '\header {'; for f in $(HEADER_FIELDS); do echo -n
mf/GNUmakefile: echo -n 'emmentaler-brace' $@
scripts/build/install-info-html.sh:echo -n $name: Writing index: $index_file...
smart-autogen.sh:echo -n $AUTOGEN_INPUT_CHECKSUM $CHECKSUM_FILE
smart-configure.sh:echo -n $CONFIGURE_CHECKSUM $CONFIGURE_CHECKSUM_FILE
stepmake/bin/stepmakeise.sh:echo -n Checking version...
stepmake/bin/stepmakeise.sh:echo -n Checking latest...
stepmake/bin/stepmakeise.sh:echo -n Updating StepMake...
stepmake/bin/stepmakeise.sh:echo -n Stepmakeising...
Wonderful.
--
David Kastrup
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
