From: "Mark E." <snowball3 AT bigfoot DOT com>
To: djgpp-workers AT delorie DOT com
Date: Sun, 18 Feb 2001 13:20:24 -0500
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: possible objcopy problem.
Message-ID: <3A8FCC18.8337.2AB3C6@localhost>
In-reply-to: <1190-Fri16Feb2001221223+0200-eliz@is.elta.co.il>
References: <3A8CF9FC DOT 21062 DOT 9A92D AT localhost> (snowball3 AT bigfoot DOT com)
X-mailer: Pegasus Mail for Win32 (v3.12c)
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

> Yes, but I don't understand why the solution calls for a new
> command-line argument.  Isn't the target format (COFF in our case)
> enough to let BFD set the architecture?

The output arch. is set the input arch when copying. But since 'binary' 
usually doesn't have an arch. for BFD to catch on to, a warning message is 
output. One can copy coff-go32->binary and then copy that to binary->coff-
go32 without warning.

Mark