Issue 791 - Invalid soname specified for some .so's
Summary: Invalid soname specified for some .so's
Status: CLOSED NOT_AN_OOO_ISSUE
Alias: None
Product: Build Tools
Classification: Code
Component: code (show other issues)
Version: 625
Hardware: SGI IRIX
: P3 Trivial (vote)
Target Milestone: ---
Assignee: sander_traveling
QA Contact: issues@tools
URL:
Keywords:
Depends on:
Blocks: 810
  Show dependency tree
 
Reported: 2001-04-26 08:16 UTC by zeroj
Modified: 2003-03-12 14:30 UTC (History)
1 user (show)

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


Attachments
solenv/inc/unxirxm3.mk : Workaround to remove -soname altogether (1.05 KB, patch)
2001-04-26 08:21 UTC, zeroj
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this issue.
Description zeroj 2001-04-26 08:16:19 UTC
The name given to -soname is quite often libim.so, and hence when multiple 
libraries named as such are used to link, only the first set of symbols are 
recognised.

From memory sal, store and registry all had this problem
Comment 1 zeroj 2001-04-26 08:21:08 UTC
Created attachment 167 [details]
solenv/inc/unxirxm3.mk : Workaround to remove -soname altogether
Comment 2 Unknown 2001-04-26 12:38:33 UTC
irix issue, sent to porting
Comment 3 Unknown 2001-11-08 23:07:29 UTC
changing QA contact from bugs@ to issues@
Comment 4 nickb 2001-11-22 05:57:05 UTC
The soname stuff shouldn't be in the OS specific makefile, as the 
target numbers are not evaluated yet. (Which explains why John was
seeing libim.so).
Using SONAME_SWITCH seems to fix this problem.
Comment 5 michael.bemmer 2003-03-12 14:05:56 UTC
As mentioned on the qa dev list on March 5th I will close all resolved
<wontfix/duplicate/worksforme/invalid> issues. Please see this posting for
details. First step in IssueZilla is unfortunately to set them to verified.
Comment 6 michael.bemmer 2003-03-12 14:30:02 UTC
As mentioned on the qa dev list on March 5th I will close all resolved
<wontfix/duplicate/worksforme/invalid> issues. Please see this posting for details.