| 1 |
Me again... This time I'm trying to get "freeswan" to build. When I try to |
| 2 |
emerge it, I get: |
| 3 |
|
| 4 |
>>> md5 ;-) freeswan-1.98b.tar.gz |
| 5 |
>>> md5 ;-) x509patch-0.9.15-freeswan-1.98b.tar.gz |
| 6 |
You need to have the crypto-enabled version of Gentoo Sources |
| 7 |
with a symlink to it in /usr/src/linux in order to have IPSec |
| 8 |
kernel compatibility. Please emerge sys-kernel/crypto-sources, |
| 9 |
compile an IPSec-enabled kernel and attempt this ebuild again. |
| 10 |
|
| 11 |
Fair enough. So I try to "emerge sys-kernel/crypto-source" and I get a note |
| 12 |
about all builds being masked (no ppc keywords). So, I do "emerge |
| 13 |
crypto-sources-2.4.19-r7.ebuild" to force it to go. |
| 14 |
|
| 15 |
It succeeds. Then I do the kernel configuration dance and proceed to do my |
| 16 |
compilation. Half way though it dies: |
| 17 |
|
| 18 |
gcc -D__KERNEL__ -I/usr/src/linux-2.4.19-crypto-r6/include -Wall |
| 19 |
-Wstrict-protot |
| 20 |
ypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer |
| 21 |
-D |
| 22 |
__powerpc__ -fsigned-char -msoft-float -pipe -ffixed-r2 -Wno-uninitialized |
| 23 |
-mmul |
| 24 |
tiple -mstring -nostdinc -I |
| 25 |
/usr/lib/gcc-lib/powerpc-unknown-linux-gnu/3.2/inc |
| 26 |
lude -DKBUILD_BASENAME=nfsctl -c -o nfsctl.o nfsctl.c |
| 27 |
nfsctl.c:314: parse error before "nfsd_init" |
| 28 |
nfsctl.c:315: warning: return type defaults to `int' |
| 29 |
nfsctl.c:332: parse error before "nfsd_exit" |
| 30 |
nfsctl.c:333: warning: return type defaults to `int' |
| 31 |
nfsctl.c:345: warning: type defaults to `int' in declaration of `module_init' |
| 32 |
nfsctl.c:345: warning: parameter names (without types) in function declaration |
| 33 |
nfsctl.c:345: warning: data definition has no type or storage class |
| 34 |
nfsctl.c:346: warning: type defaults to `int' in declaration of `module_exit' |
| 35 |
nfsctl.c:346: warning: parameter names (without types) in function declaration |
| 36 |
nfsctl.c:346: warning: data definition has no type or storage class |
| 37 |
make[3]: *** [nfsctl.o] Error 1 |
| 38 |
make[3]: Leaving directory `/usr/src/linux-2.4.19-crypto-r6/fs/nfsd' |
| 39 |
make[2]: *** [first_rule] Error 2 |
| 40 |
make[2]: Leaving directory `/usr/src/linux-2.4.19-crypto-r6/fs/nfsd' |
| 41 |
make[1]: *** [_subdir_nfsd] Error 2 |
| 42 |
make[1]: Leaving directory `/usr/src/linux-2.4.19-crypto-r6/fs' |
| 43 |
make: *** [_dir_fs] Error 2 |
| 44 |
|
| 45 |
The lines in question are the following: |
| 46 |
|
| 47 |
314: static int __init nfsd_init(void) |
| 48 |
332: static void __exit nfsd_exit(void) |
| 49 |
|
| 50 |
Anyhow, this smells like a kernel bug rather than a gentoo bug, but I'm |
| 51 |
wondering whether I am causing the problem by incorrectly emerging |
| 52 |
"sys-kernel/crypto-source" to begin with. I notice there are |
| 53 |
"sys-kernel/ppc-sources" ebuilds, which indicates to me that the PPC kernel |
| 54 |
is different from the plain vanilla kernel. Perhaps the "crypto-sources" are |
| 55 |
only for the x86? Would we need a "sys-kernel/crypto-ppc-sources" to support |
| 56 |
things like freeswan? |
| 57 |
|
| 58 |
Right now I've disabled "nfs server" in the kernel and am trying again, but I |
| 59 |
would like to know if I'm wasting my time :) |
| 60 |
|
| 61 |
Thanks, |
| 62 |
|
| 63 |
Marcio Luis Teixeira |
Archives