Bug 79872 - rpm-4.2: locking with nptl necessitates bogus glibc/kernel requirements
rpm-4.2: locking with nptl necessitates bogus glibc/kernel requirements
Status: CLOSED NOTABUG
Product: Red Hat Raw Hide
Classification: Retired
Component: rpm (Show other bugs)
1.0
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jeff Johnson
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2002-12-17 13:28 EST by Jeff Johnson
Modified: 2008-05-01 11:38 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2002-12-27 09:34:05 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Jeff Johnson 2002-12-17 13:28:02 EST
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 09:34:05 EST
Fixed by adding run time test with fallback to different
locking scheme.

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