Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 10756 - undefined symbol: fdio
undefined symbol: fdio
Status: CLOSED DUPLICATE of bug 33916
Product: Red Hat Linux
Classification: Retired
Component: rpmfind (Show other bugs)
i386 Linux
low Severity medium
: ---
: ---
Assigned To: Jeff Johnson
: FutureFeature
Depends On:
  Show dependency treegraph
Reported: 2000-04-12 12:05 EDT by david.heim
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-04-03 10:08:23 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 david.heim 2000-04-12 12:05:39 EDT
I installed rpmfind from Redhat 6.2 on a partially updated RedHat 6.0
system.  All the dependencies were satisfied. When I tried to run it I got
	rpmfind: error in loading shared libraries: rpmfind: undefined
	symbol: fdio
Comment 1 Jeff Johnson 2000-04-12 12:20:59 EDT
Upgrade to rpm-3.0.4 from 6.2 as well.
Comment 2 Anonymous 2000-04-12 13:17:59 EDT
Okay thanks.

The fact that the dependencies for rpmfind don't "require" RPM 3.0.4 while
rpmfind does, strikes me as a (minor) bug.
Comment 3 Greg Lopp 2000-09-10 01:05:50 EDT
Experincing a similar problem with the combination of rpmfind-1.4-3 and
rpm-4.0-0.67.6x.  Whenever I try to run it, I get :
rpmfind: error in loading shared libraries: /usr/lib/librpm.so.0: undefined
symbol: ufdio

Hardly worth reporting, except for two differences :
1) Different symbol (or at least a different spelling)
2) Previous problem supposedly resolved by upgrading rpm package.  My problem
exists with the latest(?) version.
Comment 4 Jeff Johnson 2001-04-03 10:08:18 EDT

*** This bug has been marked as a duplicate of 33916 ***
Comment 5 Daniel Veillard 2001-07-17 19:18:18 EDT
Had been fixed in all recent releases,


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