Package Details: flite1 1.4-7

Git Clone URL: https://aur.archlinux.org/flite1.git (read-only, click to copy)
Package Base: flite1
Description: A lighweight speech synthesis engine (version 1.x)
Upstream URL: http://www.speech.cs.cmu.edu/flite/
Licenses: custom
Conflicts: flite, flite1-patched
Provides: flite, flite1-patched
Replaces: flite1-patched
Submitter: pure-aur
Maintainer: dbermond
Last Packager: dbermond
Votes: 41
Popularity: 0.26
First Submitted: 2016-06-11 15:35 (UTC)
Last Updated: 2024-05-23 01:45 (UTC)

Required by (51)

Sources (10)

Latest Comments

1 2 3 4 5 Next › Last »

kentslaney commented on 2024-06-02 08:26 (UTC) (edited on 2024-06-02 08:43 (UTC) by kentslaney)

@dbermond I haven't looked into why, but for whatever reason my copy of texi2pdf was only outputting a DVI file, despite what the documentation claims. It's almost certainly a problem with my setup rather than the package, but I figured I'd post the workaround just in case anyone else runs into the same problem. Comment aimed at future users rather than maintainers. Thank you for the quick replies though.

dbermond commented on 2024-06-02 04:27 (UTC)

@kentslaney I cannot reproduce your issue. The package is building fine for me.

kentslaney commented on 2024-06-01 18:24 (UTC) (edited on 2024-06-01 18:33 (UTC) by kentslaney) 

install: cannot stat 'flite-1.4-release/doc/flite.pdf': No such file or directory

was resolved for me with

diff --git a/doc/Makefile b/doc/Makefile
index 828d2e5..b4fbcc3 100644
--- a/doc/Makefile
+++ b/doc/Makefile
@@ -63,7 +63,7 @@ flite.html: flite.texi
        @ (cd html; rm -f index.html; ln flite_toc.html index.html)

 flite.pdf:  flite.texi
-       @ texi2pdf flite.texi
+       @ texi2pdf --dvipdf flite.texi

though I'm not sure why it was necessary

dbermond commented on 2024-05-23 01:45 (UTC)

@Captain_Lucy this is an issue due to gcc 14. I've pushed a fix and the package is now building fine. Thanks for reporting.

Captain_Lucy commented on 2024-05-22 21:54 (UTC) (edited on 2024-05-22 21:59 (UTC) by Captain_Lucy)

I'm unable to build this. Have tried many times with makepkg and yay. It's a dependecy for ffmpeg which I need to make my system usable for my use case. Anyone know a fix or workaround?

cmu_time_awb.c: In function ‘register_cmu_time_awb’:
cmu_time_awb.c:81:27: warning: assignment discards ‘const’ qualifier from 
pointer target type [-Wdiscarded-qualifiers]
81 |     cmu_time_awb_lex.data = cmu_time_awb_lex_data;
   |                           ^
cmu_time_awb.c:82:34: error: assignment to ‘char **’ from incompatible  
pointer type ‘const char * const*’ [-Wincompatible-pointer-types]
82 |     cmu_time_awb_lex.phone_table = cmu_time_awb_lex_phone_table;
   |                                  ^
make[2]: *** [../../config/common_make_rules:108: ../../build/x86_64-linux-
gnu/obj/lang/cmu_time_awb/cmu_time_awb.os] Error 1    
make[1]: *** [../config/common_make_rules:133: ../build/x86_64-linux-gnu/ 
obj/lang/.make_build_dirs] Error 2
make: *** [config/common_make_rules:133: build/x86_64-linux-gnu/ 
obj//.make_build_dirs] Error 2
==> ERROR: A failure occurred in build().
Aborting...

dbermond commented on 2023-09-12 23:49 (UTC)

@Terseus If it works when building in a clean chroot but not when running pure makepkg locally, then probably you have something wrong in your system. Hard to tell what it can be. For me it builds fine either with devtools and with pure makepkg.

eclairevoyant commented on 2023-09-12 07:16 (UTC)

There are some AUR guidelines that mitigate environment issues, but nothing can be 100% foolproof. Best option is to build in clean chroots. As far as AUR helpers, aurutils and paru support such builds, as long as you set up the chroot beforehand and point them at it.

Terseus commented on 2023-09-12 07:09 (UTC)

@eclairevoyant Tried again, this time using extra-x86_64-build, it worked.

I wonder what's in my environment that's causing it to fail, and if it can/should be reflected in the PKGBUILD...

eclairevoyant commented on 2023-09-12 06:59 (UTC)

@Terseus I suggest building in a clean chroot to avoid problems from the build environment: https://wiki.archlinux.org/title/DeveloperWiki:Building_in_a_clean_chroot

Just tested a clean chroot build on a fully updated system and it works fine.

1 2 3 4 5 Next › Last »