> And more, MACHINE (not MACHINE_ARCH) can split into evbsh3eb and evbsh3el,
 > too. Most evaluation board can select the byte order by DIP switch. We can
 > regard this difference as the same MACHINE because there is no physical
 > difference. But, there is some apropriate situation to distinct these boards
 > as differnt MACHINE (i.e. check MACHINE instead of MACHINE_ARCH).
 > 
 > To split MACHNE into evbsh3eb and evbsh3el
 > 
 > 
 > 	Plan A)		split evbsh3 "directory" into evbsh3eb and evbsh3el.
 > 			
 > 
 > 			sh3/sh3
 > 			   /conf
 > 			   /include
 > 			evbsh3eb/evbsh3eb
 > 				/conf
 > 				/include
 > 			evbsh3el/evbsh3el	null
 > 				/conf		config file for little
 > 				/include	refer evbsh3eb/include* except
 > 						endian_machdep.h
 > 
 > 	Plan B)		use "SUBDIR= ${MACHINE:C/evbsh3e[bl]/evbsh3/}"
 > 
 > 			sh3/sh3
 > 			   /conf
 > 			   /include
 > 			evbsh3/evbsh3
 > 				/conf
 > 				/include	how to solve endian_machdep.h?
 > 
 > 
 > 	Plan C)		I don't know.
 > 

snip

 > I prefer Plan B to Plan A. I want to choice Plan B if we can generate
 > endian_machdep.h by:
 > 
 > 		config(8) or make depend under compile/*/
 > 
 > 		make includes

If we should take different MACHINE name if MACHINE_ARCH is different,
we have to choice Plan A (or C?)

----------------------------------------------------------
		SAITOH Masanobu (masanobu@iij.ad.jp
				  msaitoh@netbsd.org)