Bugzilla Bug 44546

I get the following error when I try to compile the above mentioned package:

--8<---8<---8<---8<---8<---8<-
[...]
making all in squidGuard-1.2.0
make[1]: Entering directory `/var/tmp/portage/squidguard-1.2.0-r1/work/squidGuard-1.2.0/src'
gcc -I.. -I. -I. -I/usr/local/BerkeleyDB/include -DHAVE_CONFIG_H -Os -mcpu=pentium3 -pipe -I/usr/local/BerkeleyDB/include -c main.c
making all in src
gcc -I.. -I. -I. -I/usr/local/BerkeleyDB/include -DHAVE_CONFIG_H -Os -mcpu=pentium3 -pipe -I/usr/local/BerkeleyDB/include -c sgLog.c
gcc -I.. -I. -I. -I/usr/local/BerkeleyDB/include -DHAVE_CONFIG_H -Os -mcpu=pentium3 -pipe -I/usr/local/BerkeleyDB/include -c sgDb.c
gcc -I.. -I. -I. -I/usr/local/BerkeleyDB/include -DHAVE_CONFIG_H -Os -mcpu=pentium3 -pipe -I/usr/local/BerkeleyDB/include -c sgDiv.c
sgDb.c: In function `sgDbInit':
sgDb.c:101: warning: passing arg 2 of pointer to function from incompatible pointer type
sgDb.c:101: warning: passing arg 4 of pointer to function makes pointer from integer without a cast
sgDb.c:101: error: too few arguments to function
sgDb.c:107: warning: passing arg 2 of pointer to function from incompatible pointer type
sgDb.c:107: warning: passing arg 4 of pointer to function makes pointer from integer without a cast
sgDb.c:107: error: too few arguments to function
make[1]: *** [sgDb.o] Error 1
make[1]: *** Waiting for unfinished jobs....
make[1]: Leaving directory `/var/tmp/portage/squidguard-1.2.0-r1/work/squidGuard-1.2.0/src'
make: *** [all] Error 1
--8<---8<---8<---8<---8<---8<-

Portage tree synced just a few hours ago.

# emerge info
Portage 2.0.50-r1 (default-x86-1.4, gcc-3.3.2, glibc-2.3.2-r9, 2.4.25)
=================================================================
System uname: 2.4.25 i686 AMD Athlon(tm) XP 1500+
Gentoo Base System version 1.4.3.13
Autoconf: sys-devel/autoconf-2.58-r1
Automake: sys-devel/automake-1.7.7
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CFLAGS="-Os -mcpu=pentium3 -pipe"
CHOST="i686-pc-linux-gnu"
COMPILER="gcc3"
CONFIG_PROTECT="/etc /opt/tomcat/conf /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.1/share/config /usr/kde/3.2/share/config /usr/kde/3/share/config /usr/lib/mozilla/defaults/pref /usr/share/config /var/bind /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-Os -mcpu=pentium3 -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs ccache sandbox"
GENTOO_MIRRORS="http://gentoo.oregonstate.edu http://distro.ibiblio.org/pub/Linux/distributions/gentoo"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY=""
SYNC="rsync://localhost/gentoo-portage"
USE="x86"

This bug seems to be related to BerkeleyDB-4.1.  Although there is a patch that
this ebuild applies to squidguard 1.2.0, it doesnt (to me) seem to work
properly.

I have found a workround however, and that is to install an older version of
db.  I installed 3.3.11 (which is masked so you will have to either accept
keywords, or emerge the .ebuild file directly) and then emerged squidguard and
it compiled and installed correctly.

Of course this is then using 3.3.11 rather than 4.1, but according to the
author of squidguard, the performance of squidguard running on BerkeleyDB-4.1
is rather slow anyway so perhaps this is no bad thing.

Most of all it seems to get a db version from /usr/local/include. Are there any
db includes in that dir?

Created an attachment (id=29003) [details]
emerge log

also failed for me on a clients box they use for vsat webcache... submitting
emerge info and emerge log. 

cache4 ipfm-0.11.5 # emerge info
Portage 2.0.50-r3 (default-x86-2004.0, gcc-3.3.3, glibc-2.3.3_pre20040207-r0,
2.6.4-gentoo-r1)
=================================================================
System uname: 2.6.4-gentoo-r1 i686 Pentium II (Deschutes)
Gentoo Base System version 1.4.4
Autoconf: sys-devel/autoconf-2.59-r3
Automake: sys-devel/automake-1.8.3
ACCEPT_KEYWORDS="x86 ~x86"
AUTOCLEAN="yes"
CFLAGS="-O3 -march=pentium2 -ffast-math -pipe"
CHOST="i686-pc-linux-gnu"
COMPILER="gcc3"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config
/usr/share/config /usr/share/texmf/dvipdfm/config/
/usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/
/usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O3 -march=pentium2 -ffast-math -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs buildpkg ccache fixpackages sandbox"
GENTOO_MIRRORS="http://gentoo.mirrors.pair.com/
http://mirror.datapipe.net/gentoo ftp://mirrors.tds.net/gentoo
http://mirrors.tds.net/gentoo ftp://ftp.gtlib.cc.gatech.edu/pub/gentoo
ftp://gentoo.ccccom.com ftp://gentoo.netnitco.net/pub/mirrors/gentoo/source/
http://gentoo.ccccom.com"
MAKEOPTS="-j3"
PKGDIR="/usr/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://rsync.us.gentoo.org/gentoo-portage/"
USE="X509 acl adns apache2 apm bcel berkdb bsh chroot crypt curl directfb doc
fam fbcon fullrpc gd gdbm gif informix innodb ipalias ipv6 java javamail
javascript jdepend jpeg jsch junit jython kerberos krb4 libg++ libwww log4j
maildir mbox memlimit mmx mono mpi mysql ncurses nls nptl objc oci8
optional-tasks oro ospfapi pam pcap perl pg-intdatetime pg-vacuumdelay php png
python radius readline regexp rhino ruby sasl slang socks5 spell sse ssl svg
svga tcpd tetex tiff usagi virus-scan x86 xalan xerces xml xml2 yaz zeo zlib"

Created an attachment (id=30930) [details]
add a NULL to all DB_TXN on DB->open. We dont need transaction there.

Hi

Please test this patch if it works ok. It compiles squidGuard with
db-4.1.25_p1-r3.

Thanks.

Mauricio,
I just cleanly emerged squidguard after adding your patch to the ebuild, and everything works fine for me. This is with db-4.1.25.
Thanks!

The patch works as expect well done. Now if we could just get it in portage so
all users have it we would be in good shape. Seems gentoo dev team is slow
about adding patches and correct ebuilds that users submit even tho they have
tested them.

Its a matter of who the bug is assigned to...

I have no complaints with the patch, but does it break with previous versions of DB?? 

Fixed in cvs