> thought it'd be nice to be able to use one libkern for all m68k
> machines, but with the addition of the disklabel stuff to libkern that
> is no longer possible.
> 
> Am I the only one who thinks this is dumb?

Not particularly, although I don't see much advantage to sharing
the libkern objects/library...

Well, cpu_disklabel isn't used as far as I can tell.  We're just
getting it from including sys/disklabel.h.  If a separation can
be made between disklabel and cpu_disklabel, we wouldn't have this
problem, yet.  Should we have a machine/disklabel.h?  Should
sys/disklabel.h include it for backward compat., if so?  If not,
what's the gain, unless we do:
#ifndef LIBKERN
#include <machine/disklabel.h>
#endif
in sys/disklabel.h?

-allen

Yea!  Another bounce from tech-ports!  Should I take that address
off this thread, or be added to the approved posters list?  ;-)

-- 
Allen Briggs         Find the cost of freedom / Buried in the ground
- end                Mother Earth will swallow you / Lay your body down
      killing -    
allen.briggs@vt.edu          ***** MacBSD == NetBSD/Mac *****

------------------------------------------------------------------------------