From owner-freebsd-alpha Mon Dec 30 9:40: 4 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 032E437B401 for ; Mon, 30 Dec 2002 09:40:03 -0800 (PST) Received: from ebb.errno.com (ebb.errno.com [66.127.85.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id 47F6243EC5 for ; Mon, 30 Dec 2002 09:40:02 -0800 (PST) (envelope-from sam@errno.com) Received: from melange (melange.errno.com [66.127.85.82]) (authenticated bits=0) by ebb.errno.com (8.12.5/8.12.1) with ESMTP id gBUHdrnN044070 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Mon, 30 Dec 2002 09:39:58 -0800 (PST)?g (envelope-from sam@errno.com)œ X-Authentication-Warning: ebb.errno.com: Host melange.errno.com [66.127.85.82] claimed to be melange Message-ID: <0da501c2b02a$7946bff0$52557f42@errno.com> From: "Sam Leffler" To: "Andrew Gallatin" Cc: "Rob B" , , References: <000001c2af4d$0f7da3f0$011872cf@gamer><5.1.1.6.2.20021230111030.01d0b880@127.0.0.1><15888.23645.644351.257656@grasshopper.cs.duke.edu><0d8301c2b024$13366b80$52557f42@errno.com> <15888.31820.353185.440191@grasshopper.cs.duke.edu> Subject: Re: 4.7-STABLE kernel build failure with current CVS, any ideas? Date: Mon, 30 Dec 2002 09:39:53 -0800 Organization: Errno Consulting MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > Sam Leffler writes: > > > Yes, the crypto author appears to have forgotten to backport the > > > required alpha bits. > > > > > > Can you try the following untested patch? I'm quite busy right now > > > (just got back from vacation) and don't have time to take an alpha > > > to -stable to fix this. > > > > > > > Yes, I did not include alpha-specific changes because the crypto code is > > only really useful when you have h/w drivers and there are none for alpha > > under -stable. > > > > Was this when the system was built w/o crypto support enabled? The only > > users of these definitions should be the crypto code. > > > > Sam > > The crypto modules are currently enabled to be built by default. > If there is no point to enabling them on alpha, perhaps a more > appropriate patch would be the following, which moves the crypto > modules to x86 only. > Hmm, yes, I didn't build modules on alpha (sorry). It would probably be best to fix the spl stuff and let the crypto modules be built since the crypto h/w drivers should be usable as soon as the bus dma support is working. I'm still waffling about whether or not to MFC the fast ipsec code in which case the crypto code will be needed. So I guess my preference would for your first patch. Unfortunately I don't know of an alpha running -stable to test with. If someone can verify the spl patch works then I'll commit it for you. Sam To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message