[PATCH] Move 'enum bfd_endian' to a non-generated header

Tristan Gingold gingold@adacore.com
Mon Feb 15 10:50:00 GMT 2016

Previous message (by thread): [PATCH] Move 'enum bfd_endian' to a non-generated header
Next message (by thread): [PATCH] Move 'enum bfd_endian' to a non-generated header
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

> On 12 Feb 2016, at 19:39, Pedro Alves <palves@redhat.com> wrote:
> 
> Because:
> 
> - GDB uses enum bfd_endian extensively.
> - gdbserver does not build/link-with bfd.
> - We'd like to share more code between gdb and gdbserver.
> 
> It'd make our lives easier if we could just use bfd_endian in
> gdbserver as well.
> 
> The problem is that bfd_endian is defined in a header that only exists
> if bfd is built/configured.
> 
> Thus this moves bfd_endian to a separate header, so gdbserver can
> include it.
> 
> Build tested with --enable-targets=all, from scratch.

Doesn’t this patch remove enum bfd_endian from the documentation ?

Previous message (by thread): [PATCH] Move 'enum bfd_endian' to a non-generated header
Next message (by thread): [PATCH] Move 'enum bfd_endian' to a non-generated header
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

More information about the Binutils mailing list