From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-6950-listarch-gdb=sourceware.cygnus.com@sources.redhat.com>
Received: (qmail 4055 invoked by alias); 28 Nov 2001 07:40:22 -0000
Mailing-List: contact gdb-help@sourceware.cygnus.com; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/gdb/>
List-Post: <mailto:gdb@sources.redhat.com>
List-Help: <mailto:gdb-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: gdb-owner@sources.redhat.com
Received: (qmail 3903 invoked from network); 28 Nov 2001 07:40:19 -0000
Received: from unknown (HELO localhost.cygnus.com) (24.114.42.213)
  by hostedprojects.ges.redhat.com with SMTP; 28 Nov 2001 07:40:19 -0000
Received: from cygnus.com (localhost [127.0.0.1])
	by localhost.cygnus.com (Postfix) with ESMTP id 3B0E93DC3
	for <gdb@sources.redhat.com>; Wed, 28 Nov 2001 02:40:19 -0500 (EST)
Message-ID: <3C0494E3.90601@cygnus.com>
Date: Mon, 19 Nov 2001 10:57:00 -0000
From: Andrew Cagney <ac131313@cygnus.com>
User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:0.9.3) Gecko/20011020
X-Accept-Language: en-us
MIME-Version: 1.0
To: gdb@sources.redhat.com
Subject: Re: multi-arch and breaking ``maintenance only'' targets (eg a29k)
References: <3BE0BD2B.6050609@cygnus.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-SW-Source: 2001-11/txt/msg00197.txt.bz2
Message-ID: <20011119105700.EwGSf_m2nLEu50sk9jBHI63gtc9yXcpQoHyr-Xfzp3Y@z>

No one commented.  I'm going to send out an announcement indicating that 
I intend removing a29k.

		Andrew


> Hello,
> 
> The a29k target currently builds but isn't being maintained.  Post 5.1 it will either need to be multi-arched or will find its self dieing a slow death.  That death, however, may come sooner than some might think.
> 
> I'm about to post a patch that eliminates the macro HOST_BYTE_ORDER from GDB.  Unfortunatly the a29k target has code like:
> 
>     #ifdef TARGET_BYTE_ORDER == HOST_BYTE_ORDER
>     #define MD(X)
>         .....
>     #else
>     #define MD(X)
>         .....
>     #endif
> 
> and that will no longer work.  Consequently, I intend adding a #error ... to the a29k so that it is clearly broken.
> 
> With this comes a definite shift in policy.  Up until now developers were to expected to keep non-multi-arch targets compiling.  If the above goes through, it will mean that non-multi-arch targets that are not being maintained can be broken on a case by case basis.
> 
> enjoy,
> Andrew