Issue 123964 - mismatching symbol visibility causes link problems
Summary: mismatching symbol visibility causes link problems
Status: CLOSED FIXED
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: 4.1.0-dev
Hardware: All All
: P3 Normal (vote)
Target Milestone: 4.1.0
Assignee: hdu@apache.org
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-01-03 13:42 UTC by hdu@apache.org
Modified: 2014-04-01 12:48 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description hdu@apache.org 2014-01-03 13:42:11 UTC
If a symbol is marked as visible in one object file and marked as invisible in another object file then this inconsistency causes link problems in some build environments. Even if the linker can resolve the problem by ignoring one of the visibility bits this is unclean and should be solved.
Comment 1 SVN Robot 2014-01-03 13:47:35 UTC
"hdu" committed SVN revision 1555087 into trunk:
#i123964# make symbol visibility consistent in sc module
Comment 2 SVN Robot 2014-01-03 13:48:52 UTC
"hdu" committed SVN revision 1555089 into trunk:
#i123964# fix symbol visibility mismatch in dbaccess module
Comment 3 hdu@apache.org 2014-01-03 13:49:15 UTC
Fixed with the commits above.
Comment 4 SVN Robot 2014-01-06 11:40:47 UTC
"hdu" committed SVN revision 1555720 into trunk:
#i123964# fix symbol visibility mismatch in dbaccess filter/xml
Comment 5 SVN Robot 2014-01-06 16:02:58 UTC
"hdu" committed SVN revision 1555875 into trunk:
#i123964# reshuffle DLLEXPORT in dbaccess module
Comment 6 SVN Robot 2014-01-06 17:51:30 UTC
"hdu" committed SVN revision 1555945 into trunk:
#i123964# fix SC build on windows with consistent symbol visibility
Comment 7 SVN Robot 2014-02-04 12:26:36 UTC
"hdu" committed SVN revision 1564269 into trunk:
#i123964# mark add_to_recently_used_file_list() as DLLPUBLIC
Comment 8 hdu@apache.org 2014-04-01 12:48:13 UTC
Closing the resolved issue.