Re: cipe-1.6.0 kernel 2.6.17.5 kubuntu 6.0.6
"Dick St.Peters" <[email protected]> Sun, 16 Jul 2006 14:26:37 -0400
| Newsgroups | gmane.comp.encryption.cipe |
|---|---|
| Message-ID | <[email protected]> |
Dirk Jakobsmeier writes:
> Hello all,
>
> i´m trying to get cipe compiled on an 2.6.17.5 kernel. Applied
> cipe-2.6.14.patch and the changes to cipe/output.c. While compiling i got the
> following:
>
> /cipe-1.6.0/2.6.17.5gateway-i386-cb/output.c: In Funktion »cipe_xmit«:
> /cipe-1.6.0/2.6.17.5gateway-i386-cb/output.c:176: Fehler: »struct inet_sock«
> hat kein Element namens »inet«
> /cipe-1.6.0/2.6.17.5gateway-i386-cb/output.c:198: Fehler: »struct inet_sock«
> hat kein Element namens »inet«
> make[3]: *** [/tmp/cipe-1.6.0/2.6.17.5gateway-i386-cb/output.o] Fehler 1
> make[2]: *** [_module_/tmp/cipe-1.6.0/2.6.17.5gateway-i386-cb] Fehler 2
> make[2]: Leaving directory `/usr/src/linux-2.6.17.5'
> make[1]: *** [all25] Fehler 2
> make[1]: Leaving directory `/tmp/cipe-1.6.0/2.6.17.5gateway-i386-cb'
> make: *** [all] Fehler 2
>
> Can anybody help me finding this missing element called "inet" ;-) ?
I can give you some clues. The problem lies in the definition of the
IOPT macro, which is defined in cipe/cipe.h. The stock cipe.h defines
IOPT as
#define IOPT(c) (&(c)->sock->inet)
That's OK for older 2.6 kernels, but newer kernels require
#define IOPT(c) ((c)->sock)
The 2.6.14 patch (assuming you're talking about my 2.6.14 patch)
changes the definition and wraps the change in a test of the kernel
release:
#if LINUX_VERSION_CODE < KERNEL_VERSION(2,6,12)
#define IOPT(c) (&(c)->sock->inet)
#else
#define IOPT(c) ((c)->sock)
#endif
(I'm not sure 2.6.12 is the correct branching point for this change,
but that won't affect kernels later than 2.6.12.)
It appears that
- You applied some patch other than mine, or
- Your build is picking up another cipe.h, or
- Your build is finding a kernel build directory for an older
release
For CIPE to live on, it needs someone or some group to step forward
and take on maintenance. For awhile I thought I might be in a
position to do that, but my life took a different turn. I believe
there is now a project to maintain CIPE, based on SourceForge I think.
--
Dick St.Peters, [email protected]
--
Message sent by the [email protected] mailing list.
Unsubscribe: mail [email protected], "unsubscribe cipe-l" in body
Other commands available with "help" in body to the same address.
CIPE info and list archive: <URL:http://sites.inka.de/~bigred/devel/cipe.html>