> On 28 Mar 2020, at 13:14, Moritz Heffter wrote:
>
>> https://stackoverflow.com/questions/18758837/xcode-quit-unexpectedly-for-my-project-not-in-xcode-4-6-3
>
> But I found the following. In my my log files the issue occurs always with
> the same dylib:
> 85 libdyld.dylib 0x7fff6e
> On 28 Mar 2020, at 13:14, Moritz Heffter wrote:
>
>> https://stackoverflow.com/questions/18758837/xcode-quit-unexpectedly-for-my-project-not-in-xcode-4-6-3
>
> But I found the following. In my my log files the issue occurs always with
> the same dylib:
> 85 libdyld.dylib 0x7fff6e
>> On 27 Mar 2020, at 18:53, Moritz Heffter wrote:
>>
>>> Try in Terminal
>>> export PATH=/usr/bin:/bin:/usr/sbin:/sbin
>>>
>>> and then
>>> /opt/lilypond/bin/lilypond
>>
>> Hmm, I have done that, but unfortunately without progress.
>
> In the link below, the issue was solved by fixing the env
> On 27 Mar 2020, at 18:53, Moritz Heffter wrote:
>
>> Try in Terminal
>> export PATH=/usr/bin:/bin:/usr/sbin:/sbin
>>
>> and then
>> /opt/lilypond/bin/lilypond
>
> Hmm, I have done that, but unfortunately without progress.
In the link below, the issue was solved by fixing the environment
>> On 26 Mar 2020, at 19:03, Moritz Heffter wrote:
>>
>> Thanks for the information. I’ve reinstalled the 2.19 package and put
>> /opt/lilypond/bin in the PATH. I can execute lilypond from the Terminal
>> still getting the segmentation fault. But now with a different reason:
>>
>> Termination
> On 26 Mar 2020, at 19:03, Moritz Heffter wrote:
>
> Thanks for the information. I’ve reinstalled the 2.19 package and put
> /opt/lilypond/bin in the PATH. I can execute lilypond from the Terminal still
> getting the segmentation fault. But now with a different reason:
>
> Termination Sign
Thanks for the information. I’ve reinstalled the 2.19 package and put
/opt/lilypond/bin in the PATH. I can execute lilypond from the Terminal still
getting the segmentation fault. But now with a different reason:
Termination Signal:Segmentation fault: 11
Termination Reason:Namespace SIGN
> On 26 Mar 2020, at 12:57, Moritz Heffter wrote:
>
> BTW, /opt is in read-only mode. I’m not able to remove it.
One may have to give the Terminal app permissions, which I did in the past, but
it is not there now, so it may or may not be required.
https://osxdaily.com/2018/10/09/fix-operatio
You are running a brew-installed Lilypond, my dear ;-)
Try the following in a terminal:
$ /Applications/LilyPond.app/Contents/MacOS/LilyPond
Cheers, RalfD
Am Donnerstag, 26. März 2020 10:57 CET, Moritz Heffter
schrieb:
> The error is logged for lilypond-bin when I run lilypond from the Termi
> On 26 Mar 2020, at 12:57, Moritz Heffter wrote:
>
> Well this is bringing me one step further. I think the problem is that some
> libraries are not found. Especially guile.
>
> I’ve now completely removed macports (I’ve installed it only because of
> Lilypond) and reinstalled the Lilypond
Well this is bringing me one step further. I think the problem is that some
libraries are not found. Especially guile.
I’ve now completely removed macports (I’ve installed it only because of
Lilypond) and reinstalled the Lilypond package of version 2.19 from Hans again.
It installs into /opt/li
> On 26 Mar 2020, at 10:57, Moritz Heffter wrote:
>
> The error is logged for lilypond-bin when I run lilypond from the Terminal:
>
> Process: lilypond-bin [8616]
> Path: /opt/lilypond/*/lilypond-bin
> Identifier:lilypond-bin
> Version:
The error is logged for lilypond-bin when I run lilypond from the Terminal:
Process: lilypond-bin [8616]
Path: /opt/lilypond/*/lilypond-bin
Identifier:lilypond-bin
Version: 0
Code Type: X86-64 (Native)
Parent Process:zsh
> On 26 Mar 2020, at 10:36, Moritz Heffter wrote:
>
> Hum, I’ve tried out different settings now and also updated the system to the
> version 10.15.4 but it’s still the same error. I've also deactivated
> FileVault and gave.
>
> The log file says maybe a bit more precisely:
>
> Error Code:
Hum, I’ve tried out different settings now and also updated the system to the
version 10.15.4 but it’s still the same error. I've also deactivated FileVault
and gave.
The log file says maybe a bit more precisely:
Error Code: 0x0004 (no mapping for user data read)
Trap Number: 14
B
[Keep the cc to the list so other can follow the issue.]
> On 24 Mar 2020, at 11:45, Moritz Heffter wrote:
>
> My PATH variable shows the following:
>
> /Users/username/Library/Python/3.7/bin:/opt/local/bin:/opt/local/sbin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Library/TeX/texbin
>
> My
> On 24 Mar 2020, at 10:43, Moritz Heffter wrote:
>
> Hum, that mean some configuration on my machine is the problem? I use another
> package manager (brew). Could it be that there arise some incompatibilities?
It might, if you have stuff that overrides what lilypond expects to use. Check
in
Am Dienstag, den 24.03.2020, 10:43 +0100 schrieb Moritz Heffter:
> Hum, that mean some configuration on my machine is the problem? I use
> another package manager (brew). Could it be that there arise some
> incompatibilities?
>
I'd be intersted to know if there is _any_ correlation to your MkDocs
Hum, that mean some configuration on my machine is the problem? I use another
package manager (brew). Could it be that there arise some incompatibilities?
Best,
Moritz
> Am 24.03.2020 um 10:18 schrieb Hans Åberg :
>
> The MacPorts 2.19.84 installer was made on essentially the same hardware.
>
The MacPorts 2.19.84 installer was made on essentially the same hardware.
> On 24 Mar 2020, at 09:38, Moritz Heffter wrote:
>
> It’s a new MacBook Pro 13‘ (2019) with 16/512 and an i5 (4 cores) 1,4 GHz
>
>> Am 23.03.2020 um 21:44 schrieb Hans Åberg :
>>
>> What computer model is this?
>>
>
It’s a new MacBook Pro 13‘ (2019) with 16/512 and an i5 (4 cores) 1,4 GHz
> Am 23.03.2020 um 21:44 schrieb Hans Åberg :
>
> What computer model is this?
>
>
>> On 23 Mar 2020, at 20:25, Moritz Heffter wrote:
>>
>> Thanks for this hint. I’m trying to install 2.20 on macOS Catalina (10.15.3)
What computer model is this?
> On 23 Mar 2020, at 20:25, Moritz Heffter wrote:
>
> Thanks for this hint. I’m trying to install 2.20 on macOS Catalina (10.15.3)
> and get a segmentation fault.
>
> I get this also with the version 2.19.84 mentioned below which might be
> pointing to a problem
Dear all,
Thanks for this hint. I’m trying to install 2.20 on macOS Catalina (10.15.3)
and get a segmentation fault.
I get this also with the version 2.19.84 mentioned below which might be
pointing to a problem on my machine. Does anyone have suggestions what I can
try?
Best,
Moritz
> Am 23
[Please keep the cc to the list so that others can follow the issue.]
With some programs, one may have to OK it in System Preferences > Security &
Privacy. But I think it is not needed for the MacPorts installer version.
> On 22 Mar 2020, at 23:17, Eric wrote:
>
> Actually, when this came up
> On 3 Mar 2020, at 05:14, Eric wrote:
>
> Actually, both the latest version and 2.19.84 seem not to launch at all on my
> iMac (late 2015, dual core, etc running os 10.15.3...) (2.19.84 did but it
> doesn’t.)
What binary are you using?
Actually, both the latest version and 2.19.84 seem not to launch at all on
my iMac (late 2015, dual core, etc running os 10.15.3...) (2.19.84 did but
it doesn’t.)
26 matches
Mail list logo
