On 2018-05-10 03:43, Aaron Hill wrote:
On 2018-05-10 01:04, Phil Holmes wrote:
Did you consider my suggestion of using a Linux virtual machine?
If you are running 64-bit Windows 10, remember that the Windows
Subsystem for Linux exists:
https://en.wikipedia.org/wiki/Windows_Subsystem_for_Linux
This seems like the easiest option to be able to run 64-bit build
LilyPond on Windows, until such time as mingw-w64 can be utilized by
LilyPond/GUB.
Obviously, one can run a full VM, but WSL is a much lighter-weight
option with fairly good support for command-line tools. I am in the
process of getting this set up myself for some work on other projects,
and I will report back my results.
And it works! I was able to compile Brent's original 194-page epic with
no problems apart from a missing glyph:
warning: no glyph for character U+201F in font
`/usr/local/lilypond/usr/share/lilypond/current/fonts/otf/texgyreschola-regular.otf'
This was done by following the installation guide here:
https://docs.microsoft.com/en-us/windows/wsl/install-win10
I opted for the Ubuntu distribution, but there are options for Debian,
openSUSE, and Kali as well.
After installation, I did `apt-get update` and `apt-get dist-upgrade`
which put me on 16.04.4 LTS. Then I installed the latest 64-bit
LilyPond for Linux:
http://lilypond.org/downloads/binaries/linux-64/lilypond-2.19.81-1.linux-64.sh
I also tested the stress snippet I posted to bug-lilypond that had
failed on the mingw-w32 build:
%%% stress.ly
\version "2.19.80"
\repeat unfold 36 {
<< { e'8 f' } \\ { c'4 } >> d'4
<< { g'4. f'8 } \\ { e'16 d' e'4 d'8 } >>
}
%%%
As expected, this worked just fine under WSL, even after upping the
repeats to 2048:
$ time lilypond stress.ly
. . .
[1968][1976][1984][1992][2000][2008][2016][2024][2032][2040][2048]
Preprocessing graphical objects...
Finding the ideal number of pages...
Fitting music on 39 or 40 pages...
Drawing systems...
Layout output to `/tmp/lilypond-QVyk9u'...
Converting to `stress.pdf'...
Deleting `/tmp/lilypond-QVyk9u'...
Success: compilation successfully completed
real 2m16.331s
user 1m56.906s
sys 0m15.547s
I was able to segfault with the repeats at 8192. But that might have
been an out-of-memory issue. I only have 6GB physical RAM, and I could
see that Windows had expanded the pagefile to nearly 24GB trying to
accommodate the ever-growing lilypond process.
[8120][8128][8136][8144][8152][8160][8168][8176][8184][8192]
Preprocessing graphical objects...Segmentation fault (core dumped)
While the average user is unlikely to go through this process, WSL does
seem to offer a reasonable stopgap until a working mingw-w64 build of
LilyPond is available.
-- Aaron Hill
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user