RE: [PATCH] New BFD vector for QNX Neutrino MIPS

[Jeff Baker <jbaker at qnx dot com>]

I'm reasonably new to this whole 'binutils' thing.  The original port to
Neutrino was done a long time ago by somebody else so I'm not completely up
to speed on exactly what all of our changes are for.

I know we've added a new relocation type and that we have some reasonably
significant changes to the way that relocatable sections are output.

For completeness I've attached what could be considered an example of our
changes.  It was my first attempt at just moving the changes from our
internal 2.12.1 source to the current mainline.  The only thing that doesn't
seem to work is linking against a shared object.  There are also changes to
the assembler and linker of course, but I'm just focusing on getting bfd
done cleanly for now.

Based on the assumption that these changes wouldn't be acceptable they way
they were done originally I abandoned just moving the changes forward and
now I'm trying to figure out what the correct way to include them is.

> -----Original Message-----
> From: Thiemo Seufer [mailto:ica2_ts@csv.ica.uni-stuttgart.de]
> Sent: June 9, 2003 2:16 PM
> To: binutils@sources.redhat.com
> Subject: Re: [PATCH] New BFD vector for QNX Neutrino MIPS
> 
> Jeff Baker wrote:
> > I'm not quite sure I follow.  I understand the separation of the
> > independent, 32 and 64 bit functionality, but I don't see how I'd
> integrate
> > the QNX specific new/changed code into the existing files without
> breaking
> > everything else.
> 
> Could you provide a short overview what changes are needed for QNX MIPS?
> 
> 
> Thiemo

Attachment: qnx-incomplete.patch
Description: Binary data