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 <brentanna...@gmail.com> wrote: > 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. > On Thu, 10 May 2018 at 6:55 am, Michael Gerdau <m...@qata.de> wrote: > >> > 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 general. >> >> I'm not very knowledgeable w/r to GUB. So here is a question for those >> with better knowledge: >> Is it possible to reduce the required packages for GUB for particular >> software (as in lilypond)? >> >> If that's the case I'd expect it to be fairly straight forward to >> replace the mingw stuff by mingw-w64 since the later is (or was) >> supposed to be a dropin replacement for the former. >> >> Kind regards, >> Michael >> -- >> Michael Gerdau email: m...@qata.de >> GPG-keys available on request or at public keyserver >> >> _______________________________________________ >> lilypond-user mailing list >> lilypond-user@gnu.org >> https://lists.gnu.org/mailman/listinfo/lilypond-user >> >
_______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
