John Covici, le ven. 03 avril 2020 21:04:43 -0400, a ecrit: > Well, the libraries I have are these: > > /usr/lib64/libflite_cmu_us_kal16.so.2.1 > /usr/lib64/libflite_cmu_grapheme_lex.so.2.1 > /usr/lib64/libflite_cmu_us_slt.so > /usr/lib64/libflite_cmu_time_awb.so.2.1 > /usr/lib64/libflite.so
Ah, they are in /usr/lib64, while the brltty link line has a -L/usr/lib, and thus the /usr/lib/libflite.a etc. variants get looked up first. It's odd that the .a and the .so files are in different directories. Is that really the same package which are providing them? I guess brltty could also avoid to add a -L/usr/lib since that will indeed disturb system libraries inclusion order. Could you post the generated config.log file to see where that is coming from? > And I don't see any way to change them. Is there a config to omit the > flite libraries? ./configure --help | grep flite --with-flite=DIRECTORY where the FestivalLite package is installed ... -> --without-flite Samuel _______________________________________________ This message was sent via the BRLTTY mailing list. To post a message, send an e-mail to: [email protected] For general information, go to: http://brltty.app/mailman/listinfo/brltty
