From: Thomas Morley <thomasmorley65@gmail.com>
To: Arne Babenhauserheide <arne_bab@web.de>
Cc: guile-user <guile-user@gnu.org>
Subject: Re: State of lilypond with Guile 2?
Date: Fri, 8 Nov 2019 21:26:55 +0100 [thread overview]
Message-ID: <CABsfGyV4OB36_+6LjbGbUHmttwAzv_0awsL-C8S12X0vM=7Ndg@mail.gmail.com> (raw)
In-Reply-To: <87mud66sq4.fsf@web.de>
Hi Arne,
Am Fr., 8. Nov. 2019 um 21:04 Uhr schrieb Arne Babenhauserheide
<arne_bab@web.de>:
>
> Hi,
>
> I had the recollection that lilypond nowadays can work with Guile 2, but
> when I checked right now in the docs, I saw them saying "Version 2.x of
> Guile is not currently supported"
> http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=blob;f=Documentation/included/compile.itexi;h=0abd68a9177912138f01055504f20721e4a507de;hb=HEAD#l85
>
> Do you know the state of using lilypond with modern Guile?
Due to the lack of manpower we don't get close to release any LilyPond
supporting guile-2.x.
Thus the known problems persist.
All low hanging fruits are done, though and speaking only for me: I
can't go deeper, it's beyond my depth.
Remember, I'm not even a programmer, but a musician, maybe an
ambitious musician ;)
Additionally I recently found something preventing our `make
test-baseline´ to work.
Probablly identified here:
https://lists.gnu.org/archive/html/lilypond-devel/2019-10/msg00236.html
(unsolved)
Following the link you'll find a .zip containing several patches.
Applying them you'll get a successful
`make´ and `make doc` for every guile up to guile-2.9.4, but as said
`make test-baseline´ fails.
>
> Does the lilypond in Guix use Guile 2?
No clue, I doubt, though.
>
> Does lilypond on Windows use Guile 2?
No.
>
> Best wishes,
> Arne
> --
> Unpolitisch sein
> heißt politisch sein
> ohne es zu merken
Best,
Harm
next prev parent reply other threads:[~2019-11-08 20:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-08 20:03 State of lilypond with Guile 2? Arne Babenhauserheide
2019-11-08 20:26 ` Thomas Morley [this message]
2019-11-14 21:15 ` Arne Babenhauserheide
2019-11-16 13:43 ` Thomas Morley
2019-11-09 7:30 ` Ricardo Wurmus
2019-11-17 8:53 ` Arne Babenhauserheide
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CABsfGyV4OB36_+6LjbGbUHmttwAzv_0awsL-C8S12X0vM=7Ndg@mail.gmail.com' \
--to=thomasmorley65@gmail.com \
--cc=arne_bab@web.de \
--cc=guile-user@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).