unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Simon South <simon@simonsouth.net>
To: guix-patches@gnu.org, 68195@debbugs.gnu.org
Subject: bug#68195: [PATCH core-updates 0/1] gnu: flite: Fix build.
Date: Sat, 13 Jan 2024 10:09:59 -0500	[thread overview]
Message-ID: <cover.1705157474.git.simon@simonsouth.net> (raw)
In-Reply-To: <877ckssp6f.fsf@simonsouth.net>

Here's a patch that allows flite, a lightweight speech-synthesis engine, to
build in core-updates, by applying a small patch to one of its makefiles as
outlined in an earlier email[0].

I've tested this on AArch64 and x86-64 and everything seems fine.

Note I haven't received a response from Dr. Black in almost two weeks' time,
and my email asking to join the festival-talk mailing list[1] has bounced, so
it appears flite may be unmaintained at the moment.

--
Simon South
simon@simonsouth.net

[0] https://lists.gnu.org/archive/html/bug-guix/2024-01/msg00000.html

[1] http://www.festvox.org/maillists.html


Simon South (1):
  gnu: flite: Fix build.

 gnu/local.mk                                  |  1 +
 .../patches/flite-build-with-make-4.4.patch   | 24 +++++++++++++++++++
 gnu/packages/speech.scm                       |  3 ++-
 3 files changed, 27 insertions(+), 1 deletion(-)
 create mode 100644 gnu/packages/patches/flite-build-with-make-4.4.patch


base-commit: a3ae833227a284fbcfbb813b1156d0e8aeeb29d1
-- 
2.41.0





  parent reply	other threads:[~2024-01-13 15:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-01 21:45 bug#68195: flite fails to build on core-updates Simon South
2024-01-01 23:14 ` Simon South
2024-01-13 15:09 ` Simon South [this message]
2024-01-13 15:10   ` bug#68195: [PATCH core-updates 1/1] gnu: flite: Fix build Simon South
2024-01-30 15:19 ` bug#68195: flite fails to build on core-updates Simon South

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=cover.1705157474.git.simon@simonsouth.net \
    --to=simon@simonsouth.net \
    --cc=68195@debbugs.gnu.org \
    --cc=guix-patches@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.
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).