From owner-freebsd-alpha Mon Dec 30 9: 3:19 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 282FD37B401 for ; Mon, 30 Dec 2002 09:03:18 -0800 (PST) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 771DF43EC5 for ; Mon, 30 Dec 2002 09:03:17 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.12.6/8.12.6) with ESMTP id gBUH3Dro009321 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 30 Dec 2002 12:03:13 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id gBUH38M43472; Mon, 30 Dec 2002 12:03:08 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15888.31820.353185.440191@grasshopper.cs.duke.edu> Date: Mon, 30 Dec 2002 12:03:08 -0500 (EST) To: "Sam Leffler" Cc: "Rob B" , , Subject: Re: 4.7-STABLE kernel build failure with current CVS, any ideas? In-Reply-To: <0d8301c2b024$13366b80$52557f42@errno.com> 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> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid 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. Drew Index: sys/modules/Makefile =================================================================== RCS file: /home/ncvs/src/sys/modules/Makefile,v retrieving revision 1.110.2.65 diff -u -r1.110.2.65 Makefile --- sys/modules/Makefile 11 Dec 2002 20:54:49 -0000 1.110.2.65 +++ sys/modules/Makefile 30 Dec 2002 17:01:21 -0000 @@ -14,8 +14,6 @@ ccd \ cd9660 \ coda \ - crypto \ - cryptodev \ cue \ dc \ dummynet \ @@ -110,6 +108,8 @@ SUBDIR+=ar \ bktr \ coff \ + crypto \ + cryptodev \ em \ fpu \ gnufpu \ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message