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: FW: Re: Why is my executabel in DOS file format?

From: Ian Lance Taylor <ian at wasabisystems dot com>
To: David Daney <ddaney at avtrex dot com>
Cc: Meg Abyte <fitter20 at hotmail dot com>, binutils at sources dot redhat dot com
Date: 03 Mar 2004 18:04:55 -0500
Subject: Re: FW: Re: Why is my executabel in DOS file format?
References: <BAY7-F80ulXx5TjamJr00010213@hotmail.com><40465DF2.5080809@avtrex.com> <404662D0.4090609@avtrex.com>

David Daney <ddaney@avtrex.com> writes:

> I guess the patch will not change how the linker works, but it fixes
> my main problems with objcopy.  It seems that someone could add a
> command line parameter to the linker to do the same thing.

Yes, getting linker support too is a reason to create a new BFD target
vector, as I was thinking originally.

I don't particularly like objcopy --srec-len or --srec-forces3
either.  But I suppose it's better than nothing.

Maybe we need an interface for target specific options, like objdump
-M for the disassembler?  Hmmm.

Ian

References:
- FW: Re: Why is my executabel in DOS file format?
  - From: Meg Abyte
- Re: FW: Re: Why is my executabel in DOS file format?
  - From: David Daney
- Re: FW: Re: Why is my executabel in DOS file format?
  - From: David Daney

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