----- Original Message -----
From: "David Kastrup" <d...@gnu.org>
To: "Phil Holmes" <m...@philholmes.net>
Cc: "Jonas Hahnfeld" <hah...@hahnjo.de>; "Dan Eble" <d...@faithful.be>;
"Masamichi Hosoda" <truer...@trueroad.jp>; <arnold.we...@siemens.com>;
<lilypond-devel@gnu.org>
Sent: Tuesday, February 04, 2020 5:34 PM
Subject: Re: Inline assembler fallback for _FPU_SETCW() missing in MINGW
libraries (issue 577450043 by thomasmorle...@gmail.com)
"Phil Holmes" <m...@philholmes.net> writes:
----- Original Message ----- From: "David Kastrup" <d...@gnu.org>
Wow. Ok, maybe I'll just apply this patch then (though I'll at
least
remove the conditioning on Apple here as the problem is rather likely
platform independent) and Phil may have another round.
--
David Kastrup
Will kick this off again tomorrow.
Thanks!
--
David Kastrup
The build completed successfully, as did the upload, so anyone looking at
the manuals on lilypond.org will see 19.84 information. However, the
website has not built, I think because VERSION in master has not been
updated. I've pushed an updated VERSION to staging, but my patchy refuses
to run because I have a too -old version of Python. Python -V gives 2.7.6.
Could someone:
1. Tell me a safe method for getting Python >3.5 on Ubuntu 14.04, please?
2. Possibly run patchy-staging
Thanks
--
Phil Holmes