On Wed, Dec 13, 2000 at 10:08:50AM -0800, Chris G. Demetriou wrote:
> lukem@wasabisystems.com (Luke Mewburn) writes:
> > > Hmm. Personally, I for one would rather see this feature go away
> > > and we should use existing mechanisms. 
> 
> as would I.  it's broken.
> 
> There's the issue of _ and .
> 
> There's also the issue of expected behaviour of you say:
> 
> 	include FOOBAR
> 
> in FOOBAR.DEBUG.
> 
> All of a sudden, the code paths which used to apply to FOOBAR no
> longer apply to the kernel you just built -- which from the
> configuration should be logically the same.
> 
> Unless i'm misremembering, _old_ config used to -D the kernel name,
> and that wasn't done in new config.  Instead, it could be done with
> options.

how is it broken?

the definition of _KERNEL_FOOBAR shouldn't break anything, and if the
basename of the target directory (which is usually the config file
name) contains wacky characters they get converted to `_')

if I defined `FOOBAR' instead of `_KERNEL_FOO' you might have a point.