1.8
On May 17, 2019 9:27 PM, Andrew Bernard wrote:
What version of guile should I be using to build 2.21.0 on Ubuntu (or
indeed any Linux)?
Apologies for my ignorance, but it is not immediately obvious to me where
this is documented.
Andrew
___
What version of guile should I be using to build 2.21.0 on Ubuntu (or
indeed any Linux)?
Apologies for my ignorance, but it is not immediately obvious to me where
this is documented.
Andrew
___
lilypond-devel mailing list
lilypond-devel@gnu.org
On Thu, May 16, 2019 at 6:06 PM Jahrme Risner wrote:
[...]
> Second, one of the consistent issues which Travis CI would not be able to
> solve is the dependence on LaTeX (texlive). There is not, AFAIK, *any*
> elegant
> solution to the usage of texlive on macOS. Homebrew, which is the package
>
On Fri, May 17, 2019 at 8:58 PM Carl Sorensen wrote:
> I'm pretty sure there are no Mac build instructions for Lilypond.
>
> The Linux build instructions are in the Contributor's Guide.
>
> GUB is a Linux build environment.
>
I know GUB is a Linux build environment, but that’s irrelevant since
I'm pretty sure there are no Mac build instructions for Lilypond.
The Linux build instructions are in the Contributor's Guide.
GUB is a Linux build environment.
Daniel reported success in a Homebrew build for the Mac. I would guess that
he's willing to share it with you.
I hope you can get
On Fri, May 17, 2019 at 3:48 PM Marnen Laibow-Koser
wrote:
>
> Hmm. At this point I should probably stop speculating and set up a build
> environment. But I’m getting married in a month and am not committing to
> any big projects before the wedding. :)
>
As I start to think about how to do
> On 17 May 2019, at 21:37, Daniel Johnson wrote:
>
> I had to manually download, build and install the following:
> - TeX Gyre font
> - Flex 2.5.37
Later version of Flex have broken C++ generation. Akim Demaille found a way
around this, maybe here:
Hello,
On 17/05/2019 20:37, Daniel Johnson wrote:
Here is my summary of what has been discussed regarding MacOS builds
over the last couple months. I feel like we are largely rehashing the
same questions/answers.
...
For the record, I have successfully built 64-bit Lilypond on a
Homebrew
> On 17 May 2019, at 21:48, Marnen Laibow-Koser wrote:
>
> On Fri, May 17, 2019 at 3:27 PM Hans Åberg wrote:
>
> > On 17 May 2019, at 21:14, Marnen Laibow-Koser wrote:
> >
> > On Fri, May 17, 2019 at 3:06 PM Hans Åberg wrote:
> >
> >> LilyPond uses Guile 1.8, not the latest, and the
On Fri, May 17, 2019 at 3:27 PM Hans Åberg wrote:
>
> > On 17 May 2019, at 21:14, Marnen Laibow-Koser wrote:
> >
> > On Fri, May 17, 2019 at 3:06 PM Hans Åberg wrote:
> >
> >> LilyPond uses Guile 1.8, not the latest, and the lilypond in MacPorts
> uses gcc8, not the latest supported gcc9.
> >>
> On 17 May 2019, at 21:14, Marnen Laibow-Koser wrote:
>
> On Fri, May 17, 2019 at 3:06 PM Hans Åberg wrote:
>
>> LilyPond uses Guile 1.8, not the latest, and the lilypond in MacPorts uses
>> gcc8, not the latest supported gcc9.
>>
> Will it build with GCC 9?
That would need to be tested,
Here is my summary of what has been discussed regarding MacOS builds
over the last couple months. I feel like we are largely rehashing the
same questions/answers.
1. Lilypond’s current build system is GUB. GUB is a cross-platform
all-in-one build system which produces binaries for Linux,
On Fri, May 17, 2019 at 3:06 PM Hans Åberg wrote:
>
> > On 17 May 2019, at 16:10, Marnen Laibow-Koser wrote:
> >
> >> Given that MacPorts supports more packages than Homebrew this is a
> >> very bold statement.
> >
> > Homebrew supports enough packages, and it’s really easy to add new ones,
>
> On 17 May 2019, at 16:10, Marnen Laibow-Koser wrote:
>
>> Given that MacPorts supports more packages than Homebrew this is a
>> very bold statement.
>
> Homebrew supports enough packages, and it’s really easy to add new ones, so
> that’s pretty much irrelevant.
Somebody said it had problems
I didn't find the time to do it myself, sorry.
Ofcourse, LGTM
https://codereview.appspot.com/544700043/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
On Fri, May 17, 2019 at 1:54 PM Werner LEMBERG wrote:
>
> >> [...], Homebrew does not support macOS 10.7, [...]
> >
> > Good to know; I wasn't aware of that. However, won't our existing
> > 32-bit Mac build process be sufficient for 10.7?
>
> Yes. But this fact doesn't help in creating 64bit
>> [...], Homebrew does not support macOS 10.7, [...]
>
> Good to know; I wasn't aware of that. However, won't our existing
> 32-bit Mac build process be sufficient for 10.7?
Yes. But this fact doesn't help in creating 64bit stuff for new MacOS
versions.
Werner
On Fri, May 17, 2019 at 1:13 PM Werner LEMBERG wrote:
>
> >> And all users that don't use the two latest releases of MacOS (like
> >> me) are out of the game, too.
> >>
> >> [Note that I'm not a MacOS user at all. For daily work I'm
> >> exclusively using GNU/Linux. It's just that I'm
>> And all users that don't use the two latest releases of MacOS (like
>> me) are out of the game, too.
>>
>> [Note that I'm not a MacOS user at all. For daily work I'm
>> exclusively using GNU/Linux. It's just that I'm interested in
>> providing support even on exotic platforms :-)]
>
>
On Fri, May 17, 2019 at 1:33 AM Werner LEMBERG wrote:
> > I think this is poor advice. IMHO MacPorts is very hard to work
> > with (as an end user) compared to Homebrew, and I haven't seen
> > anyone using MacPorts on their Mac in well over a decade.
>
> Given that MacPorts supports more
Hello,
Here is the current patch countdown list. The next countdown will be on
May 19th.
A quick synopsis of all patches currently in the review process can be
found here:
http://philholmes.net/lilypond/allura/
Push:
No patches to push at this time.
Countdown:
No patches on
Hello,
Here is the current patch countdown list. The next countdown will be on
May 19th.
A quick synopsis of all patches currently in the review process can be
found here:
http://philholmes.net/lilypond/allura/
Push:
No patches to push at this time.
Countdown:
No patches on
22 matches
Mail list logo
