Bug 6062 - Multiple shared libraries with same methods defined
Multiple shared libraries with same methods defined
Product: Red Hat Linux
Classification: Retired
Component: python (Show other bugs)
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Matt Wilson
Depends On:
  Show dependency treegraph
Reported: 1999-10-18 14:49 EDT by mike.olson
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 1999-11-18 18:40:31 EST
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 mike.olson 1999-10-18 14:49:42 EDT
I have 2 shared libraries that both define symbols of the
same name.  When I import these modules into python and call
the method with the shared name, I always exectue the method
of the last module imported.

Ex: If I have 2 shared modules written in C, each with a
different module name, but both having a function called
foo, the following code breaks.

import A
import B
A.foo() #Really calls B.foo

My code that uses this was originally written and worked
with the non-redhat rpms available at

Comment 1 Michael K. Johnson 1999-11-18 18:40:59 EST
Not Found

The requested URL /python/files/python-1.5.2-2.src.rpm was not found
on this server.

Binary rpms don't do us much good...  :-)

Unfortunately, the patch that I believe breaks this for you appears
to have been added to fix something else.  I'm assigning this bug
to the developer who added that patch.  (Matt, it's
python-1.5.2-dl-global.patch -- what's this about libtool, and why
is the patch there in the first place?)
Comment 2 Matt Wilson 2001-01-26 21:08:46 EST
Unfortunately I can't address this until we start using the Python 2.0 package.

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