Bug 123337 - _dl_load_lock symbol not defined in static version of libc
_dl_load_lock symbol not defined in static version of libc
Status: CLOSED NOTABUG
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: glibc (Show other bugs)
3.0
ia64 Linux
medium Severity low
: ---
: ---
Assigned To: Jakub Jelinek
Brian Brock
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2004-05-17 06:47 EDT by Chandraprakash Jain
Modified: 2007-11-30 17:07 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-05-17 06:52:10 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Chandraprakash Jain 2004-05-17 06:47:46 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1)
Gecko/20020830

Description of problem:
For my application, I need to link libdl.a, which contains a symbol
(_dl_load_lock) that is only in the static versions of libc (libc.a,
libc_p.a) and is not in libc.so.

Why is this so?

Thanks.


Version-Release number of selected component (if applicable):
glibc-2.3.2-95.17  

How reproducible:
Always

Steps to Reproduce:
used nm to verify this.    

Additional info:
Comment 1 Jakub Jelinek 2004-05-17 06:52:10 EDT
Is it statically linked program or dynamically linked?
In any case, _dl_load_lock is/used to be a glibc private symbol and no application
nor third party library should ever use it.
See dl_iterate_phdr API for querying loaded libraries in a program.
If your application uses it, it should be fixed, if some third party
library uses this, you should file a bugreport with the third party
library provider.

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