From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: Build LSK 3.14 kernel with android-toolchain
Date: Tue, 02 Dec 2014 14:03:02 +0100 [thread overview]
Message-ID: <2152219.OTGyvezhSH@wuerfel> (raw)
In-Reply-To: <20141202182952.01eda0ca@xhacker>
On Tuesday 02 December 2014 18:29:52 Jisheng Zhang wrote:
> On Tue, 2 Dec 2014 02:24:03 -0800
> > On Tuesday 02 December 2014 17:39:21 Jisheng Zhang wrote:
> > >
> > > From my experience in last several years
> > >
> > > 1. the arm-linux-androideabi- toolchain sets some options by default, PIC
> > > for example, even -mno-android can't disable all the side effects per my
> > > test.
> >
> > Yes, that's definitely possible. Any idea how the android folks build their
> > kernel?
>
> copied from https://android.googlesource.com/toolchain/build/+/HEAD/README
>
> The Android toolchain supports the following targets:
> a. arm-linux-androideabi
> b. arm-eabi (for Android kernel)
> c. arm-newlib-eabi (for runnng gcc regression tests)
> d. i[3456]86-*-linux-gnu, x86_64-*-linux-gnu (for x86 targets)
>
> So they build android kernel using the arm-eabi- toolchain.
Interesting, I think that's not supported at all, as the ABI is slightly
incompatible between arm-eabi and arm-linux-gnueabi, in particular the
short-enums that are used only in arm-eabi.
I have a patch somewhere that errors out if someone attempts to build
the kernel with an arm-eabi toolchain, I should probably submit that
upstream. The Android folks will likely just revert it, but it would
catch everyone that tries to build a normal kernel in the Android way.
Arnd
next prev parent reply other threads:[~2014-12-02 13:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAAQ0ZWRQ05GiCOqV2Q6g2B6n+XN-qs9o6MKOFXiK2wKrW0nvog@mail.gmail.com>
[not found] ` <2052560.M0NHOo7Rnz@wuerfel>
2014-12-02 9:04 ` Build LSK 3.14 kernel with android-toolchain Shawn Guo
2014-12-02 9:39 ` Jisheng Zhang
2014-12-02 10:24 ` Arnd Bergmann
2014-12-02 10:29 ` Jisheng Zhang
2014-12-02 12:34 ` Shawn Guo
2014-12-02 13:04 ` Arnd Bergmann
2014-12-02 13:03 ` Arnd Bergmann [this message]
2014-12-02 12:04 ` Shawn Guo
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=2152219.OTGyvezhSH@wuerfel \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.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 NNTP newsgroup(s).