Re: Testers wanted

[Andrew Culver]

Hello Michael Hendry

FWIW - I installed Lilypond 2.22.1 on Catalina using MacPorts. “nerdling" has 
also amiably posted version 2.23.3 there as of now.

I made a little cheatsheet after my own successful install. Here it is:

Installing and using Macports for LilyPond
==========================================
https://www.macports.org/install.php
https://guide.macports.org/#installing #better
# Xcode must be up to date (see link immediately above)
# keep macports up to date
sudo port -v selfupdate
# search for lilypond ports available
port search lilypond*
# search for all ports related to lilypond
port search lilypond
# installing a port help
https://guide.macports.org/#using.port.install
# installing lilypond
sudo port install lilypond
# also see port clean and port uninstall
https://guide.macports.org/#using.port.clean
https://guide.macports.org/#using.port.uninstall

Best

Andrew Culver



> On Jul 29, 2021, at 13:28, Michael Hendry <hendry.michael@gmail.com> wrote:
> 
> On 29 Jul 2021, at 09:57, Knut Petersen <Knut_Petersen@t-online.de> wrote:
>> 
>> On 29.07.21 02:41, Michael Hendry wrote:
>>> 
>>> Hi, Knut.
>>> 
>>> Now that I’ve settled in to my new iMac (64-bit, X86 processor, Mac OS 
>>> 11,5.1) I’ve got all my usual utilities running in the new environment 
>>> except lilypond and Frescobaldi.
>>> 
>>> Pre-compiled binaries for this computer aren’t available, so I’ve cloned 
>>> the source code into my ~/git_stuff directory as follows...
>>> 
>>> 
>>> checking how to run the C++ preprocessor... /lib/cpp
>>> configure: error: in `/Users/michaelhendry/git_stuff/lilypond':
>>> configure: error: C++ preprocessor "/lib/cpp" fails sanity check
>>> See `config.log' for more details
>>> ******
>>> 
>>> Am I naive to think this should “just work”?
>> 
>> Well, to build lilypond  you need a working toolchain, and a working cpp is 
>> definitely part of that toolchain needs.
>> 
>> Maybe you should have a look at 
>> https://gitlab.com/marnen/lilypond-mac-builder if you want to build lilypond 
>> on your mac
>> 
>> Knut
>> 
>> 
> 
> I do, in fact, have a working copy of cpp, but in /usr/bin/cpp, not in 
> /lib/cpp.
> 
> I should be able to create a /lib directory and put a link in it, but Big Sur 
> is very protective about the root directory, and I haven’t worked out how to 
> do that.
> 
> In any case, it’s usual for git compilations to use the path on the local 
> machine to establish that the necessary tools are present and not to enforce 
> an absolute location for any given tool.
> 
> Unfortunately, widespread gripping hasn’t revealed a suitable place to 
> specify the location of cpp. I have a feeling there’s a facility to override 
> default locations when running .configure (for instance) with a command-line 
> argument.
> 
> Meanwhile, I’ll have a look at mac-builder.
> 
> Thanks, 
> 
> Michael