Re: Compiling instructions for macOS 10.15 Catalina

[tansongchen]

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

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Compiling instructions for macOS 10.15 Catalina

[Carl Sorensen]

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 user who did this found success.  You may wish to try it.

We are currently trying to resolve the issues before we decide what the final 
documentation should be.

Thanks,

Carl



___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Compiling instructions for macOS 10.15 Catalina

[tansongchen]

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

 
)
I would like to know if we will have further instructions on this topic. If
possible, I suggest we can summarize it as some documentation.




--
Sent from: http://lilypond.1069038.n5.nabble.com/Dev-f88644.html
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: LSR inconsistencies

[Sebastiano Vigna]

> 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 looks like a bug in the LSR search engine.
> Sebastiano?

Mmmm... there's some weird escaping sorcery going on. If you look for 
\\startTextSpan it'll work. But yes, it should work with a single slash.

Actually, not. The indexed token is starttextspan. So the engine should 
tokenize '\' 'startTextSpan' and do its job. It's not. I'll have a look into it.

Ciao,

seba


___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: ottava signs

[foxfanfare]

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? 


Malte Meyn-3 wrote
> My question was about the vertical alignment of the 8va 
> number/text/markup and the horizontal (dashed/dotted) line:
> 
>   8_ or 8 or 8°°
> 
> This could be done (1) by defining the markups using \general-align and 
> then use the markup’s alignment (2) by defining one number/direction and 
> use a mirrored version for ottava bassa below the staff or (3) by using 
> a pair of numbers/directions.

I now understand. My opinion for that is definitively the 3rd option. Either
at the top of the "8" or just a little bit bellow is good practice for me,
as long as it's not too far from the top (that's at least how I configured
it in the example I posted with my code and what I think looks good!).



--
Sent from: http://lilypond.1069038.n5.nabble.com/Dev-f88644.html

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

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

[Hans Åberg]

> 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 that. I have used /usr/local/ mainly to 
override older system installations, such as bison, which is the intended 
purpose then, but also other packages that are compiled and typically use that 
as the default installation location.



___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

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

[Werner LEMBERG]

> 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 are put in /usr/local/.

Well, that homebrew occupies `/usr/local' is far from optimal.


Werner
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

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

[Hans Åberg]

> 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? :-) Here are some links:
>> 
>> http://www.pathname.com/fhs/pub/fhs-2.3.html
>> https://unix.stackexchange.com/questions/11544/what-is-the-difference-between-opt-and-usr-local
>> https://www.linuxjournal.com/magazine/pointcounterpoint-opt-vs-usrlocal
> 
> Well, the links you give just prove my point that `/opt/lilypond'
> would be a better choice than `/usr/local/lilypond' – I don't want
> mpkg to install into `/usr/local/bin', `/usr/local/lib', etc.
> Instead, we have a complete bundle, with a separate directory
> hierarchy.

Not better necessarily, but what the standard suggests. But let’s follow it and 
put it into /opt/lilypond/.

> Normally, the directory structure below `/usr/local' mimics `/usr'.
> Having stuff like `/usr/local/texlive' is thus an exception, basically
> violating FHS.  Not everyone likes it; see the thread starting at
> 
>  https://tug.org/pipermail/tex-live/2015-September/037361.html

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>/.

But on the hand, I have never seen anything installing in /opt/ besides 
MacPorts on MacOS. And also packages are put in /usr/local/.


___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

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

[Werner LEMBERG]

 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/fhs-2.3.html
> https://unix.stackexchange.com/questions/11544/what-is-the-difference-between-opt-and-usr-local
> https://www.linuxjournal.com/magazine/pointcounterpoint-opt-vs-usrlocal

Well, the links you give just prove my point that `/opt/lilypond'
would be a better choice than `/usr/local/lilypond' – I don't want
mpkg to install into `/usr/local/bin', `/usr/local/lib', etc.
Instead, we have a complete bundle, with a separate directory
hierarchy.

Normally, the directory structure below `/usr/local' mimics `/usr'.
Having stuff like `/usr/local/texlive' is thus an exception, basically
violating FHS.  Not everyone likes it; see the thread starting at

  https://tug.org/pipermail/tex-live/2015-September/037361.html


Werner
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: LSR inconsistencies

[Thomas Morley]

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.  What exactly is the
> >> problem?
> >
> > From here:
> >
> >   https://lsr.di.unimi.it/list.php?type=snippet
> >
> > enter in the Title-box:
> >
> >   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.

Not sure it's only the *second* backslash causing the problem.

Searching for
Template: integrating
returns correctly, but searching for
Template: integrating \startTextSpan
already fails.
Maybe the ":" is problematic as well?

Cheers,
  Harm

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

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

[Hans Åberg]

> 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 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/fhs-2.3.html
https://unix.stackexchange.com/questions/11544/what-is-the-difference-between-opt-and-usr-local
https://www.linuxjournal.com/magazine/pointcounterpoint-opt-vs-usrlocal



___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

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

[Werner LEMBERG]

>>> 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't care enough to argue :-)


Werner
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: LSR inconsistencies

[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.  What exactly is the
>> problem?
>
> From here:
>
>   https://lsr.di.unimi.it/list.php?type=snippet
>
> enter in the Title-box:
>
>   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 looks like a bug in the LSR search engine.
Sebastiano?

> Ditto for 
>
>   Aligning objects created with the \mark command

Yep.  Interestingly, it is possible to search for

  \mark

Thanks for adding the HTML tags!  Will check that tomorrow after a new
dump is available.


Werner

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: LSR inconsistencies

[Thomas Morley]

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 search box, and it *does*
> return snippets with backslashes in the title.  What exactly is the
> problem?

From here:
https://lsr.di.unimi.it/list.php?type=snippet
enter in the Title-box:
Template: integrating \startTextSpan and \stopTextSpan in a customized
TextSpanner
then click "Enable filter".
Nothing returns.

Some for #546 below (with and without -tags)

>
> By the way, Sebastiano has now added support for HTML tags in snippet
> titles.  For testing purposes I ask you to change, say in snippet
> #546
>
>   http://lsr.di.unimi.it/LSR/Item?id=546,
>
> the title from
>
>   Aligning objects created with the \mark command
>
> to
>
>   Aligning objects created with the \mark command
>
> so that HTML code is added to the LSR dump.

Done.

Cheers,
  Harm

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

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

[Hans Åberg]

> 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/local/texlive, so it seems natural.



___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

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

[Werner LEMBERG]

>> 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 made one such distribution, and even sent to a listing of its
> contents, remember?

Ah, ok.  And no, sorry, I don't remember :-)

> I think I put it into /usr/local/lilypond or
> /usr/local/lilypond-devel.  Which location would you prefer?

What about `/opt/lilypond'?

>> [*]: This is essentially a complete re-installation of MacPorts
>> from scratch, also installing the newest version of XCode and
>> its command line tools before doing that.
> 
> I am doing that right now, but there are build errors.

More or less expected; at least, this is my impression reading the
macports mailing list.  It will take some weeks until all rough edges
are fixed in Catalina support.


Werner

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

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

[Hans Åberg]

> 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 because I couldn’t build gcc8. I just modified the Portfile so it used 
> gcc9 instead. As far as I know, there’s no reason to think that lilypond 
> would have a dependency on any particular version of gcc, or even on gcc at 
> all.

This is good to know. It would be better with gcc9, but another package called 
for llvm7 and the latest is llvm9, so it is not a big deal to have multiple 
versions installed.



___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

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

[Hans Åberg]

> 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. :-)
>>   https://www.macports.org/install.php
> 
> This is irrelevant.  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 made one such distribution, and even sent to a listing of its contents, 
remember?

I think I put it into /usr/local/lilypond or /usr/local/lilypond-devel. Which 
location would you prefer?

>>> And note also that I haven't looked into how and what can get
>>> stripped of from the mpkg bundle.
>> 
>> I got the impression that is what the link you gave was about:
>>  https://lists.gnu.org/archive/html/lilypond-devel/2019-10/msg00047.html
> 
> As mentioned there, a script has to be written that does this
> stripping, and I haven't done so.


OK.

>> Also, lilypond-devel has not been updated to use gcc9.  I am using
>> it for other things, so it would be good not having to install gcc8.
> 
> This will take some time – contrary to Joe User the developers *are*
> interested why building with gcc8 fails.
> 
> I thus ask Catalina users who already have a *completely*
> *regenerated* MacPorts installation[*] to check whether using gcc8
> really fails to build LilyPond.  If it does, please file a MacPorts
> bug ticket with all the details.
> 
> 
>Werner
> 
> 
> [*]: This is essentially a complete re-installation of MacPorts from
> scratch, also installing the newest version of XCode and its
> command line tools before doing that.

I am doing that right now, but there are build errors.



___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel