From: Jing Yu <jingyu@google.com>
To: Richard Earnshaw <rearnsha@arm.com>,
ramana.radhakrishnan@arm.com, paul@codesourcery.com,
nickc@redhat.com
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: Ping:Re: Skip building target libiberty for arm*-*-linux-androideabi
Date: Fri, 03 Jun 2011 18:55:00 -0000 [thread overview]
Message-ID: <BANLkTimAvtaSY8v8LP9HG4vxP_Bq+uEj7A@mail.gmail.com> (raw)
In-Reply-To: <201106031826.p53IQVu8030199@greed.delorie.com>
ARM maintainers,
Is it ok to skip building target-libiberty for arm*-*-linux-androideabi target?
http://gcc.gnu.org/ml/gcc-patches/2011-05/msg02208.html
Thanks,
Jing
On Fri, Jun 3, 2011 at 11:26 AM, DJ Delorie <dj@redhat.com> wrote:
>
>> Ping.
>> http://gcc.gnu.org/ml/gcc-patches/2011-05/msg02208.html
>>
>> > I don't have the bandwidth to work on the ideal patch. Thus I am
>> > wondering if we can skip target-libiberty for androideabi target
>> > before the ideal patch is out.
>
> Target-specific changes in the build are up to the target maintainers.
>
prev parent reply other threads:[~2011-06-03 18:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-03 18:21 Jing Yu
2011-06-03 18:26 ` DJ Delorie
2011-06-03 18:55 ` Jing Yu [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=BANLkTimAvtaSY8v8LP9HG4vxP_Bq+uEj7A@mail.gmail.com \
--to=jingyu@google.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=nickc@redhat.com \
--cc=paul@codesourcery.com \
--cc=ramana.radhakrishnan@arm.com \
--cc=rearnsha@arm.com \
/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).