Bug 198190
Summary: | ldd -r reports undefined symbols | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Karsten Hopp <karsten> |
Component: | festival | Assignee: | Matthew Miller <mattdm> |
Status: | CLOSED RAWHIDE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | CC: | mattdm |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | 1.96-0.11 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-03-20 19:01:24 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 232105 | ||
Bug Blocks: | 198485 |
Description
Karsten Hopp
2006-07-10 13:23:02 UTC
*** Bug 197594 has been marked as a duplicate of this bug. *** These are all in the three libraries from speech_tools (libestbase, libestools, libeststring). Will investigate further. Needs -lm, -ltinfo (from ncurses), and (since we're now building the esd module) -lesd. And, also, estools needs estbase. But that's not the big one. All those nasty underscored symbols are because the makefile inexplicably defines CXX to be gcc except on Mac OS Darwin, where it's (duh) set to g++. So, set it to g++ and we're good. (My in-progress updated package does this. Stay tuned.) See bug #232105 for in-progress updated packages which address this issue. Actually, I have a question about this. libtinfo seems to be in Fedora rawhide ncurses only; before that, the symbols are just in libcurses. Is there a good way to tell automatically what's needed? (Preferably without fancy checks; festival's configure/build system is somewhat twisted.) Oh. Linking with -lncurses works in all cases. Never mind. :) This issue should be resolved by the release of festival-1.96-0.11, now in the development tree. (See bug #232105 for details.) Please reopen if there's still a problem. Thanks. |