Date: Mon, 30 Dec 2002 12:43:43 -0500 From: "Howard Leadmon" <hdl@abs.net> To: "'Sam Leffler'" <sam@errno.com>, "'Andrew Gallatin'" <gallatin@cs.duke.edu>, "'Rob B'" <rbyrnes@ozemail.com.au> Cc: <freebsd-alpha@FreeBSD.ORG> Subject: RE: 4.7-STABLE kernel build failure with current CVS, any ideas? Message-ID: <001101c2b02b$0202b790$011872cf@gamer> In-Reply-To: <0d8301c2b024$13366b80$52557f42@errno.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Just FYI, all I did was run a cvsup of STABLE, and then rebuild the OS and kernel. I changed no options in the kernel config on any of my machines, but it worked for Intel but no Alpha. So I would be inclined to say the code is enabled by default, but it breaks the alpha build. --- Howard Leadmon - hdl@abs.net Charm Net, LLC - Phone: 410-685-3900 - FAX: 410-361-8162 > -----Original Message----- > From: Sam Leffler [mailto:sam@errno.com] > Sent: Monday, December 30, 2002 11:54 AM > To: Andrew Gallatin; Rob B > Cc: hdl@abs.net; freebsd-alpha@FreeBSD.ORG > Subject: Re: 4.7-STABLE kernel build failure with current CVS, any ideas? > > > 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?001101c2b02b$0202b790$011872cf>