It seems Mark Murray wrote:
> > > Do you have a full crypto distribution (kernel also)?
> > 
> > Nope, just figured that out myself :)
> > Aren't we supposed to be able to build without crypto ??
> 
> I'm not sure about that rule anymore; AFAIK, it is not possible.

Hmm, we also have another rule, and that is to test before commit,
the following patch is needed to make a current kernel with
your resent commits compile :)


Index: dev/randomdev//randomdev.c
===================================================================
RCS file: /home/ncvs/src/sys/dev/randomdev/randomdev.c,v
retrieving revision 1.1
diff -u -r1.1 randomdev.c
--- dev/randomdev//randomdev.c  2000/06/25 08:38:58     1.1
+++ dev/randomdev//randomdev.c  2000/06/25 18:39:10
@@ -44,7 +44,7 @@
 #include <sys/sysctl.h>
 #include <crypto/blowfish/blowfish.h>
 
-#include "yarrow.h"
+#include "dev/randomdev/yarrow.h"
 
 static d_read_t randomread;
 static d_write_t randomwrite;
Index: dev/randomdev//yarrow.c
===================================================================
RCS file: /home/ncvs/src/sys/dev/randomdev/yarrow.c,v
retrieving revision 1.1
diff -u -r1.1 yarrow.c
--- dev/randomdev//yarrow.c     2000/06/25 08:38:58     1.1
+++ dev/randomdev//yarrow.c     2000/06/25 18:38:58
@@ -39,7 +39,7 @@
 #include <sys/types.h>
 #include <crypto/blowfish/blowfish.h>
 
-#include "yarrow.h"
+#include "dev/randomdev/yarrow.h"
 
 void generator_gate(void);
 void reseed(void);
Index: i386/i386//mem.c
===================================================================
RCS file: /home/ncvs/src/sys/i386/i386/mem.c,v
retrieving revision 1.86
diff -u -r1.86 mem.c
--- i386/i386//mem.c    2000/06/25 17:26:47     1.86
+++ i386/i386//mem.c    2000/06/25 18:42:13
@@ -217,10 +217,10 @@
        /* minor device 1 is kernel memory */
        case 1:
                return i386_btop(vtophys(offset));
-       }
 
        default:
                return -1;
+       }
 }
 
 /*

-Søren


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to