Re: Fwd: Compile crashing... help!

FWIW, I just tried this out on my decrepit Windows 7 machine (64-bit, 8GB, i7 core). After about 8 minutes of whizzing and whirring at 12% CPU capacity and utilising just under 5 GB of RAM, it returned the same error. Brent. On Thu, 10 May 2018 at 1:14 pm, Brent Annable

Re: Fwd: Compile crashing... help!

Being a layman, most of this is all going over my head. But I gather that compiling this particular project will not be possible for the time being on my current machine, so I’ll either try to get my decrepit laptop up and running, or ask a friend to help out :-) Thanks for the replies, Brent.

Re: Fwd: Compile crashing... help!

> I have no idea what it would entail to also provide 64bit Windows > binaries. Last time I looked (about 1.5 years ago) the problem was a missing mingw-w64 package that exists for mingw (the 32bit version) for which I think it is not actually required for the lilypond build, only for GUB in

Re: Fwd: Compile crashing... help!

Samuel Speer writes: > On Wed, May 9, 2018 at 10:44 AM David Kastrup wrote: > >> 1.82G is a bit of a strange number for a 64bit binary. Are you using a >> 64bit Windows and definitely a 64bit LilyPond (!) executable? >> > > I checked my executable and it

Re: Release schedule for 2.20

>> What about setting up GUB (with LilyPond) on >> https://hydra.nixos.org/? Other GNU projects like Emacs are also >> hosted there for daily builds, so it should be easy to get lilypond >> registered there... >> >> https://nixos.org/hydra/ > > Are you going to do it? Basically, I'm

Re: Fwd: Compile crashing... help!

On Wed, May 9, 2018 at 10:44 AM David Kastrup wrote: > 1.82G is a bit of a strange number for a 64bit binary. Are you using a > 64bit Windows and definitely a 64bit LilyPond (!) executable? > I checked my executable and it looks to be 32-bit. However, I couldn't find a 64-bit

Re: Compile crashing... help!

Not much help, but the source seems o.k. MacBook Air (2013), 4GB Ram, OS 10.13.4- for what it’s worth, compiled the file successfully and output a pdf of 104 pages. Stan > On May 9, 2018, at 11:17 AM, tyronicus wrote: > > Phil Holmes wrote >> My guess is that there's a

Re: Fwd: Compile crashing... help!

On 09/05/18 15:42, Karlin High wrote: On 5/9/2018 8:16 AM, Ben wrote: I also ran into your issue by compiling "SG_complete_DE.ly" on my Windows 10 machine. 32GB RAM. Newest i7 build. Curiouser and curiouser... It compiled successfully on my Windows 7 Pro x64 SP1, Intel Core i5-3450, 24 GB

Re: Fwd: Compile crashing... help!

tyronicus writes: > Phil Holmes wrote >> My guess is that there's a memory allocation problem that only shows up on >> large projects on Windows. > > That's my suspicion, too. I tried it on a Win10 i7-8xxx with 8G ram and saw > it cut out around 1.85G memory every time.

Re: Fwd: Compile crashing... help!

Phil Holmes wrote > My guess is that there's a memory allocation problem that only shows up on > large projects on Windows. That's my suspicion, too. I tried it on a Win10 i7-8xxx with 8G ram and saw it cut out around 1.85G memory every time. When I remove two bookparts, it only uses 1.82G of

Re: Release schedule for 2.20

Werner LEMBERG writes: > What about setting up GUB (with LilyPond) on https://hydra.nixos.org/? > Other GNU projects like Emacs are also hosted there for daily > builds, so it should be easy to get lilypond registered there... > > https://nixos.org/hydra/ Are you going to do it?

Re: Release schedule for 2.20

> On my GUB build machine (4 core hyperthreaded i7, 8 Gigs, SSD) an > incremental build (i.e. with a stable version of GUB with the > toolset all up to date) takes around one to one and a half hours. > If GUB needs updating, it can, as you say, take over 6 hours even on > that machine. The

Re: Release schedule for 2.20

Am 09.05.2018 um 17:23 schrieb Phil Holmes: Question: How difficult/costly/... would it be to prepare a "daily build from current master" for download? Very.  We are talking about 6 hours of build time on a pretty solidly powered 8-processor machine.  Actually, we _were_ talking about that

Re: Release schedule for 2.20

- Original Message - From: "David Kastrup" To: "Lukas-Fabian Moser" Cc: "lilypond-user" ; Sent: Wednesday, May 09, 2018 4:11 PM Subject: Re: Release schedule for 2.20 Lukas-Fabian Moser writes:

Re: Release schedule for 2.20

Lukas-Fabian Moser writes: > (I, for example, just recently switched to self-compiled Lilypond > because of Malte's amazing work on the \haydnTurn which was prompted > by my question. To my surprise, compiling turned out to be quite easy, > but of course there /were /some slight

Re: Release schedule for 2.20

- Original Message - From: "Lukas-Fabian Moser" To: ; "lilypond-user" Sent: Wednesday, May 09, 2018 3:09 PM Subject: Re: Release schedule for 2.20 But an increasing number of questions asked in forums or on the lists can

Re: Fwd: Compile crashing... help!

Might be simplest to create a Linux VM on the Windows box and use that for very big projects. My guess is that there's a memory allocation problem that only shows up on large projects on Windows. -- Phil Holmes - Original Message - From: Brent Annable To: David Kastrup Cc:

Re: Fwd: Compile crashing... help!

On 5/9/2018 8:16 AM, Ben wrote: I also ran into your issue by compiling "SG_complete_DE.ly" on my Windows 10 machine. 32GB RAM. Newest i7 build. Curiouser and curiouser... It compiled successfully on my Windows 7 Pro x64 SP1, Intel Core i5-3450, 24 GB RAM, LilyPond 2.19.80 -- Karlin High

Re: Re: Fwd: Compile crashing... help!

On 2018-05-09 15:59, Brent Annable wrote: Thanks everyone. Yeah I forgot to mention: I'm on a Windows 10 Thinkpad machine with i7 and 16GB RAM. So looks like the errors are coming through on the same systems. Sigh. What to do? I have an old laptop with a rocket-engine fan that I could

Re: Release schedule for 2.20

But an increasing number of questions asked in forums or on the lists can be answered by “compile current master or wait for 2.21.0”. And a huge number of answers requires at least 2.19.xx but people understandably don’t want to install an “unstable” version. IIUC, the situation used to be:

Re: Fwd: Compile crashing... help!

Brent Annable writes: > Thanks everyone. Yeah I forgot to mention: I'm on a Windows 10 Thinkpad > machine with i7 and 16GB RAM. So looks like the errors are coming through > on the same systems. > > Sigh. What to do? I have an old laptop with a rocket-engine fan that I >

Re: Fwd: Compile crashing... help!

On 5/9/2018 9:59 AM, Brent Annable wrote: Thanks everyone. Yeah I forgot to mention: I'm on a Windows 10 Thinkpad machine with i7 and 16GB RAM. So looks like the errors are coming through on the same systems. Sigh. What to do? I have an old laptop with a rocket-engine fan that I could

Re: Fwd: Compile crashing... help!

Thanks everyone. Yeah I forgot to mention: I'm on a Windows 10 Thinkpad machine with i7 and 16GB RAM. So looks like the errors are coming through on the same systems. Sigh. What to do? I have an old laptop with a rocket-engine fan that I could try Brent. On 9 May 2018 at 23:28, David

Re: Fwd: Compile crashing... help!

Ben writes: > On 5/9/2018 8:35 AM, Brent Annable wrote: >> Hi everyone, >> >> I'm trying to compile a very large project, it keeps crashing and >> I'm at a loss as to the cause. Some details: >> >> - The error first appears as a Windows notification saying: " >>

Re: Fwd: Compile crashing... help!

Am 09.05.2018 um 15:16 schrieb Ben: I also ran into your issue by compiling "SG_complete_DE.ly" on my Windows 10 machine. 32GB RAM. Newest i7 build. So, there is some consistency...I see the same errors you do. However, I compiled your project successfully (and quite fast) on my Linux Mint

Re: Fwd: Compile crashing... help!

On 5/9/2018 8:35 AM, Brent Annable wrote: Hi everyone, I'm trying to compile a very large project, it keeps crashing and I'm at a loss as to the cause. Some details: - The error first appears as a Windows notification saying: " Runtime error! This application has requested the Runtime to

Re: Release schedule for 2.20

Am 9. Mai 2018 12:18:37 MESZ schrieb Aaron Hill : >On 2018-05-09 02:49, Malte Meyn wrote: >> But an increasing number of questions asked in forums or on the lists >> can be answered by “compile current master or wait for 2.21.0”. And a >> huge number of answers requires

Re: variable and tie

Gianmaria Lari writes: > On 9 May 2018 at 10:45, David Kastrup wrote: > >> Gianmaria Lari writes: >> >> > On 13 April 2018 at 09:13, David Kastrup wrote: >> > >> >> Gianmaria Lari writes:

Re: Release schedule for 2.20

On 2018-05-09 02:49, Malte Meyn wrote: But an increasing number of questions asked in forums or on the lists can be answered by “compile current master or wait for 2.21.0”. And a huge number of answers requires at least 2.19.xx but people understandably don’t want to install an “unstable”

Re: variable and tie

On 9 May 2018 at 10:45, David Kastrup wrote: > Gianmaria Lari writes: > > > On 13 April 2018 at 09:13, David Kastrup wrote: > > > >> Gianmaria Lari writes: > >> > > >> > At the moment I do this > >> > > >> >

Re: Release schedule for 2.20

Am 09.05.2018 um 11:16 schrieb David Kastrup: Aaron Hill writes: Hi folks, It would seem the release of version 2.20 must be nearing, but I have not found anything published about the release schedule for the project. There isn't one. [CC-ing to

Re: Release schedule for 2.20

- Original Message - From: "David Kastrup" To: "Aaron Hill" Cc: Sent: Wednesday, May 09, 2018 10:16 AM Subject: Re: Release schedule for 2.20 Aaron Hill writes: Hi folks, It would seem the

Re: Release schedule for 2.20

Aaron Hill writes: > Hi folks, > > It would seem the release of version 2.20 must be nearing, but I have > not found anything published about the release schedule for the > project. There isn't one. > The website mentions following the info-lilyp...@gnu.org mailing

Release schedule for 2.20

Hi folks, It would seem the release of version 2.20 must be nearing, but I have not found anything published about the release schedule for the project. The website mentions following the info-lilyp...@gnu.org mailing list, but according to the archives that list hasn't seen a post in years.

Re: disabling \break

If you want a more lightweight way to do it, this function should also work: ⋘ removeBreaks = #(define-music-function (mus) (ly:music?) (music-filter (lambda (v) (not (music-is-of-type? v 'break-event))) mus)) ⋙ On 05/08/18 14:17, Jan-Peter Voigt wrote: > Hi Herbie, > >

Re: variable and tie

Gianmaria Lari writes: > On 13 April 2018 at 09:13, David Kastrup wrote: > >> Gianmaria Lari writes: >> > >> > At the moment I do this >> > >> > \version "2.19.81" >> > var = {a b \tag #'lastnote a} >> > {\removeWithTag #'lastnote

Re: variable and tie

On 13 April 2018 at 09:13, David Kastrup wrote: > Gianmaria Lari writes: > > > I would like to tie the last note contained in a variable like this > > > > \version "2.19.81" > > var = {a b a} > > {\var ~ a} > > > > but this generates an error. This is just