Yes, I've compiled -current after fixing that little conflict. I've been
running my "hacked" kernel for a few days now and I don't think I screwed
up anything. I guess I should have send-pr'd it a while ago but it didn't
happen.

Here is a diff.

*** machdep.c	Tue Jun  9 07:14:38 1998
--- machdep.c.fixed	Sat Jun 20 23:10:55 1998
***************
*** 339,348 ****
  		 * Initialize kernel debugger, if compiled in.
  		 */
  		{
- 			extern int end;
- 			extern int *esym;
  
! 			ddb_init(*(int *)&end, ((int *)&end) + 1, esym);
  		}
  #endif
  
--- 339,356 ----
  		 * Initialize kernel debugger, if compiled in.
  		 */
  		{
  
! /* This was causing compile errors. - 06/16/98
! *			extern int end;
! *			extern int *esym;
! *
! *			ddb_init(*(int *)&end, ((int *)&end) + 1, esym);
! */
! 
! 			extern char end[];
! 			extern u_long esym;
! 
! 			ddb_init(*(int *)&end, ((int *)&end) + 1, ((int *)esym));
  		}
  #endif
  
--

On another note, someone needs to add the makefiles in /sys/arch and below
to ksrc-common, I dislike having to sup all the arch directories just for
a few stupid makefiles.

On Sat, 20 Jun 1998, Tom Rini wrote:

[snip]
> The files exist, of course.  Also, has anyone been able to compile
> -current recently? There's some warnings in mac68k/machdep.c (non-matching
> externs, end and esym, conflict if you have DDB config'ed)  Sent in a
> send-pr a few days back.
> 
> ---
> Tom Rini (TR1265)
> http://dobbstown.yeti.edu/
>