From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 839 invoked by alias); 20 Aug 2002 14:03:32 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 825 invoked from network); 20 Aug 2002 14:03:29 -0000 Received: from unknown (HELO crack.them.org) (65.125.64.184) by sources.redhat.com with SMTP; 20 Aug 2002 14:03:28 -0000 Received: from nevyn.them.org ([66.93.61.169] ident=mail) by crack.them.org with asmtp (Exim 3.12 #1 (Debian)) id 17h9bU-0005Fl-00; Tue, 20 Aug 2002 09:03:28 -0500 Received: from drow by nevyn.them.org with local (Exim 3.35 #1 (Debian)) id 17h9c3-0007KW-00; Tue, 20 Aug 2002 10:04:03 -0400 Date: Tue, 20 Aug 2002 07:03:00 -0000 From: Daniel Jacobowitz To: Andrew Cagney Cc: Peter Barada , Peter.Barada@Motorola.com, gdb@sources.redhat.com Subject: Re: Can't build m68k-linux gdb-5.2.1 Message-ID: <20020820140403.GA28061@nevyn.them.org> Mail-Followup-To: Andrew Cagney , Peter Barada , Peter.Barada@Motorola.com, gdb@sources.redhat.com References: <200208192254.g7JMsMe09414@hyper.wm.sps.mot.com> <3D619C86.3080500@ges.redhat.com> <200208201333.g7KDXaq14662@hyper.wm.sps.mot.com> <3D62489D.5020502@ges.redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3D62489D.5020502@ges.redhat.com> User-Agent: Mutt/1.5.1i X-SW-Source: 2002-08/txt/msg00228.txt.bz2 On Tue, Aug 20, 2002 at 09:48:13AM -0400, Andrew Cagney wrote: > >>>I'm trying to build a gdb for m68k-linux, configured as: > > > >> > > > >>>All the missing references are in gdb/m68klinux-nat.c, so I'd assume > >>>this is supposed to be built, but isn't for --target=m68k-linux. Does > >>>anyone have any idea how I can get it to be built? > > > >> > >>Looks like for the moment you'll need to use m68k-elf. > >> > >>The file m68klinux-nat.c should only contain stuff for a native build > >>(eg ptrace interface). The OS dependant, but not specific to native, is > >>typically put in a file like m68k-linux-tdep.c. cf m68knbsd-tdep.c. > >>Patches against mainline welcome (do you have an FSF assignment?). > > > > > >1) I can use m68k-elf for now. > >2) I'm still working the legal department to come up with an > > assignment to cover changes for gdb. > > > > > >>Would you be able to create abug report to track this: > >>http://sources.redhat.com/gdb/bugs/ > > > > > >Shold the bug be that m68k-linux should not build on a machine that is > >*not* m68k-linux, or that it should build for m68k-linux only if > >CC is a cross-compiler? > > A m68k-linux-gnu targeted GDB should build on any UNIX like host. > > >>>While I'm at it, how do I configure(and build) a gdbserver to run on > >>>m68k-linux that's built on an x86-linux machine? > >>> > >>>All help is appreciated. > > > >> > >>You'll need to config/compile it using a cross compiler > >>(m68k-linux-gnu-gcc say). > > > > > >Do you have a configure command line to suggest? > > I think DanielJ covered this (However, we desperatly need doco > explaining the procedure :-/). It's already there. In gdbserver/README. I have a promise to Eli sitting in my inbox to add it to gdb/INSTALL, except that I just noticed there _isn't_ a gdb/INSTALL. So I don't know how much more prominent I can make it. No one reads the READMEs... -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer