Bug 79872

Summary: rpm-4.2: locking with nptl necessitates bogus glibc/kernel requirements
Product: [Retired] Red Hat Raw Hide Reporter: Jeff Johnson <jbj>
Component: rpmAssignee: Jeff Johnson <jbj>
Status: CLOSED NOTABUG QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 1.0CC: wtogami
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2002-12-27 14:34:05 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jeff Johnson 2002-12-17 18:28:02 UTC 
The kernel supplies /dev/futex functionality.

glibc supplies the pthread API that uses nptl on top
of /dev/futex functionality.

db-4.1.24 uses the the pthread API, has run-time check
that API is functional. The runtime check requires
    a) the running kernel supplies functional /dev/futex
    b) glibc with nptl.

So, rpm carries
    Requires: kernel >= 2.4.20-0.pp.9
    Requires: glibc >= 2.3.1-15
attempting to insure that the platform on which
rpm runs has (at least) the necessary capabilities available
to use posix mutexes through nptl.

This, of course, is totally bogus if, say, a different
kernel w/o /dev/futex functionality is booted.
Comment 1 Jeff Johnson 2002-12-27 14:34:05 UTC 
Fixed by adding run time test with fallback to different
locking scheme.