unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Rohleder <mike@rohleder.de>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: 42301@debbugs.gnu.org
Subject: bug#42301: [PATCH] gnu: solfage: fix build.
Date: Sun, 09 Aug 2020 18:36:11 +0200	[thread overview]
Message-ID: <87pn7zvksk.fsf@rohleder.de> (raw)
In-Reply-To: <87a6z4axff.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Sun, 09 Aug 2020 13:08:52 +0200")


[-- Attachment #1.1: Type: text/plain, Size: 565 bytes --]

Hi!

Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
> Thank you. Unfortunately, the build fails later on with the following
> unrelated message, probably related to the latest Lilypond release:
>
>     fatal error: Uninitialized variable `write-performances-midis' in module (lily)
>

This is interesting, I can't reproduce this, it builds (and runs) fine here.
Are you using a newer version of lilypond? (here, its 2.20.0 from current master)

> Besides, you are adding this snippet to an unrelated phase, about Python
> wrapping.

Added a phase 'patch-readme:


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1.2: [PATCH] gnu: solfege: fix build. --]
[-- Type: text/x-patch, Size: 1218 bytes --]

From 3e6a637fcacb990291fb8a8b7e03e18be15bd644 Mon Sep 17 00:00:00 2001
From: Michael Rohleder <mike@rohleder.de>
Date: Sun, 9 Aug 2020 18:26:25 +0200
Subject: [PATCH] gnu: solfege: fix build.

* gnu/packages/music.scm (solfege): fix build (http://issues.guix.gnu.org/42301).
---
 gnu/packages/music.scm | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/gnu/packages/music.scm b/gnu/packages/music.scm
index db2f1ff8d6..f788d93b65 100644
--- a/gnu/packages/music.scm
+++ b/gnu/packages/music.scm
@@ -1362,6 +1362,12 @@ re-sequencer LV2 plugin.")
                             "solfege/presetup.py")
                (("#!/usr/bin/python") (string-append "#!" (which "python"))))
              #t))
+         ;; fix build, see https://issues.guix.gnu.org/42301
+         (add-before 'build 'patch-readme
+           (lambda _
+             (with-fluids ((%default-port-encoding "ISO-8859-1"))
+               (substitute* '("README") (("Malm.") "Malmoe")))
+             #t))
          (add-before 'build 'add-sitedirs
            ;; .pth files are not automatically interpreted unless the
            ;; directories containing them are added as "sites".  The directories
-- 
2.28.0


[-- Attachment #1.3: Type: text/plain, Size: 841 bytes --]


>
> BTW, would it make sense to provide 3.23.4 release instead? It is
> a development version, but development has stalled anyway. Also, it
> relies on Python 3 intead of Python 2.
>
> I tried to update it with the following source:
>
>      (origin
>        (method url-fetch)
>        (uri (string-append "http://alpha.gnu.org/gnu/solfege/solfege-"
>                            version ".tar.gz"))
>        (sha256
>         (base32 "0sc17vf4xz6gy0s0z9ghi68yskikdmyb4gdaxx6imrm40734k8mp")))
>
> but it fails in the same way.
>
> WDYT?

idk.
I haven't tried building it, because I think, we should first solve that
"fatal error: Uninitialized variable `write-performances-midis' in
module (lily)" error you get and I cant reproduce...

Regards,

-- 
Ein Hamsterrad sieht von innen aus
wie eine Karriereleiter.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  reply	other threads:[~2020-08-09 16:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <b5beef52-b072-ff3a-8a97-2e462a402c65.ref@eastlincoln.net>
2020-07-09 17:43 ` bug#42301: Build of GNU Solfege fails Tim Magee
2020-08-07 18:03   ` bug#42301: [PATCH] gnu: solfage: fix build Michael Rohleder
2020-08-09 11:08     ` Nicolas Goaziou
2020-08-09 16:36       ` Michael Rohleder [this message]
2020-08-11 17:09         ` Nicolas Goaziou
2021-07-05 10:47   ` bug#42301: Build of GNU Solfege fails zimoun
2021-07-05 11:57     ` Nicolas Goaziou
2021-07-05 12:31       ` Michael Rohleder
2021-07-05 13:46         ` Tim Magee
2021-07-05 13:49           ` zimoun

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://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87pn7zvksk.fsf@rohleder.de \
    --to=mike@rohleder.de \
    --cc=42301@debbugs.gnu.org \
    --cc=mail@nicolasgoaziou.fr \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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