On Thu, Apr 2, 2020 at 1:49 PM Carl Sorensen <c_soren...@byu.edu> wrote:
> > > > > *From: *Marnen Laibow-Koser <mar...@marnen.org> > *Date: *Thursday, April 2, 2020 at 11:07 AM > *To: *Carl Sorensen <c_soren...@byu.edu> > *Cc: *LilyPond Users <lilypond-user@gnu.org>, Moritz Heffter < > mxo...@me.com> > *Subject: *Re: Lilypond 64-bit binaries > > > > > > > > On Thu, Apr 2, 2020 at 1:02 PM Carl Sorensen <c_soren...@byu.edu> wrote: > > I note that Moritz mentions he gets the same results from the MacPorts > build. Perhaps the MacPorts people could provide some insight. > > > > Hmm. I wonder if I should try using a more recent version of Mac OS and > Xcode on the build box. I was using the oldest possible version in order > to produce the most backward-compatible build. > > > > But...if this is a general issue with Catalina, why are so few users > affected by it, and why are users on Mojave among those affected? > > > > I don’t think it’s a general issue. I think it’s a specific issue, that > varies from machine to machine. My only suggestion was that perhaps > somebody in the MacPorts group might be able to provide some debugging > helps. Hopefully the issue is the same in MacPorts as in your app bundle, > so if it can be resolved in MacPorts it can be resolved in the app bundle…. > Yeah, that might be a good point. I think this is the first time we've seen a MacPorts build have this same problem. Also: it's not *my* bundle, except in that I figured out the process to build it. Ideally, it is the LilyPond project's bundle: I want this to be accepted into the core project, not remain my own personal thing. > > Carl > Best, -- Marnen Laibow-Koser mar...@marnen.org http://www.marnen.org
