This is the mail archive of the
binutils@sources.redhat.com
mailing list for the binutils project.
Re: Change to coff-arm.c breaks binutils
- To: Nick Clifton <nickc at cambridge dot redhat dot com>
- Subject: Re: Change to coff-arm.c breaks binutils
- From: Richard Earnshaw <rearnsha at arm dot com>
- Date: Wed, 02 May 2001 13:45:07 +0100
- cc: Richard dot Earnshaw at arm dot com, Sean McNeil <sean at mcneil dot com>, binutils at sources dot redhat dot com, aoliva at redhat dot com
- Organization: ARM Ltd.
- Reply-To: Richard dot Earnshaw at arm dot com
> Hi Richard,
>
> > > And I added a definition of VXWORKS in the config.bfd file.
> >
> > Wouldn't this be better done as a run-time option? Then there would
> > be a better chance of having a bfd library that could support
> > multiple targets.
>
> Probably, although what happens if you try to link mixed binaries ?
Well, no worse than at present. If we can distinguish the two types then
we could even DTRT; at worst we could refuse to link (which would be
better than the current situation where we would link incorrectly).
>
> Besides, I am fairly certain that this "feature" is actually a
> disguised bug somewhere, probably in the assembler, and I would prefer
> to track it down and fix it once and for all. This #define is a
> workaround until I can find some time to do that.
>
Though that still leaves the issue of existing binaries/libraries.
R.