From owner-freebsd-isp Thu Nov 13 15:19:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA01671 for isp-outgoing; Thu, 13 Nov 1997 15:19:37 -0800 (PST) (envelope-from owner-freebsd-isp) Received: from super-g.inch.com (super-g.com [207.240.140.161]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA01657; Thu, 13 Nov 1997 15:19:29 -0800 (PST) (envelope-from spork@super-g.com) Received: from localhost (localhost [127.0.0.1]) by super-g.inch.com (8.8.7/8.8.5) with SMTP id SAA26596; Thu, 13 Nov 1997 18:14:49 -0500 (EST) Date: Thu, 13 Nov 1997 18:14:49 -0500 (EST) From: spork X-Sender: spork@super-g.inch.com To: questions@freebsd.org cc: qpopper@qualcomm.com, freebsd-isp@freebsd.org Subject: Popper Port Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I'm trying to install the popper port (2.4b2 qpopper) and some strange things have been happening. If I compile it with defaults and "-DSERVER_MODE", it works, but has some bugs; it will occasionally zero out user's .popbull files, and if a user has an empty spool, it dumps core. I tried adding the "-DBULLDB" to solve the first problem by keeping all bulletin information in a database, but it fails like so when including the BULLDB option: cc -c -I. -DHAVE_CONFIG_H -DSETPROCTITLE -DBSD44_DBM -DBIND43 -DAPOP='"'/usr/local'/etc/popper/pop.auth"' -DPOPUID='"pop"' -DNONAUTHFILE='"/etc/ftpusers"' -DSKEY -DSERVER_MODE -DBULLDB pop_bull.c -o pop_bull.o pop_bull.c: In function `pop_bull': pop_bull.c:171: `LOCK_EX' undeclared (first use this function) pop_bull.c:171: (Each undeclared identifier is reported only once pop_bull.c:171: for each function it appears in.) pop_bull.c:178: `LOCK_UN' undeclared (first use this function) *** Error code 1 Stop. This is on 2.1.7.1, and I do see both functions declared in the system headers. There are also flock functions in popper: util [/usr/ports/mail/popper-2.4b2]# grep LOCK_EX work/qpopper2.4b2/* work/qpopper2.4b2/flock.c: arg.l_type = (LOCK_EX & operation) ? F_WRLCK : work/qpopper2.4b2/flock.h:#define LOCK_EX 2 /* exclusive lock */ I'm lost... I was looking to downgrade to 2.3 or 2.2 to take care of the core dumping, but the bulletin database fails the same way in all versions. Anyone have this working? Thanks, Charles Sprickman spork@super-g.com ---- "I'm not a prophet or a stone-age man Just a mortal with potential of a superman I'm living on" -DB