Re: Compiling instructions for macOS 10.15 Catalina

I tried to follow this, but I encountered another problem: dependency "libgcc9" is not able to be built. Here is the log: main.log -- Sent from: http://lilypond.1069038.n5.nabble.com/Dev-f88644.html _

Re: Compiling instructions for macOS 10.15 Catalina

Have you made sure to try the following, listed in that thread? > I did have to make one change to the Portfile > for lilypond-devel. I added macports-gcc-9 at the top of the > compiler.fallback-append list, because MacPorts was mistakenly trying and > failing to build gcc8 as a dependency. The u

Compiling instructions for macOS 10.15 Catalina

After updating the macOS to Catalina, I tried to use Lilypond by MacPorts: Download Xcode and its command-line tools; Build MacPorts for sources; Run sudo port install lilypond-devel in the Terminal. However, it failed when building Perl dependencies (instead of GCC 8 suggested here

Re: LSR inconsistencies

> On 12 Oct 2019, at 12:08, Werner LEMBERG wrote: > >> Template: integrating \startTextSpan and \stopTextSpan in a customized >> TextSpanner >> >> then click "Enable filter". Nothing returns. > > Indeed. Here, the *second* backslash in the title prevents results in > the filter. This loo

Re: ottava signs

Malte Meyn-3 wrote > You could either compile LilyPond yourself or wait for the release of > 2.21.0. But I have no idea when that will be … I don’t think that these > patches will be cherry-picked to 2.19.84. OK, but I don't understand, where do I find the latest sources to compile from? Malt

Re: lilypond does not work with Mac OS 10.15 (Catalina)

> On 12 Oct 2019, at 14:28, Werner LEMBERG wrote: > >> But on the hand, I have never seen anything installing in /opt/ >> besides MacPorts on MacOS. And also packages are put in /usr/local/. > > Well, that homebrew occupies `/usr/local' is far from optimal. It decided to avoid it because of th

Re: lilypond does not work with Mac OS 10.15 (Catalina)

> The standard explicitly says it should not be there, but in > /opt/. Also, MacPorts is in /opt/local/ but should have been in > /opt/macports/, as it suggests /opt≮provider>/. Yes. > But on the hand, I have never seen anything installing in /opt/ > besides MacPorts on MacOS. And also packages

Re: lilypond does not work with Mac OS 10.15 (Catalina)

> On 12 Oct 2019, at 13:43, Werner LEMBERG wrote: > > What about `/opt/lilypond’? The location /usr/local/ is for user installations on BSD systems, there is for example /usr/local/texlive, so it seems natural. >>> >>> Well, I don't care enough to argue :-) >> >> Why not? :

Re: lilypond does not work with Mac OS 10.15 (Catalina)

What about `/opt/lilypond’? >>> >>> The location /usr/local/ is for user installations on BSD systems, >>> there is for example /usr/local/texlive, so it seems natural. >> >> Well, I don't care enough to argue :-) > > Why not? :-) Here are some links: > > http://www.pathname.com/fhs/pub/fh

Re: LSR inconsistencies

Am Sa., 12. Okt. 2019 um 12:08 Uhr schrieb Werner LEMBERG : > > >> > Though the title contains backslashes, thus it's not searchable > >> > in LSR. Not sure what to do!? > >> > >> Hmm. I just entered `\mark' in the LSR search box, and it *does* > >> return snippets with backslashes in the title.

Re: lilypond does not work with Mac OS 10.15 (Catalina)

> On 12 Oct 2019, at 12:09, Werner LEMBERG wrote: > > I think I put it into /usr/local/lilypond or /usr/local/lilypond-devel. Which location would you prefer? >>> >>> What about `/opt/lilypond’? >> >> The location /usr/local/ is for user installations on BSD systems, >> there is fo

Re: lilypond does not work with Mac OS 10.15 (Catalina)

>>> I think I put it into /usr/local/lilypond or >>> /usr/local/lilypond-devel. Which location would you prefer? >> >> What about `/opt/lilypond’? > > The location /usr/local/ is for user installations on BSD systems, > there is for example /usr/local/texlive, so it seems natural. Well, I don'

Re: LSR inconsistencies

>> > Though the title contains backslashes, thus it's not searchable >> > in LSR. Not sure what to do!? >> >> Hmm. I just entered `\mark' in the LSR search box, and it *does* >> return snippets with backslashes in the title. What exactly is the >> problem? > > From here: > > https://lsr.di.uni

Re: LSR inconsistencies

Am Sa., 12. Okt. 2019 um 07:22 Uhr schrieb Werner LEMBERG : > > > Done. > > Thanks! > > >> http://lsr.di.unimi.it/LSR/Item?id=857 > > > > Done. > > > > Though the title contains backslashes, thus it's not searchable in > > LSR. Not sure what to do!? > > Hmm. I just entered `\mark' in the LSR se

Re: lilypond does not work with Mac OS 10.15 (Catalina)

> On 12 Oct 2019, at 10:55, Werner LEMBERG wrote: > >> I think I put it into /usr/local/lilypond or >> /usr/local/lilypond-devel. Which location would you prefer? > > What about `/opt/lilypond’? The location /usr/local/ is for user installations on BSD systems, there is for example /usr/loca

Re: lilypond does not work with Mac OS 10.15 (Catalina)

>> To build a distributable `mpkg', you have to install MacPorts with >> a *different* prefix (i.e., not `/opt/local') so that it doesn't >> interfere with the `standard' MacPorts a user might have installed. >> And for such custom MacPorts installations only building from >> source works. > > I

Re: lilypond does not work with Mac OS 10.15 (Catalina)

> On 12 Oct 2019, at 07:21, Eric Benson wrote: > > gcc8 doesn’t build in MacPorts on Catalina, at least it didn’t build for me > on Thursday. There was a MacPorts release on Friday, but I haven’t tried it > yet. Maybe the problem has been fixed. I never got lilypond to build with > gcc8 becau

Re: lilypond does not work with Mac OS 10.15 (Catalina)

> On 12 Oct 2019, at 07:00, Werner LEMBERG wrote: > > >>> Well, right now you have to build MacPorts from source on MacOS >>> 10.15 – I guess this takes almost a day of compilation. (I don't >>> have such an OS, by the way). >> >> The link I gave has an installer for MacOS 10.15, and it works