Re: The new minstall fails...

-----BEGIN PGP SIGNED MESSAGE-----


On Mon, 24 Feb 2003, Hugh Daniel wrote:

> mkdir -p $FSMODLIB/kernel/net/ipsec ; \
> cp linux/net/ipsec/ipsec.o $FSMODLIB/kernel/net/ipsec )
> + mkdir -p /lib/modules/2.4.20/kernel/net/ipsec
> + cp linux/net/ipsec/ipsec.o /lib/modules/2.4.20/kernel/net/ipsec
> cp: cannot stat `linux/net/ipsec/ipsec.o': No such file or directory
> make: *** [minstall] Error 1
> 
>   There _is_ such a directory as:
> 
> /usr/src/freeswan/linux/net/ipsec/
> 
>   but nothing has happened in it, while over in:
> 
> /usr/src/linux/net/ipsec/ipsec.o
> 
>   we obviously have the right file.  To get here I issued two
> commands, "make oldgo" and "make minstall".  So there is confusion as
> to where to get the binary from.

Let me provide the insight I can. This is based off of doc/install.html.

First off, there are two "types" of kernel/module building targets: *mod, *go. 
"make oldmod" is to be used when we intend to compile KLIPS as module; "make 
oldgo" when we intend to compile a kernel with our IPSec code statically 
linked. 

The appropriate way to install FreeS/WAN after oldgo:  kinstall. After oldmod,
minstall.

... but what surprises me is this: when I look at the .config after it is
modified by oldgo, it's not CONFIG_IPSEC=y -- it's CONFIG_IPSEC=m. I can
understand your confusion.

An added complication: In the 2.00 series, when we configure KLIPS as a module
via "oldmod", it gets built in our source tree, in linux/net/ipsec, but we
patch FreeS/WAN code into the kernel anyhow.  When we build via oldgo, my
understanding is that we mean to build it into the kernel - the documentation
certainly indicates so - and the appropriate install target is "kinstall".

It's important to keep the compile and install targets separate, as people may 
be crosscompiling, or compiling for use on multiple machines with similar 
code/architecture.

As oldgo is not defaulting to static IPSEC compilation, is it broken, or is 
there some other confusion?

- -- 
Sam Sgro
[email protected]

-----BEGIN PGP SIGNATURE-----
Version: 2.6.3ia
Charset: noconv
Comment: For the matching public key, finger the Reply-To: address.

iQCVAwUBPlnkC0OSC4btEQUtAQGcqAQA0olhOt99jK/mKbOJ9fNH24tMkBulvxFg
ef/tfWaMYAAKl6K8Eo4+JcXfNRLuh/Rok5Xx9Up5rz1Zv7ljFiQ8+Zta1/Oy4NiY
hSdTPwQiU61qQJmzc7lc4BTITJd5cGjxEZJsGW5TeE1BAlRvZYCLu1zF9w7FDfqO
3WxzYZeMiWM=
=cG6K
-----END PGP SIGNATURE-----