Bug 2190221 - /lib64/libespeak-ng.so does not exist. But /lib64/libespeak-ng.so.1 and /lib64/libespeak-ng.so .1.1.49 do
Summary: /lib64/libespeak-ng.so does not exist. But /lib64/libespeak-ng.so.1 and /lib6...
Keywords:
Status: VERIFIED
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: espeak-ng
Version: CentOS Stream
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Tomas Korbar
QA Contact: Tomas Pelka
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-04-27 15:10 UTC by Warren Dodge
Modified: 2023-06-27 06:40 UTC (History)
4 users (show)

Fixed In Version: espeak-ng-1.50-9.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-155956 0 None None None 2023-04-27 15:12:57 UTC

Description Warren Dodge 2023-04-27 15:10:51 UTC
Description of problem:

The system allows espeak-ng to be loaded. There is no devel module available for it. It is needed for the perl module Speech::eSpeak which I modified to look for the espeak-ng library. I had to add the link by hand to make it compile.

ln -s  libespeak-ng.so -> libespeak-ng.so.1

yum list | grep espeak
espeak-ng.i686       1.50-7.el9                            @appstream    
espeak-ng.x86_64     1.50-7.el9                            @AppStream    
speech-dispatcher-espeak-ng.x86_64   0.10.2-4.el9                  @AppStream    
brltty-espeak-ng.x86_64      6.3-4.el9                             appstream     


Version-Release number of selected component (if applicable):


How reproducible:

Try to build Speech::eSpeak after editing ources to use -lespeak-ng

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Joe Orton 2023-04-28 07:12:31 UTC
Thanks for the report, I'll propose to add espeak-ng-devel to CRB.


Note You need to log in before you can comment on or make changes to this bug.