Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 30 Dec 2002 09:39:53 -0800
From:      "Sam Leffler" <>
To:        "Andrew Gallatin" <>
Cc:        "Rob B" <>, <>, <freebsd-alpha@FreeBSD.ORG>
Subject:   Re: 4.7-STABLE kernel build failure with current CVS, any  ideas?
Message-ID:  <0da501c2b02a$7946bff0$>
References:  <000001c2af4d$0f7da3f0$011872cf@gamer><><><0d8301c2b024$13366b80$> <>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
> 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
>  > only really useful when you have h/w drivers and there are none for
>  > under -stable.
>  >
>  > Was this when the system was built w/o crypto support enabled?  The
>  > 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.


To Unsubscribe: send mail to
with "unsubscribe freebsd-alpha" in the body of the message

Want to link to this message? Use this URL: <$7946bff0$52557f42>