This is the mail archive of the binutils@sources.redhat.com mailing list for the binutils project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: QNX binutils targets

From: "H. J. Lu" <hjl at lucon dot org>
To: Graeme Peterson <gp at qnx dot com>
Cc: Hans-Peter Nilsson <hp at bitrange dot com>,Segher Boessenkool <segher at koffie dot nl>, binutils at sources dot redhat dot com
Date: Fri, 25 Oct 2002 11:27:41 -0700
Subject: Re: QNX binutils targets
References: <Pine.BSF.4.44.0210251259220.78167-100000@dair.pair.com> <200210251814.SAA363016228@node128.ott.qnx.com>

On Fri, Oct 25, 2002 at 02:14:54PM -0400, Graeme Peterson wrote:
> Hey.
> 
> If possible:
> 
> 1) I want to maintain backward compatibility with our
>    exisiting tools and the binaries the produced. 

You can take both ELFOSABI_NONE and ELFOSABI_QNX as valid QNX input,
when you configure bfd with QNX targets only, but always output with
ELFOSABI_QNX. That means the consumer of your new binaries should be
the same version of binutils or newer.

> 
> 2) I want to see that other people do not get the QNX 
>    specific behavior when they build --enable-targets=all.

When bfd is configured with --enable-targets=all, don't accept
ELFOSABI_NONE for QNX.

H.J.

Follow-Ups:
- Re: QNX binutils targets
  - From: H. J. Lu

References:
- Re: QNX binutils targets
  - From: Hans-Peter Nilsson
- Re: QNX binutils targets
  - From: Graeme Peterson

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]