Bug 5431 - lsof RPM can't be rebuilt with 2.2.12 kernel
lsof RPM can't be rebuilt with 2.2.12 kernel
Product: Red Hat Linux
Classification: Retired
Component: lsof (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: David Lawrence
Depends On:
  Show dependency treegraph
Reported: 1999-09-29 05:50 EDT by Alec Voropay
Modified: 2008-05-01 11:37 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 1999-10-01 15:03:40 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 Alec Voropay 1999-09-29 05:50:43 EDT

 I just have installed new kernel 2.2.12 from
ftp://linux.kernel.org on my RedHat 5.2 (Appollo) system.
New utilities for 2.2 kernel from RedHat was also
All working OK.

 But lsof utility stos to work. And more : I can't rebuild
lsof-4.40-1.src.rpm om my system now !

$ rpm -i lsof-4.40-1.src.rpm
$ cd /usr/src/redhat/SPECS
$ rpm -ba lsof.spec
/usr/include/socketbits.h:198: `__cmsg_nxthdr' previously
defined here
In file included from ../dlsof.h:343,
                 from ../lsof.h:70,
                 from ckkv.c:43:
/usr/include/netinet/in.h:42: conflicting types for
/usr/src/linux/include/linux/in.h:37: previous declaration
/usr/include/netinet/in.h:43: parse error before `58'
make[1]: *** [ckkv.o] Error 1
make[1]: Leaving directory
make: *** [lib/liblsof.a] Error 2
Bad exit status from /var/tmp/rpm-tmp.71569 (%build)

 So, I have downloaded lsof_4.45 from $URL and build it.
All OK. But seems, should be better to have RPM from RedHat.

 Could you issue new lsof 4.45 RPM version for 2.2 kernel
(for RedHat 5.2) ?

with best regards
Comment 1 Jeff Johnson 1999-10-01 15:03:59 EDT
Try the lsof-4.45-1.src.rpm from Raw Hide.
Comment 2 Alec Voropay 1999-11-23 14:42:59 EST
October 23, 1999 new version of lsof was released :

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