This is the mail archive of the
binutils@sourceware.org
mailing list for the binutils project.
Re: Always include elf.lo?
- From: Daniel Jacobowitz <drow at false dot org>
- To: Nick Clifton <nickc at redhat dot com>
- Cc: binutils at sourceware dot org, Pedro Alves <pedro_alves at portugalmail dot pt>
- Date: Mon, 21 May 2007 13:03:16 -0400
- Subject: Re: Always include elf.lo?
- References: <20070521125938.GC32557@caradoc.them.org> <4651CE97.3090405@redhat.com>
On Mon, May 21, 2007 at 05:53:43PM +0100, Nick Clifton wrote:
> Hi Daniel,
>
> > GDB currently includes elfread.o on all targets.
>
> Why does GDB do this ? Wouldn't it make more sense for GDB only to include it
> for ELF based targets ?
Because then GDB would have to know which targets "were ELF based".
You can feed GDB any object file you want, from any toolchain - not
necessarily a GNU one. I think it would even work, in most cases,
without special BFD support for ELF on that platform; we'll still get
addresses, symbol names, and so forth. But you've got to have at
least the ELF reader.
Also, probably, because this way we didn't need to keep track of which
targets were which.
I'll try an autoconf solution instead.
--
Daniel Jacobowitz
CodeSourcery