Bug 27093

Summary: qpopper-4.0.1 - make fails
Product: Ports & Packages Reporter: kar_alerts <kar_alerts>
Component: Individual Port(s)Assignee: Mario Sergio Fujikawa Ferreira <lioux>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Latest   
Hardware: Any   
OS: Any   
Attachments:
Description Flags
patch-qpopper none

Description kar_alerts 2001-05-05 15:40:00 UTC 
When I type "make" from /usr/ports/mail/qpopper, the command fails with the error code 1. Here are the messages I get,


*** - message start - ***

cc -c -I.. -I.. -I.  -I../mmangle -I../common -I/usr/include  -O -pipe  -idiraft
er /usr/local/include -freg-struct-return -DHAVE_CONFIG_H  -DSETPROCTITLE  -DFREEBSD -DUNIX popauth.c -o popauth.o
popauth.c: In function `check_db_err':
popauth.c:356: `DBM' undeclared (first use in this function)
popauth.c:356: (Each undeclared identifier is reported only once
popauth.c:356: for each function it appears in.)
popauth.c:356: syntax error before `)'
popauth.c: In function `main':
popauth.c:659: `DBM' undeclared (first use in this function)
popauth.c:659: `db' undeclared (first use in this function)
popauth.c:660: syntax error before `char'
popauth.c:693: `mode' undeclared (first use in this function)
popauth.c:879: `auth_dir' undeclared (first use in this function)
popauth.c:921: incompatible types in assignment
popauth.c:1034: `f' undeclared (first use in this function)
popauth.c:1056: incompatible types in assignment
popauth.c:1097: incompatible types in assignment
popauth.c:1097: incompatible types in assignment
popauth.c:1106: incompatible types in assignment
popauth.c:1183: incompatible types in assignment
popauth.c:1428: `DBM_REPLACE' undeclared (first use in this function)
*** Error code 1      

Stop in /usr/ports/mail/qpopper/work/qpopper4.0.1/popper.
*** Error code 1

Stop in /usr/ports/mail/qpopper/work/qpopper4.0.1.
*** Error code 1

Stop in /usr/ports/mail/qpopper.
*** Error code 1

Stop in /usr/ports/mail/qpopper.
*** Error code 1

Stop in /usr/ports/mail/qpopper.  


*** - message end - ***

Fix: 

don't know
How-To-Repeat: cd /usr/ports/mail/qpopper
make
Comment 1 lioux 2001-05-05 16:48:55 UTC 
Humm, there seems to have something odd with your CFLAGS. Could you try
cleaning your CFLAGS? I mean, please comment all CFLAGS entries inside your
/etc/make.conf. Let me know what happens.

I am suspecting that the gdbm port is conflicting. This might be due
to a -I/usr/local/include inside your CFLAGS.

Also, please make sure you have the absolute latest version
of the qpopper port.

$ rm -Rf /usr/ports/mail/qpopper
$ cvsup again

-- 
Mario S F Ferreira - UnB - Brazil - "I guess this is a signature."
lioux at ( freebsd dot org | linf dot unb dot br )
flames to beloved devnull@someotherworldbeloworabove.org
feature, n: a documented bug | bug, n: an undocumented feature
Comment 2 lioux 2001-05-05 18:38:50 UTC 
On Sun, May 06, 2001 at 01:38:54AM +0900, Hajimu UMEMOTO wrote:
> >>>>> On Sat, 5 May 2001 13:25:52 -0300
> >>>>> "Mario Sergio Fujikawa Ferreira" <lioux@uol.com.br> said:
> 
> > I met same problem here.  If gdbm is installed, configure find it out
> > and set `#define HAVE_GDBM_H 1' into config.h.  It causes the problem.
> > I did delete HAVE_GDBM_H line from config.h after `make configure' for
> > workaround.
>  
> lioux> 	Could you try the following patch?
> 
> Unfortunately, I tried it, then it didn't help.  It works not for
> `HAVE_GDBM_H' but for `GDBM'.  In configure.in, gdbm.h is absolutely
> checked out by:
> 
>   AC_CHECK_HEADER( gdbm.h, GDBM_H="yes"; AC_DEFINE(HAVE_GDBM_H), GDBM_H="no" )
> 
> reagadless of --disable-gdbm option.

	My mistake. Try this patch. I removed the option from
configure.in and then used autoconf.
	- Removed files: files/patch-configure
	- Added files: files/patch-configure.in

-- 
Mario S F Ferreira - UnB - Brazil - "I guess this is a signature."
lioux at ( freebsd dot org | linf dot unb dot br )
flames to beloved devnull@someotherworldbeloworabove.org
feature, n: a documented bug | bug, n: an undocumented feature
Comment 3 Ying-Chieh Liao freebsd_committer freebsd_triage 2001-05-17 19:18:41 UTC 
Responsible Changed
From-To: freebsd-ports->lioux

over to maintainer
Comment 4 Mario Sergio Fujikawa Ferreira freebsd_committer freebsd_triage 2001-05-25 13:45:20 UTC 
State Changed
From-To: open->closed

Problem seems to be fixed in version 4.0.2 of the port. 
Besides, feedback time out from originator. 
Thanks for the report!