From: Arnaud Lacombe <lacombar@gmail.com>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: Mike Frysinger <vapier@gentoo.org>, binutils@sourceware.org
Subject: Re: Using binutils with all target enabled
Date: Thu, 02 Dec 2010 00:17:00 -0000 [thread overview]
Message-ID: <AANLkTikdTJHY9myiq2aPF=DcmLaf5W-Bpndt1WXZE1mt@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1012020009400.9155@digraph.polyomino.org.uk>
Hi,
On Wed, Dec 1, 2010 at 7:10 PM, Joseph S. Myers <joseph@codesourcery.com> wrote:
> On Wed, 1 Dec 2010, Mike Frysinger wrote:
>
>> On Wednesday, December 01, 2010 14:27:10 Arnaud Lacombe wrote:
>> > I'd have hoped that specifying the the format explicits would have
>> > been possible, but very few program seems to support such options.
>> > Actually, only objdump (maybe others) accepts a '-b' flags.
>>
>> ld has -m, objcopy/strip have -F/-O/-I, readelf doesnt care, addr2line/nm/size
>> have --target. seems like just as, ar, and ranlib are missing command line
>> flags, and --target might be the logical flag to add to them.
>
> I don't think as has any useful multi-target support; the code is full of
> uses of macros defined in target-specific headers.
>
I was talking about ar/ranlib here, not `as'. I'm fine with having a
target specific `as'.
- Arnaud
prev parent reply other threads:[~2010-12-02 0:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-01 19:27 Arnaud Lacombe
2010-12-01 20:56 ` Andreas Schwab
2010-12-01 22:06 ` Mike Frysinger
2010-12-01 23:16 ` Arnaud Lacombe
2010-12-04 3:37 ` [PATCH 2/3] binutils/ar: use getopt_long() for options parsing Arnaud Lacombe
2010-12-04 3:37 ` [PATCH 1/3] binutils/ar: split ar/ranlib path Arnaud Lacombe
2010-12-04 10:45 ` Mike Frysinger
2010-12-04 3:38 ` [PATCH 3/3] binutils/ar: learn --target Arnaud Lacombe
2010-12-08 5:08 ` Alan Modra
2010-12-15 19:58 ` H.J. Lu
2010-12-15 20:09 ` Arnaud Lacombe
2010-12-16 1:23 ` H.J. Lu
2010-12-04 3:47 ` Using binutils with all target enabled Arnaud Lacombe
2010-12-02 0:10 ` Joseph S. Myers
2010-12-02 0:17 ` Arnaud Lacombe [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='AANLkTikdTJHY9myiq2aPF=DcmLaf5W-Bpndt1WXZE1mt@mail.gmail.com' \
--to=lacombar@gmail.com \
--cc=binutils@sourceware.org \
--cc=joseph@codesourcery.com \
--cc=vapier@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).