Re: broken doc build (orchestra.ly)

Knut Petersen writes: > "make doc" succeeds again, at least here. > > [newer versions]: make doc succeeds > dbaf1e56e37be0e204231c5bf1adcb14bd8ac3b8: fixes "make doc" failure here Ugh, I forgot to make this a merge commit. The preceding commit does not compile on its

Re: broken doc build (orchestra.ly)

"make doc" succeeds again, at least here. [newer versions]: make doc succeeds dbaf1e56e37be0e204231c5bf1adcb14bd8ac3b8: fixes "make doc" failure here 4b4a2cae9953cff69159f10763e990f5e4265ddd: lilypond does not build cccd7f9574c72ccecca00641d7a5ea3e8ce99cfd: still broken "make doc" [...]

Re: broken doc build (orchestra.ly)

David, On 25/05/16 14:43, David Kastrup wrote: David Kastrup writes: James writes: David On 24/05/16 18:20, David Kastrup wrote: James Lowe writes: No core file was generated, I also upped the ulimit to 1GB. So perhaps it isn't the type of

Re: broken doc build (orchestra.ly)

Knut Petersen writes: Knut, did you use any options to ./configure ? config.log should mention how configure was called. > doit "../configure --prefix=$MYROOT" Ok, so no options at all. -- David Kastrup ___

Re: broken doc build (orchestra.ly)

Am 25.05.2016 um 16:14 schrieb David Kastrup: What about current master? More exactly, did 56a1519b44d1a0a8500c43236ae644053cc1f25b make a difference? No, both 56a1519b4 and a1467ba6de6 fail to process orchestra.ly. More tomorrow. Knut ___

Re: broken doc build (orchestra.ly)

Am 25.05.2016 um 15:58 schrieb Phil Holmes: Knut, did you use any options to ./configure ? config.log should mention how configure was called. I use the following script to build lilypond: RED='\033[0;31m' NOC='\033[0m' function doit { AT=`date +"%s"` echo -en exec $RED$1$NOC in `pwd`

Re: broken doc build (orchestra.ly)

Knut Petersen writes: > Am 20.05.2016 um 17:27 schrieb David Kastrup: >> David Kastrup writes: >> >>> Can you run this under a debugger and place a breakpoint on >>> Scheme_engraver::init_from_scheme or just write abort(); as its first >>> line? I want

Re: broken doc build (orchestra.ly)

- Original Message - From: "David Kastrup" <d...@gnu.org> To: "James" <p...@gnu.org> Cc: <lilypond-devel@gnu.org> Sent: Wednesday, May 25, 2016 2:43 PM Subject: Re: broken doc build (orchestra.ly) David Kastrup <d...@gnu.org> writes: James

Re: broken doc build (orchestra.ly)

David Kastrup writes: > James writes: > >> David >> >> On 24/05/16 18:20, David Kastrup wrote: >>> James Lowe writes: >>> No core file was generated, I also upped the ulimit to 1GB. So perhaps it isn't the type of 'assertion' or crash

Re: broken doc build (orchestra.ly)

James writes: > David > > On 24/05/16 18:20, David Kastrup wrote: >> James Lowe writes: >> >>> No core file was generated, I also upped the ulimit to 1GB. >>> >>> So perhaps it isn't the type of 'assertion' or crash you thought it >>> was after all? >> Perhaps.

Re: broken doc build (orchestra.ly)

David On 24/05/16 18:20, David Kastrup wrote: James Lowe writes: No core file was generated, I also upped the ulimit to 1GB. So perhaps it isn't the type of 'assertion' or crash you thought it was after all? Perhaps. Knut's problem, however, sounded like it. If you have

Re: broken doc build (orchestra.ly)

David On 24/05/16 18:20, David Kastrup wrote: James Lowe writes: No core file was generated, I also upped the ulimit to 1GB. So perhaps it isn't the type of 'assertion' or crash you thought it was after all? Perhaps. Knut's problem, however, sounded like it. If you have

Re: broken doc build (orchestra.ly)

James Lowe writes: > No core file was generated, I also upped the ulimit to 1GB. > > So perhaps it isn't the type of 'assertion' or crash you thought it > was after all? Perhaps. Knut's problem, however, sounded like it. If you have different results from Knut, things are even

Re: broken doc build (orchestra.ly)

Am 20.05.2016 um 17:27 schrieb David Kastrup: David Kastrup writes: Can you run this under a debugger and place a breakpoint on Scheme_engraver::init_from_scheme or just write abort(); as its first line? I want to know whether the problem is triggered _without_ creating a

Re: broken doc build (orchestra.ly)

David, On 22/05/16 13:08, David Kastrup wrote: James Lowe writes: My make doc issue has come back :( Taking a few more minutes to try and diagnose the problem - it is the same again, as Knut had. With the same error on processing orchestra.ly. Bah. Let's try getting a post

Re: broken doc build (orchestra.ly)

James Lowe writes: > OK I'll give that a go and roll back to the commit just before all the > 4842/* ones - in case I cannot just roll back to before the 4842/6 and > not break something dependent in the other 4842 changes. All of the commits should compile fine (or I'd have put

Re: broken doc build (orchestra.ly)

On 22/05/16 13:04, Phil Holmes wrote: - Original Message - From: "James Lowe" <p...@gnu.org> To: "David Kastrup" <d...@gnu.org> Cc: <lilypond-devel@gnu.org> Sent: Sunday, May 22, 2016 12:53 PM Subject: Re: broken doc build (orchestra.ly) On 21/05

Re: broken doc build (orchestra.ly)

"Phil Holmes" writes: > I think it's likely to be what David was guessing at - David's "Issue > 4842/6: Don't special-case Scheme_engraver's acknowledgers" has > affected garbage collection somehow, and this affects different > systems in different ways, because of the way

Re: broken doc build (orchestra.ly)

James Lowe writes: > My make doc issue has come back :( > > Taking a few more minutes to try and diagnose the problem - it is the > same again, as Knut had. With the same error on processing > orchestra.ly. Bah. Let's try getting a post mortem backtrace from it. Basically, you

Re: broken doc build (orchestra.ly)

- Original Message - From: "James Lowe" <p...@gnu.org> To: "David Kastrup" <d...@gnu.org> Cc: <lilypond-devel@gnu.org> Sent: Sunday, May 22, 2016 12:53 PM Subject: Re: broken doc build (orchestra.ly) On 21/05/16 10:38, David Kastrup wrote: Jam

Re: broken doc build (orchestra.ly)

On 21/05/16 10:38, David Kastrup wrote: James Lowe writes: David, On 20/05/16 17:38, David Kastrup wrote: James writes: I don;t know what the lilypond.pot stuff does but could that have been the problem? Unlikely. I think it may be the distribution of files

Re: broken doc build (orchestra.ly)

> This change, however, affected cross-references and index entries. Ah, ok. > With regard to the text changes: I don't actually know whether the > correct Finnish word is kaksoisappogiatura or kaksoisappoggiatura > but am willing to believe the latter. I looked it up :-) While I couldn't

Re: broken doc build (orchestra.ly)

David, On 21/05/16 10:38, David Kastrup wrote: James Lowe writes: David, On 20/05/16 17:38, David Kastrup wrote: James writes: I don;t know what the lilypond.pot stuff does but could that have been the problem? Unlikely. I think it may be the distribution

Re: broken doc build (orchestra.ly)

Werner LEMBERG writes: >> At any rate, Werner had pushed a spelling correction commit that >> ended up staying in staging for a long time (days I think) but >> then got passed to master pretty fast once _another_ commit was >> pushed on top of it. > > I hope it is OK to push

Re: broken doc build (orchestra.ly)

> At any rate, Werner had pushed a spelling correction commit that > ended up staying in staging for a long time (days I think) but > then got passed to master pretty fast once _another_ commit was > pushed on top of it. I hope it is OK to push such minor tweaks without creating an issue.

Re: broken doc build (orchestra.ly)

James Lowe writes: > David, > > On 20/05/16 17:38, David Kastrup wrote: >> James writes: >> >>> I don;t know what the lilypond.pot stuff does but could that have been >>> the problem? >> Unlikely. I think it may be the distribution of files across parallel >>

Re: broken doc build (orchestra.ly)

David, On 20/05/16 17:38, David Kastrup wrote: James writes: I don;t know what the lilypond.pot stuff does but could that have been the problem? Unlikely. I think it may be the distribution of files across parallel builds, where the few snippets using the Scheme_engraver

Re: broken doc build (orchestra.ly)

James writes: > I don;t know what the lilypond.pot stuff does but could that have been > the problem? Unlikely. I think it may be the distribution of files across parallel builds, where the few snippets using the Scheme_engraver poison the session so that it crashes during an

Re: broken doc build (orchestra.ly)

Knut, On 20/05/16 10:34, Phil Holmes wrote: - Original Message - From: "Knut Petersen" <knut_peter...@t-online.de> To: <lilypond-devel@gnu.org> Sent: Friday, May 20, 2016 9:56 AM Subject: broken doc build (orchestra.ly) Hi everybody! Building the curre

Re: broken doc build (orchestra.ly)

David Kastrup writes: > David Kastrup writes: > > [Bisection] > >>> Commit c1d7bc2217462a63bf5c5c6d6f6df5cb00099180 >>> Author: David Kastrup >>> Date: Tue May 3 19:11:15 2016 +0200 >>> >>> Issue 4842/6: Don't special-case Scheme_engraver's

Re: broken doc build (orchestra.ly)

David Kastrup writes: [Bisection] >> Commit c1d7bc2217462a63bf5c5c6d6f6df5cb00099180 >> Author: David Kastrup >> Date: Tue May 3 19:11:15 2016 +0200 >> >> Issue 4842/6: Don't special-case Scheme_engraver's acknowledgers >> >> >>

Re: broken doc build (orchestra.ly)

Knut Petersen writes: > Am 20.05.2016 um 14:20 schrieb David Kastrup: >> Knut Petersen writes: >> >>> Hi everybody! >>> >>> Building the current git lilypond binary succeeds, but building the >>> documentation is broken even if I try a

Re: broken doc build (orchestra.ly)

Am 20.05.2016 um 15:50 schrieb Knut Petersen: Am 20.05.2016 um 14:20 schrieb David Kastrup: Knut Petersen writes: Hi everybody! Building the current git lilypond binary succeeds, but building the documentation is broken even if I try a single core build. [...]

Re: broken doc build (orchestra.ly)

Am 20.05.2016 um 14:20 schrieb David Kastrup: Knut Petersen writes: Hi everybody! Building the current git lilypond binary succeeds, but building the documentation is broken even if I try a single core build. [...] So there really is a lot of "Huh?" involved

Re: broken doc build (orchestra.ly)

Knut Petersen writes: > Hi everybody! > > Building the current git lilypond binary succeeds, but building the > documentation is broken even if I try a single core build. > > > exec ./autogen.sh --noconfigure in /home/knut/sources/lily > ... succeeded after 1 seconds >

Re: broken doc build (orchestra.ly)

- Original Message - From: "Knut Petersen" <knut_peter...@t-online.de> To: <lilypond-devel@gnu.org> Sent: Friday, May 20, 2016 9:56 AM Subject: broken doc build (orchestra.ly) Hi everybody! Building the current git lilypond binary succeeds, but building the d

broken doc build (orchestra.ly)

Hi everybody! Building the current git lilypond binary succeeds, but building the documentation is broken even if I try a single core build. exec ./autogen.sh --noconfigure in /home/knut/sources/lily ... succeeded after 1 seconds exec ../configure --prefix=/home/knut/sources/lilybuilt/ in