Andreas Cadhalpun <andreas.cadhal...@googlemail.com> (2014-04-29): > Package: libflite1 > Version: 1.4-release-8 > Severity: normal > > Dear Maintainer, > > libflite1 seems to have a lot of undefined symbols: > $ adequate libflite1 > libflite1:amd64: undefined-symbol > /usr/lib/x86_64-linux-gnu/libflite_cmu_time_awb.so.1.4 => clunits_synth > libflite1:amd64: undefined-symbol > /usr/lib/x86_64-linux-gnu/libflite_cmu_time_awb.so.1.4 => cmu_syl_boundary > libflite1:amd64: undefined-symbol > /usr/lib/x86_64-linux-gnu/libflite_cmu_time_awb.so.1.4 => lexicon_val > libflite1:amd64: undefined-symbol > /usr/lib/x86_64-linux-gnu/libflite_cmu_time_awb.so.1.4 => usenglish_init > libflite1:amd64: undefined-symbol > /usr/lib/x86_64-linux-gnu/libflite_cmu_time_awb.so.1.4 => > clunits_ldom_phone_word > > > If I'm not completely mistaken, this could lead to crashes. But as far as I > can tell, at least flite works correctly. > Still this should be fixed.
I'm not flite expert but it looks to me there's a plugin mechanism, with most symbols being defined in the shared library (libflite.so.1.4); depending on the intended architecture, it might be a better idea to store the plugins in a private directory. Mraw, KiBi.
signature.asc
Description: Digital signature
