From: Jing Yu <jingyu@google.com>
To: dj@redhat.com
Cc: gcc-patches <gcc-patches@gcc.gnu.org>,
"Joseph S. Myers" <joseph@codesourcery.com>,
Ye Joey <joey.ye.cc@gmail.com>
Subject: Ping:Re: Skip building target libiberty for arm*-*-linux-androideabi
Date: Fri, 03 Jun 2011 18:21:00 -0000 [thread overview]
Message-ID: <BANLkTinJv-qXMd8rTfGYmbEd8MZxnKTe3w@mail.gmail.com> (raw)
Ping.
http://gcc.gnu.org/ml/gcc-patches/2011-05/msg02208.html
On Tue, May 31, 2011 at 11:32 AM, Jing Yu <jingyu@google.com> wrote:
> Based on discussion on another thread
> (http://www.mail-archive.com/gcc-patches@gcc.gnu.org/msg06627.html),
> what Joseph recommended was ripping out all support for building
> libiberty for the target side as it is not needed. Thus I doubt
> skipping target-libiberty for all targets is acceptable.
> 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.
>
> Thanks,
> Jing
>
> On Sun, May 29, 2011 at 9:23 PM, Ye Joey <joey.ye.cc@gmail.com> wrote:
>> On Sat, May 28, 2011 at 5:42 AM, Jing Yu <jingyu@google.com> wrote:
>>>
>>> Building gcc-4.6 arm android toolchain fails because of an
>>> incompatible function definition between libiberty and bionic.
>>>
>>> Thanking Joseph, I have learned that "there's no such thing as a
>>> target libiberty" and we should rip all the target-libiberty rules
>>> out. I don't know if someone is working on it. Before that patch comes
>>> out, can we add arm*-*-linux-androideabi to the list of targets where
>>> target-libiberty is skipped?
>>>
>> How about skip libiberty for all targets then?
>>
>> - Joey
>
next reply other threads:[~2011-06-03 18:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-03 18:21 Jing Yu [this message]
2011-06-03 18:26 ` DJ Delorie
2011-06-03 18:55 ` Jing Yu
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=BANLkTinJv-qXMd8rTfGYmbEd8MZxnKTe3w@mail.gmail.com \
--to=jingyu@google.com \
--cc=dj@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=joey.ye.cc@gmail.com \
--cc=joseph@codesourcery.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).