Bugzilla Bug 37281

Compiling libggz-0.0.7 with libgcrypt-1.1.91 results in an error.  Dropping the
USE flags and removing C/XXFLAGS did not change the error.  Compiling
libggz-0.0.7 with libgcrypt-1.1.12 does not produce this error.

Reproducible: Always
Steps to Reproduce:
1.  Emerge libgcrypt-1.1.91
2.  Emerge libggz-0.0.7
Actual Results:  
...
gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I ../../src -Os -march=i686 -pipe
-fomit-frame-pointer -D_REENTRANT -I /usr/include -Wall -MT hashfunc.lo -MD -MP
-MF .deps/hashfunc.Tpo -c hashfunc.c  -fPIC -DPIC -o .libs/hashfunc.lo
hashfunc.c: In function `hash_create_private':
hashfunc.c:12: warning: `GcryMDHd' is deprecated (declared at
/usr/include/gcrypt.h:1033)
hashfunc.c:35: error: too few arguments to function `gcry_md_open'
hashfunc.c:35: warning: assignment makes pointer from integer without a cast
make[4]: *** [hashfunc.lo] Error 1
make[4]: *** Waiting for unfinished jobs....
gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I ../../src -Os -march=i686 -pipe
-fomit-frame-pointer -D_REENTRANT -I /usr/include -Wall -MT base64.lo -MD -MP
-MF .deps/base64.Tpo -c base64.c -o base64.o >/dev/null 2>&1
mv -f .libs/base64.lo base64.lo
make[4]: Leaving directory
`/var/tmp/portage/libggz-0.0.7/work/libggz-0.0.7/src/security'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory
`/var/tmp/portage/libggz-0.0.7/work/libggz-0.0.7/src/security'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory
`/var/tmp/portage/libggz-0.0.7/work/libggz-0.0.7/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/libggz-0.0.7/work/libggz-0.0.7'
make: *** [all] Error 2

!!! ERROR: dev-games/libggz-0.0.7 failed.
!!! Function src_compile, Line 25, Exitcode 2
!!! (no error message)


Expected Results:  
libggz-0.0.7 should have compiled successfully.

Portage 2.0.49-r20 (default-x86-1.4, gcc-3.3.2, glibc-2.3.3_pre20031222-r0,
2.6.1-rc1-mm1)
=================================================================
System uname: 2.6.1-rc1-mm1 i686 Pentium III (Coppermine)
Gentoo Base System version 1.4.3.12
distcc 2.12 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632)
[disabled]
ccache version 2.3 [enabled]
ACCEPT_KEYWORDS="x86 ~x86"
AUTOCLEAN="yes"
CFLAGS="-Os -march=i686 -pipe -fomit-frame-pointer"
CHOST="i686-pc-linux-gnu"
COMPILER="gcc3"
CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config
/usr/kde/3/share/config /usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d"
CXXFLAGS="-Os -march=i686 -pipe -fomit-frame-pointer"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs ccache sandbox"
GENTOO_MIRRORS="http://gentoo.mirrors.pair.com/"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://rsync.us.gentoo.org/gentoo-portage"
USE="X apm avi berkdb bonobo crypt cups curl dvd esd ethereal faad ffmpeg flac
foomaticdb gdbm gif gnome gphoto2 gpm gtk gtk2 gtkhtml guile imap imlib java
jpeg libg++ libwww mad maildir mikmod motif mozilla moznocompose moznoirc
moznomail mpeg ncurses nls offensive ofx oggvorbis opengl pam pcap pcmcia pda
pdflib perl png python qt quicktime readline samba sasl scanner sdl slang snmp
spell sse ssl svga tcltk tcpd transcode truetype vim-with-x wxwindows x86 xml2
xv zlib"

the reason disabling crypt in USE didnt work is because their configure.ac is
wrong

god, this kind of stuff pisses me off ;)

Does is still fail with libggz-0.0.8?

Yes - with and without USE="crypt", libggz-0.8 fails to compile with
libgcrypt-1.1.91 and both times gives an almost identical error message to one
in my first post.  Arg!

*** Bug 54759 has been marked as a duplicate of this bug. ***

I think this is the same problem of 41408.

libgcrypt 1.2.0 (1.1.9x are the pre-version of 1.2.0) is at alpha stage, Aegyptian2 is not complete. GnuPG 1.9.0 is actually masked (and this is right). Also libgcrypt should be, or at least SLOTed.

libgcrypt should not be slotted ... that's the completely wrong way to go

i talked to the libggz devs and they say this should be fixed with the next release (the one after 0.0.9)

libgcrypt-1.1.9x is an alpha, not compatible with the stable version, why
shouldn't be SLOTed?

SLOTing isnt just some magical process that 'happens'

unless upstream designs their versions to be so (and the gnu peeps have def NOT designed it like this), then the library and any package that uses that library has to be hacked apart

besides, like you say, 1.1.9x is alpha ... 1.2.x is out and is the new stable version so that point is moot now

appears to be fixed in upstream cvs ... just need the next version to be
released :)

The next version seems to be released

I think I missed this... is this still valid with the newer libgcrypt versions?
 Nobody really mentioned which application's upstream fixed this.

the 0.0.11 versions fix this (which Bug 94362 is blocking this bug)

Created an attachment (id=77394) [edit]
libggz-0.0.9-gcrypt.patch

gcrypt_mod_open prototype has changed. Providing a fix to that.

Created an attachment (id=77395) [edit]
libggz-0.0.9.ebuild

change to the ebuild to apply the patch

I've added the patch to CVS...