Michael
I think this indication to your terminal is significant: Bad CPU type in executable - /Users/michaelhendry/.lyp/lilyponds/2.23.3/bin/lilypond
Perhaps nerdling compiled v 2.23.3 with an M1 chip. And it think you indicated your new Mac is Intel.
If so, try removing 2.23.3 using MacPorts, and installing 2.22.1 also using MacPorts. My machine is Intel and the MacPorts 2.22.1 works fine.
It’s a pity nerdling is not in on this conversation. Does anyone know who that is? Also, it should be possible to reach them through MacPorts.org.
Andrew
Hello Michael,
Check the output of:
echo $PATH
The folder containing the LilyPond version you want to use should be the first such.
JM
On 4 Aug 2021, at 15:50, Andrew Culver <culver@anarchicharmony.org> wrote:
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
Thanks, Andrew. I tried the above and got:michaelhendry@iMac ~ % which lilypond/Users/michaelhendry/.rvm/gems/ruby-head/bin/lilypondmichaelhendry@iMac ~ % /Users/michaelhendry/.rvm/gems/ruby-head/bin/lilypond --versionBad CPU type in executable - /Users/michaelhendry/.lyp/lilyponds/2.23.3/bin/lilypondmichaelhendry@iMac ~ % Will investigate further, but probably not today.Michael
Michael, looks like you have multiple package managers in play. For plain MacPorts Lilypond would've been in the /opt/local folder structure. Yours appear to reside in folders of the Ruby Version Manager. I didn't know it, but looking at their site version and MacPorts configuration are a bit blurry to me. In the past I've had issues mixing multiple package managers on Mac OS, so in the end I've decided to only use MacPorts. With a plain MacPorts I've never encountered an issue with the Lilypond port.
kind regards, Hans
|