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 5A574138334 for ; Tue, 4 Dec 2018 09:03:38 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 5B3AFE0C4A; Tue, 4 Dec 2018 09:03:30 +0000 (UTC) Received: from mx07-00178001.pphosted.com (mx08-00178001.pphosted.com [91.207.212.93]) (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 C7F2FE0B97 for ; Tue, 4 Dec 2018 09:03:29 +0000 (UTC) Received: from pps.filterd (m0046661.ppops.net [127.0.0.1]) by mx08-00178001.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id wB491f0R019772 for ; Tue, 4 Dec 2018 10:03:27 +0100 Received: from beta.dmz-eu.st.com (beta.dmz-eu.st.com [164.129.1.35]) by mx08-00178001.pphosted.com with ESMTP id 2p3wt6ea3y-1 (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Tue, 04 Dec 2018 10:03:27 +0100 Received: from zeta.dmz-eu.st.com (zeta.dmz-eu.st.com [164.129.230.9]) by beta.dmz-eu.st.com (STMicroelectronics) with ESMTP id 36D62100 for ; Tue, 4 Dec 2018 09:03:27 +0000 (GMT) Received: from Webmail-eu.st.com (sfhdag7node2.st.com [10.75.127.20]) by zeta.dmz-eu.st.com (STMicroelectronics) with ESMTP id 00B7F26F8 for ; Tue, 4 Dec 2018 09:03:26 +0000 (GMT) Received: from [10.50.186.1] (10.75.127.48) by SFHDAG7NODE2.st.com (10.75.127.20) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Tue, 4 Dec 2018 10:03:26 +0100 Subject: Re: [gentoo-user] RAM checks for chromium To: References: <5441151.iEbWm1uMdi@dell_xps> <2242407.4WviNIMaRH@dell_xps> From: Raffaele Belardi Message-ID: <85c6ecb6-fbee-75e2-6a19-b7483ed489e3@st.com> Date: Tue, 4 Dec 2018 10:04:37 +0100 User-Agent: Mozilla/5.0 (X11; Linux i686; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.9.1 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 In-Reply-To: <2242407.4WviNIMaRH@dell_xps> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Originating-IP: [10.75.127.48] X-ClientProxiedBy: SFHDAG8NODE1.st.com (10.75.127.22) To SFHDAG7NODE2.st.com (10.75.127.20) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2018-12-04_05:,, signatures=0 X-Archives-Salt: 76e0870b-73c4-46da-a736-d6d066928287 X-Archives-Hash: 945ecbd32e202e5c4409df9ec8756efb > Thanks for this. It may be I'll need to build chromium as a binary on the > faster PC from now on and copy it over to the older clients, but I can't > recall what command spews out the detailed CFLAGS for the client which I will > need to run on the faster host's CLI to emerge the binary. Grateful for any > hints. app-portage/cpuid2cpuflags Mick wrote: > On Tuesday, 4 December 2018 08:06:22 GMT Alexander Kapshuk wrote: >> On Tue, Dec 4, 2018 at 9:35 AM Mick wrote: >>> Two Intel systems with 4G RAM failed to build chromium, even after setting >>> >>> MAKEOPTS="-j2". The ebuild is checking for a minimum of 3G RAM: >>>>>> Running pre-merge checks for www-client/chromium-70.0.3538.110 >>> >>> * Checking for at least 3 GiB RAM ... [ ok >>> ] >>> * Checking for at least 5 GiB disk space at "/var/tmp/portage/www-client/ >>> >>> chromium-70.0.3538.110/temp" ... [ ok >>> ] >>> >>> Given I've spent more than two days compiling to get nowhere with this, >>> I'm >>> thinking: >>> >>> a) Chromium probably needs more than 3G now. >>> b) Either the ebuild, or portage, ought to check available RAM and >>> dynamically adjust the number of jobs accordingly - or have I watched too >>> many AI movies? >>> >>> -- >>> Regards, >>> Mick >> >> You're right. Chromium does require more than 3G of RAM to build. >> Here are the current system requirements for building Chromium on Linux: >> >> System requirements >> A 64-bit Intel machine with at least 8GB of RAM. More than 16GB is >> highly recommended. > > OK it figures, an AMD system with 16G RAM and /var/portage/ on a tmpfs had no > problem. > > >> At least 100GB of free disk space. > > O_O What the ... ? > > >> You must have Git and Python v2 installed already. >> >> See the link below for details. >> https://chromium.googlesource.com/chromium/src/+/HEAD/docs/linux_build_instr >> uctions.md#system-requirements > > Thanks for this. It may be I'll need to build chromium as a binary on the > faster PC from now on and copy it over to the older clients, but I can't > recall what command spews out the detailed CFLAGS for the client which I will > need to run on the faster host's CLI to emerge the binary. Grateful for any > hints. >