Opened 9 years ago
Last modified 9 years ago
#90 new task
pango: Fix module exports
Reported by: | dmik | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | |
Component: | pango | Version: | |
Severity: | medium | Keywords: | |
Cc: |
Description
Pango language modules export a bunch of symbols starting with script_engine_
. The OS/2 build does this as well but the symbols start with underscores (of course) so that the module loader (and various tests) can't find them afterwards. Unfortunately, there is no easy way to solve this as some thinking needs to be done.
Change History (3)
comment:1 by , 9 years ago
comment:2 by , 9 years ago
Until this issue is solved, our RPMs will not provide these language modules as they can't be currently loaded.
Note:
See TracTickets
for help on using tickets.
There are basically two ways to solve the problem:
-export-symbols MY.DEF
because it applies special processing to this DEF file on OS/2 and still prefixes all symbols with underscores; b) I can't recall if the import library will be able to correctly resolve such symbols (as from the C point of view they should have underscores).script_engine_
symbols. Doesn't need a special DEF file and a libtool fix, the import library will surely work but this requires strictly platform-dependent bits in the source code which is also not very good.