From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 2AFBA1382C5 for ; Thu, 2 Jul 2020 03:50:34 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 1462AE0875; Thu, 2 Jul 2020 03:50:33 +0000 (UTC) Received: from NAM11-CO1-obe.outbound.protection.outlook.com (mail-co1nam11olkn2099.outbound.protection.outlook.com [40.92.18.99]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id C9B31E0875 for ; Thu, 2 Jul 2020 03:50:32 +0000 (UTC) ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=RFRz6gGXeeH4OVzUORxayO+6irzy5OTGT7Xr6fIWa0BepnQ8/d4SEAyDFUNncOh9yFQ3qUAiI6hnvR17IHMWgVdXQbLptuuHm+69twaLyEwr1hwA1ZAYsSHHcKqiGqm9BquA4ZdTZG8AGBeB2t4D9+UoXm2686Wsf+uso7opBmmBA9bGRtz8rD2dvg1td5kVAtyuLGmX8H+Gf1RvrvjxERujl8oL4VUF6siquDMEEUgOJvlu9IaDQhzTidMhJYCL8EuB8PYapsP7qfdiRN3tdQvzaN8xPA2hP1d7Ddg51g9YzsEMtYRbzmNomu4DSVF0gY/PoEzUUfBoLzA5vdsOZg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=aYPwrMdWBqre1aymziqLagO4RgPVs1BSwjhD6NMp6ig=; b=Ze/RkdFpDomMWEfsD0YwEOob3hZnDKoXf5m38h/0ZuvplU0kmNcZgqrxjZGhmWCOBz2WWB/rojZX7238s8nfkKmHvJXfzj3hu6KGD8Z9l43uv4ZI1zOWDOsWIRgOCmrLav4KaWoTgeTG51F2gEQwXfp+iOayPg82yNo5gm7kw9mVIjPruoWMIhJTjF2qDnSYhioRQ9V/+WY2+xLtvk4Yj26bjWu0JNEhYeELW2n7WzGgmbmEt9fuYsq2tb1PUqLFDetM0KfC29myBCrm/WI06IEHBR7X+bvPCNKEqJxw1eClCdl3zy5OVtjL0jEmZmIzeNa4kr616G8v53WVEkzuZQ== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=none; dmarc=none; dkim=none; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=live.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=aYPwrMdWBqre1aymziqLagO4RgPVs1BSwjhD6NMp6ig=; b=TTYPX7mgxADzj3KnVPztr07I1kTDrftdkhhvt7eMsNWdLaNu/aOch1vec2Ee9phOJoll0xG3xWHkkTtmpuQLCpg4UmWIjTsCKxrvPI+6RXOdD13XtvY8Olvwq48y6KB6LSMSXD9J7bKD457zGM6pTcSG63biCdH7RXV/BedR2MZcLgBxG3T61HwRE+dWUDU59u6Ygw6Kch0D1lLpT6PfPnH671KoDpfgJJCeoqIldLV+StEVZOYRIT6tm+tQu3ze/a43bg8UTCY5IloEgQcGrQNR4O76DJFf7tG1BigusFBpm69kmPgOLz34WJsEugA1estJu5VLgdGPqywynOwzAw== Received: from BN8NAM11FT038.eop-nam11.prod.protection.outlook.com (2a01:111:e400:fc4b::41) by BN8NAM11HT113.eop-nam11.prod.protection.outlook.com (2a01:111:e400:fc4b::284) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3153.24; Thu, 2 Jul 2020 03:50:31 +0000 Received: from BN6PR03MB3378.namprd03.prod.outlook.com (2a01:111:e400:fc4b::40) by BN8NAM11FT038.mail.protection.outlook.com (2a01:111:e400:fc4b::246) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3131.20 via Frontend Transport; Thu, 2 Jul 2020 03:50:31 +0000 X-IncomingTopHeaderMarker: OriginalChecksum:A999C16833ADEB7D2BCABD8238E9EA636190BA8833E976C47040D00EF780D156;UpperCasedChecksum:90AA598B5632C31B99C6FACD7FB394432AFD08B7FD9F8D109F02A2F7B1559116;SizeAsReceived:8922;Count:47 Received: from BN6PR03MB3378.namprd03.prod.outlook.com ([fe80::4537:5963:f4fe:a142]) by BN6PR03MB3378.namprd03.prod.outlook.com ([fe80::4537:5963:f4fe:a142%3]) with mapi id 15.20.3153.024; Thu, 2 Jul 2020 03:50:31 +0000 Date: Wed, 01 Jul 2020 23:50:28 -0400 User-Agent: K-9 Mail for Android In-Reply-To: <20200701165354.4f4yyz5fuwqdqpk7@tardis.localdomain> References: <20200629201204.hssao7lsdtcmpsme@tardis.localdomain> <02fc01d64fb1$006b0e30$01412a90$@jsteward.moe> <20200701165354.4f4yyz5fuwqdqpk7@tardis.localdomain> Content-Type: multipart/alternative; boundary="----PJ2O7B7JM9L67MJKL6RFORY99OD3CL" Content-Transfer-Encoding: 7bit Subject: Re: [gentoo-soc] Weekly Report: Portage Powered Android To: gentoo-soc@lists.gentoo.org,Gunwant Jain From: UnderSampled Message-ID: X-ClientProxiedBy: BN6PR11CA0044.namprd11.prod.outlook.com (2603:10b6:404:4b::30) To BN6PR03MB3378.namprd03.prod.outlook.com (2603:10b6:405:42::30) X-Microsoft-Original-Message-ID: <8F1DF0BB-D79C-4F24-BD1F-FFB279622FB8@live.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-soc@lists.gentoo.org Reply-to: gentoo-soc@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 X-MS-Exchange-MessageSentRepresentingType: 1 Received: from [IPv6:2600:1700:e70:a9a0:559e:2c6:ff86:7ae8] (2600:1700:e70:a9a0:559e:2c6:ff86:7ae8) by BN6PR11CA0044.namprd11.prod.outlook.com (2603:10b6:404:4b::30) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3153.20 via Frontend Transport; Thu, 2 Jul 2020 03:50:30 +0000 X-Microsoft-Original-Message-ID: <8F1DF0BB-D79C-4F24-BD1F-FFB279622FB8@live.com> X-TMN: [kV0kXixu5uZ3xx3Qg1DikS6mUOmgwedim37atCWyJSGhmzpLDp+hcF7OkQ2ILvYT] X-MS-PublicTrafficType: Email X-IncomingHeaderCount: 47 X-EOPAttributedMessage: 0 X-MS-Office365-Filtering-Correlation-Id: 19058a88-f18c-47f9-77c3-08d81e3b10cb X-MS-TrafficTypeDiagnostic: BN8NAM11HT113: X-Microsoft-Antispam: BCL:0; X-Microsoft-Antispam-Message-Info: 8PbEPKw5eMzKfn61KEHm+IPu2we82+BKmUPOL5xgSewQpZQZ8GylYMP/IsUOMSj69t/3ti39fY/7921pCLzKo10Rj7VfJ2IVIjpm3cDjLPf6pEUqNo0EkIFVLucbGGOCR1X2h3kkpqaevtTh3myXEKMe4SIPFUqbx0bgSU+C1RlhpypdCwPj/+KqQhgKQlXKVEB3/BrBkB0fMfjWhQ0Jvw== X-Forefront-Antispam-Report: CIP:255.255.255.255;CTRY:;LANG:en;SCL:0;SRV:;IPV:NLI;SFV:NSPM;H:BN6PR03MB3378.namprd03.prod.outlook.com;PTR:;CAT:NONE;SFTY:;SFS:;DIR:OUT;SFP:1901; X-MS-Exchange-AntiSpam-MessageData: 3D4Rgu8rV8YmSaI6Io2ClDkhmxKRYOrKMpEw7Gpj+Dr840PIsWiJk9ZXrurSfo/hCcdBdJjo1oyrlwtwDuKGvZnMn73HaycdCcii6ARVZoIzwDRWm19sb2Jf8tAqU1UzLBpdXisi6DfNFOwVw8ztFu9xfUs+Cs9fKCgFLoCwpRON0OOd6957v9dCC5PqMFl4CiOWe52Jyn98hmE6tgt7Fw== X-OriginatorOrg: live.com X-MS-Exchange-CrossTenant-Network-Message-Id: 19058a88-f18c-47f9-77c3-08d81e3b10cb X-MS-Exchange-CrossTenant-OriginalArrivalTime: 02 Jul 2020 03:50:31.3075 (UTC) X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted X-MS-Exchange-CrossTenant-Id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa X-MS-Exchange-CrossTenant-AuthSource: BN8NAM11FT038.eop-nam11.prod.protection.outlook.com X-MS-Exchange-CrossTenant-AuthAs: Anonymous X-MS-Exchange-CrossTenant-FromEntityHeader: Internet X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg: 00000000-0000-0000-0000-000000000000 X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN8NAM11HT113 X-Archives-Salt: 537f06ee-66b5-4b62-babd-828a24701caa X-Archives-Hash: c577048a6cf857dffabaa52200495172 ------PJ2O7B7JM9L67MJKL6RFORY99OD3CL Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Where is the IRC logged? I generally only catch up on my phone, and haven't= been able to check the IRC after the Gitter bridge failed=2E Stephen On July 1, 2020 12:53:54 PM EDT, Gunwant Jain = wrote: >Thanks for your comments Pengcheng=2E > >On 20/07/01 10:07PM, Pengcheng Xu wrote: >> It's good that you chose to get familiar with the GNU build system >(autotools); it will save you large amounts of time when meddling with >toolchain-related work=2E I would also suggest taking a look at the "GNU >Hello" project; it serves as a genuine example of the basics for a GNU >project, which GCC is as well=2E Get familiar with how to read the >configuration and compilation logs, especially when they're littered >with libtool calls instead of directly calling the compiler=2E > >Thanks for the tip, I will definitely look into it=2E > >> > But while building the toolchain, I was not able to compile `gcc` >as >> > I was riddled with errors along the way=2E Most of them are related >to the >> > newer `gcc` (version 9=2Ex) finding incompatibility in the sources of >the >> > `gcc` I am trying to build (version 4=2E9)=2E >> > I will continue to build the toolchain and hopefully move onto >> > separating `Bionic` from the other side of Android mid-week=2E >>=20 >> Just as Benda pointed out, 4=2E9 may be the one I chose two years ago, >but it's not a hard requirement: most Android things should compile >fine with any newer versions of GCC as long as the toolchain is >correctly configured for an Android target; in many occasions even >Clang works perfectly fine=2E You may try to fix the problems in the 4= =2E9 >tree, tweak the options for the "build" compiler (gcc-9) to accept >older, non-compliant sources, or try to find a newer version of GCC >source tree with Android (i=2Ee=2E Bionic) support=2E You may have bette= r >luck looking for such a source tree in the AOSP codebase=2E > >I agree, and I just realised that even though NDK requires gcc-4=2E9,=20 >Android 8=2E0 and above uses Clang for compilation=2E This differs from m= y >days of compiling custom ROMs (pre Android 8)=2E I am sorry for the >confusion created with gcc, I should have known better=2E > >Let me switch to building a clang based toolchain now onwards=2E=20 > >> And, we'd love to see a link to your weekly writeup of your efforts >and problems encountered in greater detail=2E We can find out more about >your progress and perhaps provide assistance if we can see the exact >problem; for example, it would be helpful if you quoted or linked to >the exact error message in the gcc build process you just mentioned=2E=20 >It's also a good idea to keep these in track for archival purposes, >such that future contributors can have an idea of what's going on if >they run into the same problem=2E > >I wasn't planning on keeping the logs of errors I face, but since it is >requested, I will provide them in a new segment of "weekly blogs" now=20 >onwards (keeping in mind that I have switched to using clang based=20 >toolchains)=2E Furthermore, I will be actively indicating the errors in= =20 >the IRC chatroom, which is logged as well=2E > >Please let me know if you have more comments=2E > >Regards, >Gunwant --=20 Sent from my Android device with K-9 Mail=2E Please excuse my brevity=2E ------PJ2O7B7JM9L67MJKL6RFORY99OD3CL Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable Where is the IRC logged? I generally only catch up on my phone, = and haven't been able to check the IRC after the Gitter bridge failed.
<= br>Stephen

On July 1, 2020 12:53:54 PM ED= T, Gunwant Jain <therealgunwant@gmail.com> wrote:
Thanks for your comments Pengcheng.

On 20/07/0=
1 10:07PM, Pengcheng Xu wrote:
It's good that you chose to get familiar with the GNU build system =
(autotools); it will save you large amounts of time when meddling with tool=
chain-related work.  I would also suggest taking a look at the "GNU He=
llo" project; it serves as a genuine example of the basics for a GNU p=
roject, which GCC is as well.  Get familiar with how to read the configurat=
ion and compilation logs, especially when they're littered with libtool cal=
ls instead of directly calling the compiler.

Thanks for=
 the tip, I will definitely look into it.

But whi=
le building the toolchain, I was not able to compile `gcc` as
I was ridd=
led with errors along the way. Most of them are related to the
newer `gc=
c` (version 9.x) finding incompatibility in the sources of the
`gcc` I a=
m trying to build (version 4.9).
I will continue to build the toolchain =
and hopefully move onto
separating `Bionic` from the other side of Andro=
id mid-week.

Just as Benda pointed out, 4.9 may be the =
one I chose two years ago, but it's not a hard requirement: most Android th=
ings should compile fine with any newer versions of GCC as long as the tool=
chain is correctly configured for an Android target; in many occasions even=
 Clang works perfectly fine.  You may try to fix the problems in the 4.9 tr=
ee, tweak the options for the "build" compiler (gcc-9) to accept =
older, non-compliant sources, or try to find a newer version of GCC source =
tree with Android (i.e. Bionic) support.  You may have better luck looking =
for such a source tree in the AOSP codebase.

I agree, a=
nd I just realised that even though NDK requires gcc-4.9, 
Android 8.0 a=
nd above uses Clang for compilation. This differs from my
days of compil=
ing custom ROMs (pre Android 8). I am sorry for the
confusion created wi=
th gcc, I should have known better.

Let me switch to building a clan=
g based toolchain now onwards. 

And, we'd love to see a link to your weekly writeup of your effo=
rts and problems encountered in greater detail.  We can find out more about=
 your progress and perhaps provide assistance if we can see the exact probl=
em; for example, it would be helpful if you quoted or linked to the exact e=
rror message in the gcc build process you just mentioned.  It's also a good=
 idea to keep these in track for archival purposes, such that future contri=
butors can have an idea of what's going on if they run into the same proble=
m.

I wasn't planning on keeping the logs of errors I fa=
ce, but since it is
requested, I will provide them in a new segment of &=
quot;weekly blogs" now 
onwards (keeping in mind that I have switch=
ed to using clang based 
toolchains). Furthermore, I will be actively in=
dicating the errors in 
the IRC chatroom, which is logged as well.
Please let me know if you have more comments.

Regards,
Gunwant<=
br>


--
Sent from my Android device = with K-9 Mail. Please excuse my brevity.= ------PJ2O7B7JM9L67MJKL6RFORY99OD3CL--