Bug 216696 - global symbol collisions in OpenIPMI libraries
global symbol collisions in OpenIPMI libraries
Product: Fedora
Classification: Fedora
Component: OpenIPMI (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Ales Ledvinka
Depends On:
Blocks: 216170
  Show dependency treegraph
Reported: 2006-11-21 10:58 EST by Joe Orton
Modified: 2016-09-20 00:32 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-05-06 21:01:03 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Joe Orton 2006-11-21 10:58:52 EST
Description of problem:

The following collisions between global symbols defined by the OpenIPMI
libraries were found:

Clashes for /usr/lib/libOpenIPMIcmdlang.so.0.0.5:
  with /usr/lib/libOpenIPMIui.so.1.0.1 => fru_change sdrs_fetched

Clashes for /usr/lib/libOpenIPMIposix.so.0.0.1:
  with /usr/lib/libOpenIPMIpthread.so.0.0.1 => sel_set_fd_handlers
ipmi_sel_set_read_fds_handler (...14 symbols omitted...) posix_mutex_free

are these intentional?
Comment 1 Phil Knirsch 2007-04-17 09:00:36 EDT
How did you test that?

And assuming that i haven't fiddled with the build process of OpenIPMI i suspect
those are intentional, yes.

Read ya, Phil
Comment 2 Joe Orton 2007-04-27 06:37:32 EDT
Scripts at http://people.redhat.com/jorton/symclash/


$ ~/symclash.py /usr/lib/libOpenIPMIcmdlang.so.0.0.5
/usr/lib/libOpenIPMIposix.so.0.0.1 /usr/lib/libOpenIPMIpthread.so.0.0.1

it's bad if only because of unnecessary code duplication -> bloat.
Comment 3 Bug Zapper 2008-04-03 14:41:44 EDT
Based on the date this bug was created, it appears to have been reported
against rawhide during the development of a Fedora release that is no
longer maintained. In order to refocus our efforts as a project we are
flagging all of the open bugs for releases which are no longer
maintained. If this bug remains in NEEDINFO thirty (30) days from now,
we will automatically close it.

If you can reproduce this bug in a maintained Fedora version (7, 8, or
rawhide), please change this bug to the respective version and change
the status to ASSIGNED. (If you're unable to change the bug's version
or status, add a comment to the bug and someone will change it for you.)

Thanks for your help, and we apologize again that we haven't handled
these issues to this point.

The process we're following is outlined here:

We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.
Comment 4 Bug Zapper 2008-05-06 21:01:01 EDT
This bug has been in NEEDINFO for more than 30 days since feedback was
first requested. As a result we are closing it.

If you can reproduce this bug in the future against a maintained Fedora
version please feel free to reopen it against that version.

The process we're following is outlined here:

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