From owner-freebsd-stable Sat Mar 18 5:27:30 2000 Delivered-To: freebsd-stable@freebsd.org Received: from polaris.shore.net (polaris.shore.net [207.244.124.105]) by hub.freebsd.org (Postfix) with ESMTP id 33C3237B5E2; Sat, 18 Mar 2000 05:27:26 -0800 (PST) (envelope-from tjlegg@shore.net) Received: from eskimos.the-eleven.com [207.244.92.51] by polaris.shore.net with esmtp (Exim) id 12WJGG-00001x-00; Sat, 18 Mar 2000 08:27:24 -0500 Mime-Version: 1.0 X-Sender: tjlegg@shell2.shore.net Message-Id: In-Reply-To: References: Date: Sat, 18 Mar 2000 08:27:23 -0500 To: Kris Kennaway From: Tom Legg Subject: Re: 3 to 4 Upgrade, missing crypto bugs, and random thoughts Cc: freebsd-stable@freebsd.org Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 9:52 PM -0800 3/17/2000, Kris Kennaway wrote: >On Fri, 17 Mar 2000, Tom Legg wrote: > >> I've reproduced the missing crypto bug when compiling a kernel..... >> I think I've isolated it. If you try to build a custom kernel with >> IPSEC options the make will bomb. This will happen even after the >> current UPDATING instructions are complete. > >You do have the src-sys-crypto sources, right? /usr/src/sys/crypto/? > >> But... if you do a buildworld and installworld with existing source >> after getting 4.0 running, then you can implement IPSEC in the kernel. > >Hmm..I think you'd have to provide a build log showing where it failed >without this step - I don't know why it would be the case. It fails looking for /usr/src/crypto/sha.c. Did the crypto sources move in the directory tree between RELENG_3 and RELENG_4? -- ----- Tom Legg tjlegg@shore.net http://www.shore.net/~tjlegg/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message