A couple of problems I've found so far:
1. When building with krb5 enabled (linking against krb5-1.2.1), I get the
following error:
gcc -I/s/krb5-1.2.1/include -I/s/gdbm-1.8.0/include -g -O2 -Wall Werror
-DHAVE_CONFIG_H -I.. -I./include -I./common -DCHOWN=\"/usr/bin/chown\"
-DCHGRP=\"/usr/bin/chgrp\" -DPRINTCAP_PATH=\"/s/lprng-3.7/etc/printcap\"
-DLPD_PRINTCAP_PATH=\"/s/lprng-3.7/etc/lpd_printcap\"
-DLPD_PERMS_PATH=\"/s/lprng-3.7/etc/lpd.perms\" -DLPD_CONF_PATH=\"/s/lprng-3.7/
etc/lpd.conf\" -DREQUIRE_CONFIGFILES=\"1\" -DFILTER_PATH=\"\"
-DLD_LIBRARY_PATH=\"\" -DLOCKFILE=\"/var/run/lpd\" -DCLEAR=\"/usr/bin/clear\"
-DUSERID=\"daemon\" -DGROUPID=\"daemon\" -DLOCALEDIR=\"/s/lprng-3.7/share/local
e\" -c -o krb5_auth.o ./common/krb5_auth.c
./common/krb5_auth.c: In function `Krb5_receive':
./common/krb5_auth.c:1371: warning: implicit declaration of function
`Do_secure_work'
With the -Werror flag set in the build, this will cause the build to die.
Removing the -Werror flag from src/Makefile allows the build to continue on
without any further warnings.
2. When building against GDBM 1.8.0, I find lpd (and checkpc -f) get stuck
trying to set a lock on the gdbm file for the first printer. Here's an
excerpt from the truss output on "checkpc -f":
getuid() = 0 [0]
setuid(0) = 0
seteuid(0) = 0
getuid() = 0 [0]
xstat(2, "/usr/spool/remote-laser", 0x08047714) = 0
open64("/usr/spool/remote-laser", O_RDONLY|O_NDELAY) = 5
fcntl(5, F_SETFD, 0x00000001) = 0
fstat64(5, 0x0804770C) = 0
getdents64(5, 0x080A8FC8, 1048) = 248
xstat(2, "control.laser", 0x08047A84) = 0
xstat(2, "control.laser", 0x08047714) = 0
xstat(2, "status.laser", 0x08047A84) = 0
xstat(2, "status.laser", 0x08047714) = 0
xstat(2, "status", 0x08047A84) = 0
xstat(2, "status", 0x08047714) = 0
xstat(2, "log", 0x08047A84) = 0
xstat(2, "log", 0x08047714) = 0
xstat(2, "acct", 0x08047A84) = 0
xstat(2, "acct", 0x08047714) = 0
xstat(2, "db.laser", 0x08047A84) = 0
xstat(2, "db.laser", 0x08047714) = 0
xstat(2, "lpq.0", 0x08047A84) = 0
xstat(2, "lpq.0", 0x08047714) = 0
getdents64(5, 0x080A8FC8, 1048) = 0
close(5) = 0
open("control.laser", O_RDONLY|O_NOCTTY) = 5
fxstat(2, 5, 0x08047704) = 0
xstat(2, "control.laser", 0x08047644) = 0
close(5) = 0
open("status.laser", O_RDONLY|O_NOCTTY) = 5
fxstat(2, 5, 0x08047714) = 0
xstat(2, "status.laser", 0x08047654) = 0
close(5) = 0
open("status", O_RDONLY|O_NOCTTY) = 5
fxstat(2, 5, 0x08047654) = 0
xstat(2, "status", 0x08047594) = 0
close(5) = 0
open("log", O_RDONLY|O_NOCTTY) = 5
fxstat(2, 5, 0x08047664) = 0
xstat(2, "log", 0x080475A4) = 0
close(5) = 0
open("acct", O_RDONLY|O_NOCTTY) = 5
fxstat(2, 5, 0x08047654) = 0
xstat(2, "acct", 0x08047594) = 0
close(5) = 0
unlink("lpq") Err#2 ENOENT
unlink("db.laser") = 0
open64(".", O_RDONLY|O_NDELAY) = 5
fcntl(5, F_SETFD, 0x00000001) = 0
fstat64(5, 0x0804758C) = 0
umask(0) = 077
open("db.laser", O_RDWR|O_APPEND|O_CREAT|O_NOCTTY, 0600) = 6
umask(077) = 0
fxstat(2, 6, 0x080475A4) = 0
fcntl(6, F_SETLKW, 0x08047508) = 0
fcntl(6, F_SETLKW, 0x08047508) = 0
fcntl(6, F_SETLKW, 0x08047508) = 0
fcntl(6, F_SETLKW, 0x08047508) = 0
<repeat ad nauseum>
Disabling the GDBM support clears up the problem.
--
============================================================================
John Perkins | University of Wisconsin-Madison
Associate Researcher | Department of Computer Science
[EMAIL PROTECTED] | 1210 W. Dayton St.
608-262-0438/608-262-9997 FAX | Madison, WI 53706-1685
============================================================================
-----------------------------------------------------------------------------
YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRNG MAILING LIST
The address you post from MUST be your subscription address
If you need help, send email to [EMAIL PROTECTED] (or lprng-requests
or lprng-digest-requests) with the word 'help' in the body. For the impatient,
to subscribe to a list with name LIST, send mail to [EMAIL PROTECTED]
with: | example:
subscribe LIST <mailaddr> | subscribe lprng-digest [EMAIL PROTECTED]
unsubscribe LIST <mailaddr> | unsubscribe lprng [EMAIL PROTECTED]
If you have major problems, send email to [EMAIL PROTECTED] with the word
LPRNGLIST in the SUBJECT line.
-----------------------------------------------------------------------------
