> On 7 Jul 2018, at 13:12, David Kastrup <[email protected]> wrote: > > Hans Åberg <[email protected]> writes: > >> There is a danger in using an older compiler that is not supported, as >> there might be bugs that are not going to be fixed. > > Well, that's the point, isn't it? If a significant amount of users have > no convenient choice avoiding that older compiler, we want to discover > any such bugs that are not going to be fixed in testing.
You are not likely to be very successful at that, as gcc is too big and complicated, but the tradeoff is ditching some older platforms, for sure. The current LilyPond binary won't run on the upcoming MacOS 10.14 as it is only 32-bit, I think. So not updating might cause it to not run on newer platforms. _______________________________________________ lilypond-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-devel
