>All of a sudden, after updating with CVS today, I'm seeing new obj
>directories being created like this:
>
>obj ===> games/fortune/strfile
>/usr/src/games/fortune/strfile/obj.i386.NetBSD-1.5Y-i386 -> /usr/local/obj/games/fortune/strfile.i386.NetBSD-1.5Y-i386
>
>In /etc/mk.conf, I've got:
>
>MKOBJDIRS=yes
>OBJMACHINE=yes
>BSDSRCDIR=/usr/src
>BSDOBJDIR=/usr/local/obj
>
>...which until now would have caused the above to read:
>
>obj ===> games/fortune/strfile
>/usr/src/games/fortune/strfile/obj.i386 -> /usr/local/obj/games/fortune/strfile.i386
>
>I must say I liked that better...  :-)

hmm, yes, perhaps, but!  the strfile program is now being targeted as
a cross compilation tool, not just something that gets built.  this
means that after you start cross compiling for other platforms (if i
understand all this so far), you'll end up with a bunch of

/usr/src/games/fortune/strfile/obj.alpha.NetBSD-1.5Y-i386 -> /usr/local/obj/games/fortune/strfile.alpha.NetBSD-1.5Y-i386
/usr/src/games/fortune/strfile/obj.sparc.NetBSD-1.5Y-i386 -> /usr/local/obj/games/fortune/strfile.sparc.NetBSD-1.5Y-i386
/usr/src/games/fortune/strfile/obj.vax.NetBSD-1.5Y-i386 -> /usr/local/obj/games/fortune/strfile.vax.NetBSD-1.5Y-i386

links that identify themselves as being built on i386, but for a alpha
(or sparc, or vax).

incidentally, this makes things start to look like what i had already
as a result of my

	BSDOBJDIR!=echo /usr/obj/${MACHINE}-on-`uname -m`

setting.  that segregates sparc natively built foo from cross built
stuff i did on my 386.

-- 
|-----< "CODE WARRIOR" >-----|
codewarrior@daemon.org             * "ah!  i see you have the internet
twofsonet@graffiti.com (Andrew Brown)                that goes *ping*!"
andrew@crossbar.com       * "information is power -- share the wealth."