QNX binutils targets

[Graeme Peterson]

Hi, all.

I am in the process of adding the ELFOSABI_QNX.  I have some questions and
concerns.

- How will changing the OSABI and bfd names affect our existing tools
  (gcc, gdb, etc...) that use the generic ones?  I had tried to simply
  extend the existing bfd's, not realizing the concequences in the 
  namimg when targetting all.

- My current approach is to add the define in include/elf/common.h:
  #define ELFOSABI_QNX     13     /* QNX Neutrino */

  Then I have added a function in elf32-qnx.c, with a bfd_backend
  define in elf32-qnx.h:

  #undef  elf_backend_post_process_headers
  #define elf_backend_post_process_headers    elf_qnx_post_process_headers

  This is a copy of the similar function in elf32-i386.c, the FREEBSD's
  elf_i386_post_process_headers.

- Then I want to change the config.bfd, so that our bfd vectors will default 
  to a non-qnx specific one, but incllude them all, ie:

    arm-*-nto* | nto*arm*)
    targ_defvec=bfd_elf32_littlearm_vec
    targ_selvecs="bfd_elf32_bigarm_vec bfd_elf32_littlearmqnx_vec bfd_elf32_bigarmqnx_vec"
    ;;

  i[3456]86-*-nto-qnx*)
    targ_defvec=bfd_elf32_i386_vec
    targ_selvecs="i386coff_vec bfd_elf32_i386qnx_vec"
    ;;

Comments?  Have I got it right, or am I missing something?

Thanks.
GP

> 
> On Fri, Oct 25, 2002 at 10:54:52AM +0930, Alan Modra wrote:
> > On Thu, Oct 24, 2002 at 11:32:00PM +0200, Segher Boessenkool wrote:
> > [zapping targets from _bfd_target_vector]
> > > which makes things work as I like.  It seems this is done for some other
> > > ambiguously detected formats as well.
> > 
> > Yes, that works.  The trouble is that your selection of targets to
> > "make things work as I like" may not suit everybody.
> > 
> 
> QNX should add ELFOSABI_QNX and use it.
> 
> 
> H.J.
>