Re: [patch] Zap a29k ultra native stuff

[Andrew Cagney <ac131313@cygnus.com>]

>> The a29k is very much on notice (obsolete announcement sent out).

> Does this mean you're looking at dropping the utils/amd-udi directory
> as well?  This is some code to talk to a ROM monitor that was used
> on 29k boards long ago, it's a code drop of AMD's own support code
> slightly munged to work in our build setup.  Mostly, though, it's
> 1.4MB of wasted disk space on every gdb checkout these days.

Yep (delete a29k?)!  The below went out problably 1s after 5.1 was 
released.  Hmm, forgot to cc gdb@, I'll forward the original post.

I'm playing with a draft patch in my local sandpit.  The number of 
remote-*.c targets that are deleted is suprising.  This must have been a 
popular target back in its time.

enjoy,
Andrew


> [Reply-to: GDB Discussion < gdb AT sources DOT redhat DOT com > ]
> 
> Hello,
> 
> As part of GDB 5.2, the a29k target
> 
>     a29k-* (a29k-aout, a29k-coff, ...)
> 
> has been identified as a candidate for obsolescence.  This target:
> 
>     o    depends on the the macro HOST_BYTE_ORDER
>         which is being deleted from GDB.
> 
>     o    does not build multi-arch.
> 
>     o    has no active maintainer
> 
> ``Configurations that have been declared obsolete in this release have
> been commented out.  Unless there is activity to revive these
> configurations, the next release of GDB will have their sources
> permanently REMOVED.''
> 
> If you have any comments or questions on this, please send them to the GDB Discussion group.
> 
>         Andrew
> 
> Andrew Cagney
> Acting Head GDB Maintainer
>