> gcc8 doesn’t build in MacPorts on Catalina, at least it didn’t build
> for me on Thursday.
OK, I misunderstood.
Werner
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
> 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 exactl
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 us
>> 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 irrel
> On 11 Oct 2019, at 21:43, Werner LEMBERG wrote:
>
A problem with the [MacPorts] lilypond-devel package is that it
listed all dependencies for the build as required for the
installer, including GCC, making it very large, so it should be
slimmed down.
>>>
>>> This is not cor
>>> A problem with the [MacPorts] lilypond-devel package is that it
>>> listed all dependencies for the build as required for the
>>> installer, including GCC, making it very large, so it should be
>>> slimmed down.
>>
>> This is not correct any more, I think. See
>>
>> https://lists.gnu.org/ar
> On 11 Oct 2019, at 19:16, Eric Benson wrote:
>
> > I see that MacPorts now has been updated for MacOS 10.15.
>
> Hah! If only I had waited one more day!
It was not a waste of time — I have also done such package chasing, but a
package manager is of course more convenient. :-)
___
> On 11 Oct 2019, at 18:41, Werner LEMBERG wrote:
>
>
>> A problem with the [MacPorts] lilypond-devel package is that it
>> listed all dependencies for the build as required for the installer,
>> including GCC, making it very large, so it should be slimmed down.
>
> This is not correct any mor
> On 11 Oct 2019, at 18:41, Werner LEMBERG wrote:
>
> See
>
> https://lists.gnu.org/archive/html/lilypond-devel/2019-10/msg00047.html
The dependency has not yet been update to GCC 9, it seems:
https://ports.macports.org/port/lilypond-devel/summary
> I see that MacPorts now has been updated for MacOS 10.15.
Hah! If only I had waited one more day!
On Fri, Oct 11, 2019 at 1:12 PM Hans Åberg wrote:
>
> > On 11 Oct 2019, at 18:41, Werner LEMBERG wrote:
> >
> >
> >> A problem with the [MacPorts] lilypond-devel package is that it
> >> listed a
> A problem with the [MacPorts] lilypond-devel package is that it
> listed all dependencies for the build as required for the installer,
> including GCC, making it very large, so it should be slimmed down.
This is not correct any more, I think. See
https://lists.gnu.org/archive/html/lilypond-
Malte Meyn writes:
> Am 11.10.19 um 15:13 schrieb foxfanfare:
>> Hi Malte, this sounds really terrific, thank you very much for your work.
>> How could I test it or include your patch in my score presently? Should I
>> wait for a new release of lilypond (2.19.83)?
>
> You could either compile Lil
Am 11.10.19 um 15:13 schrieb foxfanfare:
Hi Malte, this sounds really terrific, thank you very much for your work.
How could I test it or include your patch in my score presently? Should I
wait for a new release of lilypond (2.19.83)?
You could either compile LilyPond yourself or wait for the
Malte Meyn-3 wrote
> Hi foxfanfare,
>
> Hopefully, all of this will be possible without ly:line-spanner::print
> and all those bound-details and bound-info overrides in a few days or
> weeks ;)
>
> You won’t need those shortcuts anymore, just override some grob
> properties of OttavaBracket an
> On 10 Oct 2019, at 17:41, Eric Benson wrote:
>
> I haven't tried to build the Mac OS application, Lilypond.app, because I
> don't use it myself. I only use the command line lilypond.
I believe it is deprecated, as there are better alternatives, Frescobaldi was
one suggestion I think.
> On 10 Oct 2019, at 17:41, Eric Benson wrote:
>
> sudo port install lilypond-devel
>
> That should work, after which you will have /opt/local/bin/lilypond
> installed. You have to make sure that /opt/local/bin is on your $PATH.
MacPorts adds it to $PATH, though not correctly first: I have /op
> On 10 Oct 2019, at 18:45, Carl Sorensen wrote:
>
> I think that we are going to need to move to having somebody with a Mac build
> and provide an OSX 64-bit build for lilypond, rather than using GUB for the
> 64-bit build.
MacPorts can create a standalone installer, one can choose installat
Hello,
Here is the current patch countdown list. The next countdown will be on
October 13th.
A quick synopsis of all patches currently in the review process can be
found here:
http://philholmes.net/lilypond/allura/
Push:
5568 Make build output terse by default - Dan Eble
https://sourcef
Hello,
On Thu, 10 Oct 2019 16:45:23 +, Carl Sorensen wrote:
>
>
> From: Eric Benson
> Date: Thursday, October 10, 2019 at 9:42 AM
> To: Carl Sorensen
> Cc: "lilypond-devel@gnu.org"
> Subject: Re: lilypond does not work with Mac OS 10.15 (Catalina)
>
> I could, but it is quite unreasona
On Thu, 10 Oct 2019 16:51:56 +, Carl Sorensen wrote:
> Given that make will not do anything if the source tree has not been changed,
> I see no problem (and plenty of benefit) in having make check do the
> equivalent of make && make check.
>
> Personally, however, I prefer to do
>
> mak
Am Mo., 7. Okt. 2019 um 09:16 Uhr schrieb Werner LEMBERG :
> Another minor issue: There are some snippets that have a full stop at
> the end of the title. IMHO, a title should never have that.
>
> http://lsr.di.unimi.it/LSR/Item?id=310
Done
> http://lsr.di.unimi.it/LSR/Item?id=336
Title is
21 matches
Mail list logo
