[Openswan Users] building
ted leslie
tleslie at tcn.net
Fri Mar 24 02:52:02 CET 2006
i am so close i can taste it!!!
i have applied Klips patch to a 2.6.14 kernel,
compiled userland
all is well except i get warnings below in the kernel compile step,
since they were warnings, i ignored at first,
*** Warning: "ipsec_aes_init" [net/ipsec/ipsec.ko] undefined!
*** Warning: "des_check_key" [net/ipsec/ipsec.ko] undefined!
*** Warning: "ipsec_3des_init" [net/ipsec/ipsec.ko] undefined!
*** Warning: "des_ede3_cbc_encrypt" [net/ipsec/ipsec.ko] undefined!
but when i run /etc/init.d/ipsec start
and it in turn loads ipsec.ko
it complains about the missing object refs above again
i can see in the .config of the kernel that these options are all "Y" for include in kernel.
when i go into
net/ipsec/
i can see them being included in the
built-in.o
being made in that directory,
but in the
net/
directory, the built-in.o (based on Makefile? and .built-in.o.cmd)
doesnt include taking the build-in.o from the ipsec directory, it takes many other
built-in.o 's from other sub directories in /net/ but nothing from ipsec.
ofcourse i tried plugging the files manually (As a quick cheat), but the make (kernel)
process just overwrites it.
So basically i am down to just a configuration of a paramter issue,
something somewhere needs to be set to include the /net/ipsec/built-in.o in the /net/built-in.o
which inturn makes it way into the master built-in's of the vmlinuz being built.
any ideas?
it's got to be something really simple,
but i have gone over the .config file of the kernel and don't see anything obvious.
if someone knows about what makes the .built-in.o.cmd files, and where it gets it data ..
i am home free!!
-tl
On Fri, 24 Mar 2006 08:02:02 +0100 (CET)
Paul Wouters <paul at xelerance.com> wrote:
> On Fri, 24 Mar 2006, ted leslie wrote:
>
> > i think its ok to ignore hw_random.ko insmod "fatals"
> > because a software random is its back up? right?
> >
> > but i have never seen a padlock.ko error,
> > can i ignore this?
>
> Yes, unless you have a VIA C3 or newer cpu with padlock.
>
> Paul
>
More information about the Users
mailing list