From: Gunwant Jain <therealgunwant@gmail.com>
To: Benda Xu <heroxbd@gentoo.org>
Cc: gentoo-soc@lists.gentoo.org
Subject: Re: [gentoo-soc] Weekly Report: Portage Powered Android
Date: Wed, 1 Jul 2020 21:42:58 +0530 [thread overview]
Message-ID: <20200701161258.s4mxna65c4s5m36a@tardis.localdomain> (raw)
In-Reply-To: <874kqrzoth.fsf@proton.d.airelinux.org>
[-- Attachment #1: Type: text/plain, Size: 1115 bytes --]
On 20/07/01 03:17PM, Benda Xu wrote:
> > But while building the toolchain, I was not able to compile `gcc` as I
> > was riddled with errors along the way. Most of them are related to the
> > newer `gcc` (version 9.x) finding incompatibility in the sources of
> > the `gcc` I am trying to build (version 4.9). I will continue to
> > build the toolchain and hopefully move onto separating `Bionic` from
> > the other side of Android mid-week.
>
> Why do you need to build gcc-4.9?
I assumed we need to build the gcc which is used by the Android platform
(and as an extension NDK as well). The latest gcc which they ship is
version 4.9 [1].
> Does the version number "4.4.222" coresspond to the kernel of your
> phone?
Yes.
> Generally, when compiling a toolchain, you don't need to match
> the linux-header version to the running kernel. The newest linux-header
> will do.
I was not aware of that, thanks. But then again, I don't see why I
shouldn't continue using the "4.4.222" headers.
Regards,
Gunwant
[1] https://android.googlesource.com/toolchain/gcc/+/refs/heads/master
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-07-01 16:13 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-29 20:12 [gentoo-soc] Weekly Report: Portage Powered Android Gunwant Jain
2020-06-29 21:27 ` EBo
2020-06-30 21:42 ` Gunwant Jain
2020-07-01 2:37 ` EBo
2020-07-01 3:15 ` Gunwant Jain
2020-07-01 12:40 ` Lucas Ramage
2020-07-01 7:17 ` Benda Xu
2020-07-01 16:12 ` Gunwant Jain [this message]
2020-07-01 14:07 ` Pengcheng Xu
2020-07-01 16:53 ` Gunwant Jain
2020-07-02 3:50 ` UnderSampled
2020-07-02 12:14 ` Gunwant Jain
-- strict thread matches above, loose matches on Subject: below --
2020-08-17 18:05 Gunwant Jain
2020-08-17 23:15 ` Benda Xu
2020-08-20 6:21 ` Gunwant Jain
2020-08-12 1:41 Gunwant Jain
2020-08-12 7:34 ` EBo
2020-08-14 7:26 ` Gunwant Jain
2020-07-30 15:00 Gunwant Jain
2020-07-20 7:40 Gunwant Jain
2020-07-24 14:08 ` Benda Xu
2020-07-24 15:02 ` Gunwant Jain
2020-07-24 17:07 ` UnderSampled
2020-07-24 18:12 ` Gunwant Jain
2020-07-25 3:00 ` Benda Xu
2020-07-25 8:02 ` Gunwant Jain
2020-07-25 8:21 ` Gunwant Jain
2020-07-13 23:09 Gunwant Jain
2020-07-14 0:17 ` Benda Xu
2020-07-14 5:01 ` Gunwant Jain
2020-07-15 1:04 ` Benda Xu
2020-07-15 1:09 ` UnderSampled
2020-07-15 4:55 ` Gunwant Jain
2020-07-15 4:45 ` Pengcheng Xu
2020-07-15 4:58 ` Gunwant Jain
2020-07-15 4:52 ` Gunwant Jain
2020-07-14 4:05 ` Pengcheng Xu
2020-07-14 5:05 ` Gunwant Jain
2020-07-08 11:39 Gunwant Jain
2020-07-08 13:53 ` Pengcheng Xu
2020-07-09 1:04 ` Benda Xu
2020-06-22 19:15 Gunwant Jain
2020-06-23 4:45 ` Pengcheng Xu
2020-06-23 11:44 ` Gunwant Jain
2020-07-01 7:14 ` Benda Xu
2020-06-15 8:03 Gunwant Jain
2020-07-01 7:10 ` Benda Xu
2020-06-09 11:39 Gunwant Jain
2020-07-01 7:08 ` Benda Xu
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=20200701161258.s4mxna65c4s5m36a@tardis.localdomain \
--to=therealgunwant@gmail.com \
--cc=gentoo-soc@lists.gentoo.org \
--cc=heroxbd@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