Date: Sat, 18 Mar 2000 08:27:23 -0500 From: Tom Legg <tjlegg@shore.net> To: Kris Kennaway <kris@freebsd.org> Cc: freebsd-stable@freebsd.org Subject: Re: 3 to 4 Upgrade, missing crypto bugs, and random thoughts Message-ID: <p04310101b4f933c6eaa4@[207.244.92.51]> In-Reply-To: <Pine.BSF.4.21.0003172149220.46620-100000@freefall.freebsd.org> References: <Pine.BSF.4.21.0003172149220.46620-100000@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?p04310101b4f933c6eaa4>