Likely obsolete pieces of GDB

[Joel Brobecker]

> I am happy to change the mechanism; I don't like // OBSOLETE either. 
> We can't even use the current mechanism for some of these files:
> anything not directly corresponding to a target.
> 
> To be honest, I'd been thinking about waiting for everyone to agree on
> which things to remove, sending a message to gdb-announce, and then
> just doing it.  If there were any justifiable complaints at the time of
> the next release we could recover targets from CVS history.  I'm sure
> not everyone is comfortable with that sudden of an approach, so
> using configure for targets for one release is fine with me too.

Either approach is fine with me. I agree the // OBSOLETE approach
is a bit of a pain...

-- 
Joel