public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/52989] Installation error on OS X (arm-eabi) cross-compiler
Date: Mon, 18 Jun 2012 15:47:00 -0000 [thread overview]
Message-ID: <bug-52989-4-dDTz2Rxzf1@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52989-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52989
--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> 2012-06-18 15:47:16 UTC ---
(In reply to comment #3)
> (In reply to comment #2)
> > (In reply to comment #1)
> > I don't think we support --with-multilib-list yet for arm -
> If not, what is the proper way to specify the libraries to build for ARM
> (regular ARM ISA and Thumb-1 ISA)?
You have to edit the t-arm-elf but the default is to enable arm and thumb
multilibs.
next prev parent reply other threads:[~2012-06-18 15:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-14 18:11 [Bug other/52989] New: " eblot.ml at gmail dot com
2012-04-24 4:26 ` [Bug target/52989] " pinskia at gcc dot gnu.org
2012-05-16 10:05 ` ramana at gcc dot gnu.org
2012-06-18 14:06 ` eblot.ml at gmail dot com
2012-06-18 15:47 ` pinskia at gcc dot gnu.org [this message]
2012-11-28 3:28 ` ramana at gcc dot gnu.org
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=bug-52989-4-dDTz2Rxzf1@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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).