From: Thomas Albers via Guix-patches via <guix-patches@gnu.org>
To: Maxime Devos <maximedevos@telenet.be>
Cc: 50722@debbugs.gnu.org
Subject: [bug#50722] [PATCH] gnu: Update amsynth to 1.12.2
Date: Sun, 26 Sep 2021 22:41:50 +0200 [thread overview]
Message-ID: <874ka7dpy0.fsf@thomaslabs.org> (raw)
In-Reply-To: <f18b12ea9bfa61d8e34e6a3e5125406b7916e291.camel@telenet.be>
Hello Maxime,
you are completely right. I wanted to avoid making more modification
than needed to get the program to work because of my inexperience
submitting patches. I will take it into account now that I have to look
into an error I missed.
Greetings,
Thomas.
Maxime Devos <maximedevos@telenet.be> writes:
> [[PGP Signed Part:Undecided]]
> Thomas Albers via Guix-patches via schreef op di 21-09-2021 om 16:17 [+0200]:
>>
>> [...]
>> (arguments
>> `(#:phases
>> @@ -2372,13 +2373,12 @@ special variant of additive synthesis.")
>> (lambda _
>> (substitute* "src/GUI/editor_pane.c"
>> (("/usr/bin/unzip") (which "unzip")))
>
> Needs to be (string-append (assoc-ref inputs "unzip") "/bin/unzip")
> for cross-compilation.
>
>> - (substitute* "src/GUI/GUI.cc"
>> + (substitute* "src/GUI/MainMenu.cpp"
>> (("/usr/bin/which") (which "which")))
>
> Likewise.
>
> Greetings,
> Maxime.
>
> [[End of PGP Signed Part]]
next prev parent reply other threads:[~2021-09-26 20:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-21 14:17 [bug#50722] [PATCH] gnu: Update amsynth to 1.12.2 Thomas Albers via Guix-patches via
2021-09-26 17:24 ` Efraim Flashner
2021-09-26 20:17 ` Thomas Albers via Guix-patches via
2021-09-30 22:43 ` Thomas Albers via Guix-patches via
2021-09-26 20:19 ` Maxime Devos
2021-09-26 20:41 ` Thomas Albers via Guix-patches via [this message]
2021-09-30 23:11 ` [bug#50722] [PATCH] Update-amsynth-to-1.12.2 Thomas Albers via Guix-patches via
2021-10-02 15:22 ` bug#50722: [PATCH] gnu: Update amsynth to 1.12.2 Ludovic Courtès
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=874ka7dpy0.fsf@thomaslabs.org \
--to=guix-patches@gnu.org \
--cc=50722@debbugs.gnu.org \
--cc=maximedevos@telenet.be \
--cc=thomas@thomaslabs.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.
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).