From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-7541-listarch-gdb=sourceware.cygnus.com@sources.redhat.com>
Received: (qmail 21643 invoked by alias); 30 Jan 2002 03:24:11 -0000
Mailing-List: contact gdb-help@sources.redhat.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 21568 invoked from network); 30 Jan 2002 03:24:07 -0000
Received: from unknown (HELO localhost.cygnus.com) (24.114.26.18)
  by sources.redhat.com with SMTP; 30 Jan 2002 03:24:07 -0000
Received: from cygnus.com (localhost [127.0.0.1])
	by localhost.cygnus.com (Postfix) with ESMTP
	id 3D5583DD2; Tue, 29 Jan 2002 21:27:40 -0500 (EST)
Message-ID: <3C575A1C.5020700@cygnus.com>
Date: Tue, 29 Jan 2002 19:24:00 -0000
From: Andrew Cagney <ac131313@cygnus.com>
User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:0.9.7) Gecko/20020103
X-Accept-Language: en-us
MIME-Version: 1.0
To: Daniel Jacobowitz <drow@mvista.com>
Cc: Dan Kegel <dank@kegel.com>, gdb@sources.redhat.com
Subject: Re: How does one cross-compile gdbserver?
References: <3C574C25.8A2F007@kegel.com> <20020129205052.B19879@nevyn.them.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-SW-Source: 2002-01/txt/msg00344.txt.bz2

> On Tue, Jan 29, 2002 at 05:28:05PM -0800, Dan Kegel wrote:
> 
>> I'm going crazy trying to build gdb 5.1.1's gdbserver
>> in a cross-development environment.
>> 
>> Has anyone here build one recently?
>> If so, can you please post your recipe?
> 
> 
> (Just the day for this answer...)
> 
> Same way as anything else!  You need to have a compiler capable of
> building target userland binaries, and a development environment set up
> for same.  You may need to run configure in the gdbserver directory
> manually, with CC set appropriately.  Note that you want a gdb
> configured --host=<your target>, not --target=<>!
> 
> I don't give it good odds of compiling.  I've tried several times to
> clean that up and gotten stymied in various people's objections to my
> methods (sorry Andrew).  I'll be taking another stab at it this week I
> think.


:-)

I've been thinking about making it obsolete.  Not that I want to lose 
it.  Rather that it clears the slate and removes any obligation to keep 
other targets working.

The other is to just declare it really broken.

Andrew