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 573BC1382C5 for ; Wed, 1 Jul 2020 16:54:07 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 81A2EE0909; Wed, 1 Jul 2020 16:54:06 +0000 (UTC) Received: from mail-pf1-x42c.google.com (mail-pf1-x42c.google.com [IPv6:2607:f8b0:4864:20::42c]) (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 74025E0909 for ; Wed, 1 Jul 2020 16:54:06 +0000 (UTC) Received: by mail-pf1-x42c.google.com with SMTP id j1so11249176pfe.4 for ; Wed, 01 Jul 2020 09:54:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=TrmYPBw60mgkXQaxMYmktR5BfZ7ehPFMzjOAZhFmKfM=; b=mjuP135eZkIdZLi0X9pNwSGH6QzZTGqoU4jDBcbOnlwkKCRHZRkeAciyrXyZ0INb8U ZClCdISZ5tFJDUlCcTmev8ORJjRYtLeYb4E+zjxdNwPLEaIcTsNXVUpT3QNASgS12Dm+ oEdO06ZK9i7ZXzWK2cOfKFge7p9Xgc5JgdqLJKZ5RmgDBGH1GTs4c6jIPskQ/dudTplO tEL5J0F7rrA25JICzhWt98isa0+wYpUriDptawoSGndtt+PTrdmqpznmW1fFNNeIRoE/ RiJA8iU4FV4POdY75dRAug5LBa/4jdpIXl20Ckqqc1QndoPhr1+Jd1ltyFzo8Ak3jUwN 0sPw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=TrmYPBw60mgkXQaxMYmktR5BfZ7ehPFMzjOAZhFmKfM=; b=pyRxd9aor1PSX4+x0EVxMFxJja/8rkpCVtandnaqQIYpogq6Y+orOpB0o+gHc5Azc5 vUVWGeM663URk4o1LOmmykisx/HUsU5YSmIXcBRcOgDHbVhvENl+Wsk095LXrVvURs9y 7EiXhlIZwlgGR7lnOaTRtldcxRrZ7zUL1IN/GbRPaZhsTWGdOsIe9SBN9PKRq+h3HeFv c5kAVPCEnrmOCA1NRmeXw/7UFn06b8wwVVUQjazODWWiFRFZTjA99Pxhfsyi9bN4GmeX kTd+V7q4pusAIPYA1Xguj0wmoqIgk01pG4Mek/m46lrnm7Hp4L0n8CD2s/enJFAL0rw8 P6EA== X-Gm-Message-State: AOAM530eoqQsqVfcPs+kjHeg82oEtR/dGzM0i5hPoGcYvS+uxj58yC/z aYJQ92KySjcQsf46P4G5GRW6t+Oq X-Google-Smtp-Source: ABdhPJzcBjRNzAA1TBmlI0nP2nfVx4t+ltIRe2hHJ1deWKrLWRXkhTP7EiTcYRq4HeQYtAabV8h09Q== X-Received: by 2002:a63:4c08:: with SMTP id z8mr20058815pga.201.1593622444963; Wed, 01 Jul 2020 09:54:04 -0700 (PDT) Received: from localhost ([223.190.120.187]) by smtp.gmail.com with ESMTPSA id y7sm4813951pjp.47.2020.07.01.09.54.03 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 01 Jul 2020 09:54:03 -0700 (PDT) Date: Wed, 1 Jul 2020 22:23:54 +0530 From: Gunwant Jain To: gentoo-soc@lists.gentoo.org Subject: Re: [gentoo-soc] Weekly Report: Portage Powered Android Message-ID: <20200701165354.4f4yyz5fuwqdqpk7@tardis.localdomain> References: <20200629201204.hssao7lsdtcmpsme@tardis.localdomain> <02fc01d64fb1$006b0e30$01412a90$@jsteward.moe> 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 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="vx7yx37glif3q6o6" Content-Disposition: inline In-Reply-To: <02fc01d64fb1$006b0e30$01412a90$@jsteward.moe> X-Archives-Salt: 98cae162-f6e2-4dcb-b99f-6ed34e97c8ed X-Archives-Hash: 6dcc816819bf96957d2c215cfade5bfb --vx7yx37glif3q6o6 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Thanks for your comments Pengcheng. On 20/07/01 10:07PM, Pengcheng Xu wrote: > It's good that you chose to get familiar with the GNU build system (autot= ools); it will save you large amounts of time when meddling with toolchain-= related work. I would also suggest taking a look at the "GNU Hello" projec= t; it serves as a genuine example of the basics for a GNU project, which GC= C is as well. Get familiar with how to read the configuration and compilat= ion logs, especially when they're littered with libtool calls instead of di= rectly calling the compiler. Thanks for the tip, I will definitely look into it. > > 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. >=20 > 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 things should compile fine with a= ny newer versions of GCC as long as the toolchain is correctly configured f= or an Android target; in many occasions even Clang works perfectly fine. Y= ou may try to fix the problems in the 4.9 tree, tweak the options for the "= build" compiler (gcc-9) to accept older, non-compliant sources, or try to f= ind 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 codeba= se. I agree, and I just realised that even though NDK requires gcc-4.9,=20 Android 8.0 and above uses Clang for compilation. This differs from my days of compiling custom ROMs (pre Android 8). I am sorry for the confusion created with gcc, I should have known better. Let me switch to building a clang based toolchain now onwards.=20 > And, we'd love to see a link to your weekly writeup of your efforts and p= roblems encountered in greater detail. We can find out more about your pro= gress and perhaps provide assistance if we can see the exact problem; for e= xample, it would be helpful if you quoted or linked to the exact error mess= age 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 contributors ca= n have an idea of what's going on if they run into the same problem. 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). Furthermore, I will be actively indicating the errors in=20 the IRC chatroom, which is logged as well. Please let me know if you have more comments. Regards, Gunwant --vx7yx37glif3q6o6 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAABCAAdFiEEVcYcuddz0Grkn4q20gpuZPFudnkFAl78v6EACgkQ0gpuZPFu dnlaYAgAnRJxev6ZPYaeZf0UtzULPeHqZrnwhEfRmY5t9l48aCy0wP2rzlZM/ikp jPK5Lm2xmaJUj16T7bVA2BvS73QxG7UrSLCb09rfKSnsxrsJldA06JhAcSgGvoSx 0DtG5qwpiLkp1IlxRVWML4Mfgg0XuOKbscpzI8DEIjy9+ckNKwicKAiBFn9nagNV amsi87bkRWzzBpYnxh+VqdDzCQ1CZ5h7qnT271mMXEU8hLl+AJTes2dBrHP9PBAc A9RwQ9dqyPU2LF1bNRderNJBYOQc+61CV8Sh7QTC2EBhyCFbrBBMcev8XRS70Wj0 DER5PN7twMXwsy53LLkVzW90Gg73+w== =Gygj -----END PGP SIGNATURE----- --vx7yx37glif3q6o6--