From: "Mark E." <snowball3 AT bigfoot DOT com>
To: "Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>, djgpp-workers AT delorie DOT com
Date: Sun, 18 Feb 2001 15:48:19 -0500
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: possible objcopy problem.
Message-ID: <3A8FEEC3.5120.1473CE@localhost>
In-reply-to: <3791-Sun18Feb2001222902+0200-eliz@is.elta.co.il>
References: <3A8FCC18 DOT 8337 DOT 2AB3C6 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

> > The output arch. is set [to] 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.
> 
> But doesn't coff-go32 identify the output architecture unambiguously?

Sure. But objcopy doesn't care if the output arch. can be deduced from the 
output target because it doesn't even try to.

Mark