This service will be undergoing maintenance at 20:00 UTC, 2017-04-03. It is expected to last about 30 minutes
Bug 638 - the rxvt rpm does not seem to include rxvt binary.
the rxvt rpm does not seem to include rxvt binary.
Status: CLOSED CURRENTRELEASE
Product: Red Hat Raw Hide
Classification: Retired
Component: rxvt (Show other bugs)
1.0
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Preston Brown
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1998-12-28 13:18 EST by David Lawrence
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 1998-12-30 15:53:14 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description David Lawrence 1998-12-28 13:18:20 EST
the rxvt rpm does not seem to include rxvt binary in
/usr/X11R6/bin.

A rpm -ql shows that it is not installing the binary.
Comment 1 Jeff Johnson 1998-12-30 14:59:59 EST
This problem is with dist-6.0/rxvt-2.4.7-3

Here's the compiler output:

make[1]: Entering directory `/usr/src/redhat/BUILD/rxvt-2.4.7/src'
gcc -DHAVE_CONFIG_H -DDEBUG_STRICT  -c  -I/usr/X11R6/include   -I.
-I.. -I.  -O2 -m486 -fno-strength-reduce utmp.c
utmp.c: In function `makeutent':
utmp.c:232: `WTMPX_FILE' undeclared (first use in this function)
utmp.c:232: (Each undeclared identifier is reported only once
utmp.c:232: for each function it appears in.)
utmp.c: In function `cleanutent':
utmp.c:291: `WTMPX_FILE' undeclared (first use in this function)
make[1]: *** [utmp.o] Error 1

and the configure output looks fishy -- I don't think we  always have
utmp/wtmp files in the build environments ...

checking for host in utmp struct... yes
checking where utmp is located...
checking where wtmp is located... /var/log/wtmp
Comment 2 Jeff Johnson 1998-12-30 15:53:59 EST
Fixed in dist-6.0/rxvt-2.4.7-4

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