Dear all, And thanks Marnen!
I’ve posted my logfiles at the gitlab issue to avoid spam on the mailing list: https://gitlab.com/marnen/lilypond-mac-builder/-/issues/16 <https://gitlab.com/marnen/lilypond-mac-builder/-/issues/16> I'm just coming back to this after a few days doing other stuff. I've read several issues that deal with similiar problems when a library is called on macOS Catalina. E.g.: https://github.com/mpv-player/mpv/issues/7053#issuecomment-541459793 <https://github.com/mpv-player/mpv/issues/7053#issuecomment-541459793> Could it be related to that? Best, Moritz > Am 02.04.2020 um 16:48 schrieb Marnen Laibow-Koser <mar...@marnen.org>: > > > > On Thu, Apr 2, 2020 at 10:38 AM Moritz Heffter <mxo...@me.com > <mailto:mxo...@me.com>> wrote: > Dear Marnen, > > Thanks for providing 64-bit versions of lilypond. I recently updated to macOS > Catalina and was looking for exactly that. > > You’re welcome! > > > Unfortunatly, each time I try to use the LilyPond.app I’ve been running into > segmentation faults. I’ve discussed this with Hans Åberg on the lilypond user > mailing list: > > https://lists.gnu.org/archive/html/lilypond-user/2020-03/msg00224.html > <https://lists.gnu.org/archive/html/lilypond-user/2020-03/msg00224.html> > > First of all, please keep discussion on the lists or other forums rather than > private e-mail. That way we all can benefit and contribute. > > <https://lists.gnu.org/archive/html/lilypond-user/2020-03/msg00224.html> > > Is this a known issue or do you know anything I could try? My Machine is a > new 2019 MacBook Pro 13’’ 16/512 i5 1,4 with Catalina 10.15.4. I’ve also brew > and MacPorts installed. > > You’re only the second user to report something like this, and we don’t know > what causes it yet; see > https://gitlab.com/marnen/lilypond-mac-builder/-/issues/16 > <https://gitlab.com/marnen/lilypond-mac-builder/-/issues/16> for more > information (and run Lily verbose as described there so we can make sure it’s > the same problem). I’ve brought it up with the Guile list, but they’ve asked > for further debugging information, which the other affected user has not yet > been able to provide; see > https://debbugs.gnu.org/cgi/bugreport.cgi?bug=39863 > <https://debbugs.gnu.org/cgi/bugreport.cgi?bug=39863> . Perhaps you can > follow the instructions there and provide this debugging info to the Guile > folks? > > > Best, > Moritz > > Best, > -- > Marnen Laibow-Koser mar...@marnen.org <mailto:mar...@marnen.org> > http://www.marnen.org <http://www.marnen.org/> Sent from Gmail Mobile
