Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 7866

Summary: linking against libe2p fails
Product: [Retired] Red Hat Linux Reporter: Matthew Gauthier <elleron>
Component: e2fsprogsAssignee: Florian La Roche <laroche>
Status: CLOSED NOTABUG QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 6.1   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 1999-12-17 15:16:31 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Matthew Gauthier 1999-12-17 11:16:32 UTC
On redhat 6.1/intel linking against any of the ext2 libs fails when
using the -l<libname> switch, but succedes when the full path is passed
on the cc command line. ie,

gcc obj1.o obj2.o /lib/ # works
gcc obj1.o obj2.o -le2p              # fails

Comment 1 Jeff Johnson 1999-12-17 15:16:59 UTC
Make sure that you have e2fsprogs-devel installed. If you are not installing
from a package, make sure that you have run ldconfig. The actual file that
should be used by the linker when given -le2p is /usr/lib/ created
by either the package or the ldconfig command.