Bugzilla Bug 19006

On 'emerge cryptoapi' I get the following error:

cryptoapi.c:466: parse error before
"this_object_must_be_defined_as_export_objs_in_the_Makefile"
cryptoapi.c:466: warning: type defaults to `int' in declaration of
`this_object_must_be_defined_as_export_objs_in_the_Makefile'
cryptoapi.c:466: warning: data definition has no type or storage class
cryptoapi.c:467: parse error before
"this_object_must_be_defined_as_export_objs_in_the_Makefile"
cryptoapi.c:467: warning: type defaults to `int' in declaration of
`this_object_must_be_defined_as_export_objs_in_the_Makefile'
cryptoapi.c:467: warning: data definition has no type or storage class
cryptoapi.c:468: parse error before
"this_object_must_be_defined_as_export_objs_in_the_Makefile"
cryptoapi.c:468: warning: type defaults to `int' in declaration of
`this_object_must_be_defined_as_export_objs_in_the_Makefile'
cryptoapi.c:468: warning: data definition has no type or storage class
cryptoapi.c:469: parse error before
"this_object_must_be_defined_as_export_objs_in_the_Makefile"
cryptoapi.c:469: warning: type defaults to `int' in declaration of
`this_object_must_be_defined_as_export_objs_in_the_Makefile'
cryptoapi.c:469: warning: data definition has no type or storage class
cryptoapi.c:470: parse error before
"this_object_must_be_defined_as_export_objs_in_the_Makefile"
cryptoapi.c:470: warning: type defaults to `int' in declaration of
`this_object_must_be_defined_as_export_objs_in_the_Makefile'
cryptoapi.c:470: warning: data definition has no type or storage class
cryptoapi.c:471: parse error before
"this_object_must_be_defined_as_export_objs_in_the_Makefile"
cryptoapi.c:471: warning: type defaults to `int' in declaration of
`this_object_must_be_defined_as_export_objs_in_the_Makefile'
cryptoapi.c:471: warning: data definition has no type or storage class
cryptoapi.c:472: parse error before
"this_object_must_be_defined_as_export_objs_in_the_Makefile"
cryptoapi.c:472: warning: type defaults to `int' in declaration of
`this_object_must_be_defined_as_export_objs_in_the_Makefile'
cryptoapi.c:472: warning: data definition has no type or storage class
cryptoloop.c:51:3: warning: #warning LO_CRYPT_CRYPTOAPI not (yet) defined in
kernel header
cryptoloop.c:103:2: warning: #warning USE_LO_IV_MODE_SECTOR enabled -- hope you
know what this means
cryptoloop.c: In function `transfer_cryptoapi':
cryptoloop.c:106: `LO_IV_SECTOR_SIZE' undeclared (first use in this function)
cryptoloop.c:106: (Each undeclared identifier is reported only once
cryptoloop.c:106: for each function it appears in.)
cryptoloop.c:138:3: #error You dont seem have a kernel patched for this to work...
cryptoloop.c: In function `cryptoapi_status':
cryptoloop.c:141: `LO_IV_SECTOR_SIZE' undeclared (first use in this function)
cryptoloop.c:144: structure has no member named `lo_iv_mode'
cryptoloop.c:144: `LO_IV_MODE_SECTOR' undeclared (first use in this function)
gmake[1]: *** [cryptoloop.o] Error 1
gmake[1]: *** Waiting for unfinished jobs....
gmake[1]: *** [cryptoapi.o] Error 1
gmake[1]: Leaving directory
`/var/tmp/portage/cryptoapi-2.4.7.0/work/cryptoapi-2.4.7.0/api'
make: *** [all-recursive] Error 1

!!! ERROR: app-crypt/cryptoapi-2.4.7.0 failed.
!!! Function src_compile, Line 28, Exitcode 2
!!! (no error message)

I have CryptoAPI and loopback enabled in the kernel.  I've 'emerge sync'd.  I've
done everything I can think of to make the problem go away, but apparently it's
something to do with the ebuild or with the program itself.  As I understand it,
this package is just for the cryptoapi modules, there shouldn't be any strange
dependencies, right?  (The package dependencies are satisfied, of course.)

Reproducible: Always
Steps to Reproduce:
1. 'emerge cryptoapi'




Portage 2.0.47-r10 (default-x86-1.4, gcc-3.2.2, glibc-2.3.1-r4)
=================================================================
System uname: 2.4.19-gentoo-r10 i686 AMD Athlon(tm) processor
GENTOO_MIRRORS="http://gentoo.oregonstate.edu/
http://distro.ibiblio.org/pub/Linux/distributions/gentoo"
CONFIG_PROTECT="/etc /var/qmail/control /usr/kde/2/share/config
/usr/kde/3/share/config /usr/X11R6/lib/X11/xkb /usr/kde/3.1/share/config
/usr/share/config"
CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d"
PORTDIR="/usr/portage"
DISTDIR="/usr/portage/distfiles"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR_OVERLAY=""
USE="x86 oss 3dnow apm avi crypt cups encode gif jpeg libg++ mmx mpeg ncurses
pdflib png quicktime spell truetype xml2 xmms xv zlib gdbm berkdb slang readline
arts svga tcltk java X sdl gpm tcpd pam libwww ssl perl python imlib oggvorbis
qt kde motif opengl aalib alsa directfb esd fbcon -gnome gphoto2 -gtk mbox
-mikmod mozilla mysql -nls static usb"
COMPILER="gcc3"
CHOST="i686-pc-linux-gnu"
CFLAGS="-march=athlon -O2 -pipe -fomit-frame-pointer"
CXXFLAGS="-march=athlon -O2 -pipe -fomit-frame-pointer"
ACCEPT_KEYWORDS="x86"
MAKEOPTS="-j2"
AUTOCLEAN="yes"
SYNC="rsync://rsync.us.gentoo.org/gentoo-portage/"
FEATURES="sandbox ccache"

This problrem is related to a compilation parameter of the e-build.
It as been wrote to compile with "iv-compatibility" this mean that in the ebuild tries to compile the package with the iv-mode backward compatibility, this parameter is useful just in case you need to mount old encrypted FS created with crypto patch for kernel 2.4.3 or previous.
The problems is that both gentoo kernel and wolk kernel crypto sections are not patched for this backward compatibility, so when the ebuild tries to compile with this flag enabled just don't find a suitable kernel and fail.
Edit the package script "/usr/portage/app-crypt/cryptoapi/cryptoapi-2.4.7.0.ebuild", the line 19 should be something like "econf --enable-iv-mode-sector" change it in just "econf" without other parameters and it will build, this solution seems to work great for my laptop.

removed the legacy support. Thanks!