public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Fred <fred@arkansaswebs.com>
To: Subba Rao <subba9@home.com>, Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Problems installing FreeS/WAN 1.9.1 on kernel 2.4.9
Date: Mon, 3 Sep 2001 14:03:59 -0500	[thread overview]
Message-ID: <01090314035904.21988@bits.linuxball> (raw)
In-Reply-To: <20010903133025.B31122@home.com>
In-Reply-To: <20010903133025.B31122@home.com>

looks similiar to problems I had a while back because I didn't 'make 
mrproper'.
try removing FreeS/WAN 1.9.1 and kernel sources, then untar the kernel, do: 

make mrproper 
make xconfig 
make dep clean <bzImage | install> modules modules_install

if this works, then do

make mrproper
add the FreeS/WAN 1.9.1 code
make xconfig 
make dep clean <bzImage | install> modules modules_install

hope this helps

Fred

 _________________________________________________ 
On Monday 03 September 2001 12:30 pm, Subba Rao wrote:
> Could anyone here get FreeS/WAN 1.9.1 to compile on kernel 2.4.9?
> My kernel compilation is ending with tons of warnings and errors. Before
> installing the FreeS/WAN code, I have customized kernel 2.4.9 and installed
> it without any problems.
>
> Here is what I did so far:
>
> 	1. tar xzvf freeswan-1.91.tar.gz (in /usr/src)
> 	2. cd freeswan-1.91
> 	3. make insert
> 	4. make programs
> 	5. make install
> 	6. cd ../linux
> 	7. make depend; make bzImage
>
> My distribution is Slackware 8 runnning kernel 2.4.9
>
> I have listed the errors, once build goes into ipsec directory.
>
> If anyone got the ipsec compiled into kernel 2.4.9, please let me know how
> you did it.
>
> TIA.

      reply	other threads:[~2001-09-03 19:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-03 17:30 Problems installing FreeS/WAN 1.9.1 on kernel 2.4.9 Subba Rao
2001-09-03 19:03 ` Fred [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=01090314035904.21988@bits.linuxball \
    --to=fred@arkansaswebs.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=subba9@home.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox