> On 2 Nov 2021, at 08:52, Thomas Scharkowski <t.scharkow...@t-online.de> wrote:
>
>
>>>
>>> Am 31.10.2021 um 18:36 schrieb Hans Åberg <haber...@telia.com>:
>>>>
>>>>
>>>>> On 31 Oct 2021, at 11:43, Thomas Scharkowski <t.scharkow...@t-online.de>
>>>>> wrote:
>>>>>
>>>>> Hi, I have installed this version on a fresh MacOS 12 and get this error
>>>>> message:
>>>>
>>>> I have made an installer using MacPorts directly on MacOS 12; see separate
>>>> post.
>>>>
>>>>
>>> I get the same error with this one.
>>>
>>> On my other machine (MacBook Pro) I had installed LilyPond with MacPorts,
>>> Frescobaldi are exactly the same on both machines (I once had different
>>> versions of Frescobaldi 3.1.3.).
>>> I wanted to avoid installing MacPorts on my iMac, but perhaps I will try
>>> this way.
>>
>> I have installed LilyPond via MacPorts now (it took several hours for all
>> this stuff) - now it works!
>> :-)
>
> macOS 12.0.1
> iMac 14,2
> Xcode 13.1
> MacPorts 2.7.1
>
> The Frescobaldi version is this one, no bug here:
It is actually a feature, not a bug, I think: LilyPond is set to call some
packages by name and not absolute paths, which is a carried over to the
MacPorts version. So if one does not set PATH, there will be an error. When
installing MacPorts, it used to add this to PATH, but there is a different
addition for the installer.
